DRAFT: Implement TLS/SSL Support for EPMD

[karomnii]

Description
This PR introduces optional TLS/SSL encryption for EPMD (Erlang Port Mapper Daemon) communications. It updates both the C-based EPMD daemon and the erl_epmd Erlang client to securely handle encrypted socket connections.

Key Changes

• EPMD Daemon (C-side): Linked OpenSSL libraries and added -tls <cert_path> <key_path> command-line arguments. Replaced direct socket read/write operations with wrappers that dynamically use standard TCP or TLS depending on the configuration.
• Erlang Client (erl_epmd.erl): Added logic to check for epmd_ssl_options in the application environment. If present, the client routes connections through the ssl module instead of gen_tcp and natively handles the corresponding SSL socket messages and connection states.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

CT Test Results

No tests were run for this PR. This is either because the build failed, or the PR is based on a branch without GH actions tests configured.

Results for commit 04e2f77

To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass.

See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally.

Artifacts

• No CT logs found
• No HTML docs found
• No Windows Installer found

// Erlang/OTP Github Action Bot

[joaohf]

Hi,

Is that possible to make it build time configurable ?

[karomnii]

Hi @joaohf,
Could you clarify the question a little bit more? I am not sure that I understand what you mean by build-time configurable. Right now, it is configurable by the user at start time.