serly is an OTP application which serves up TLS/SSL TCP sockets to a callback function. The application config, serly.config, specifies which port and x509 certificate/key to use for the created sockets.
This application is pretty new so it may not handle all socket closing/error modes perfectly.
The opened socket also uses the following options:
{mode, binary}: received packets are delivered as binary{reuseaddr, true}: many workers will reuse the socket{active, false}: the callback function must use ssl:recv to receive packet data
serly was developed against Erlang 18.3. It hasn't been tested with earlier versions, but it shouldn't rely on 'recent' language changes/features. Let me know if it builds for you and on what Erlang version. :)
$ rebar3 compile
A key principle in serly is its plugin behavior -- the consumer provides a {Module, Function} callback to serly:listen/1. serly will prepare a socket and pass it to the callback. The callback should serve as an entry point for the business logic.
To see an example of this, check out the usage_example module:
$> rebar3 compile
===> Verifying dependencies...
===> Compiling serly
# You'll see some warnings for undefined gen_server callbacks
$> erl -pa $(rebar3 path) -config serly.config
1> usage_example:start().
Received: Why, hello there!
Received: Why, hello there!
Received: Why, hello there!
Received: Why, hello there!
Received: Why, hello there!
Received: Y'all come back now!
ok
2> usage_example:multi_start(20). % Start 20 concurrent clients
If you want to test this out locally, you'll want to generate an x509 certificate and key for localhost. This is pretty straightforward, here's an example for debian:
$> openssl req -x509 -sha256 -nodes -newkey rsa:2048 -days 365 -keyout localhost.key -out localhost.crt
$> sudo cp localhost.crt /usr/local/share/ca-certificates/
$> sudo update-ca-certificates