Fixes issue/TLS-init-failing (#3468)

[kaitozaw]

Pull Request

Category

Bug

Feature/Issue Description

Q: Please give a brief summary of your feature/fix
A: This PR fixes a TLS initialisation failure in the Docker-based setup, where BeEF crashes with an EventMachine “Encryption not available” error.

Q: Give a technical rundown of what you have changed (if applicable)
A:
The root cause was that EventMachine was being built without SSL/TLS support inside the Docker image because OpenSSL development headers were missing at build time. Since bundle install is executed in the Docker builder stage, EventMachine’s native extension was compiled without TLS support.

This PR adds libssl-dev to the Docker builder stage so EventMachine is built with SSL/TLS support.
In addition, libssl-dev has been removed from the final runtime stage, as it is only required at build time and not needed once the native extension is compiled.

After these changes, BeEF starts correctly with HTTPS enabled and no longer raises the TLS-related runtime error.

[zinduolis]

PR Review Summary: Fixes TLS Init Failing in Docker (#3470)

I have successfully verified this PR in a Docker environment.

Testing Steps Performed:

1. Environment: Docker container build based on the current PR branch.
2. Setup: Generated certificates for localhost via bundle exec rake ssl:replace.
3. Configuration: Enabled HTTPS in config.yaml and set non-default credentials.
4. Verification: Rebuilt and ran the container, confirming success on HTTPS.

Results:

• ✅ Success: BeEF starts without the EventMachine "Encryption not available" error.
• ✅ Success: Admin UI is accessible over HTTPS.
• ✅ Stability: Non-HTTPS startup remains unaffected and works correctly.

The change correctly addresses the root cause by providing the necessary build-time dependencies.

Verdict: Approved.