class PacketThief::Handlers::SSLServer

Basic SSL/TLS Server built on Ruby’s OpenSSL objects instead of on EventMachine’s start_tls. This allows you to manipulate the SSLContext and other details of the connection that EM normally doesn’t let you touch.

Subclass it and override any of the methods in the following example to use the the functionality.

You can send_data to send encrypted data to the other side, and receive_data will be called when there is data for the handler.

EM.run {
  # Leave the hostname blank for Linux's netfilter.
  SSLServer.start '', 54321 do |p|

    # Note: this code block is actually too late to set up a new
    # #post_init since it runs just after post_init. Instead, you would
    # use post_init in a subclass.
    def p.post_init
      # modify p.ctx to configure your certificates, key, etc.
    end

    # In this example, the following would work in this initialization
    # block:
    h.ctx.cert = cert
    h.ctx.extra_chain_cert = chain
    h.ctx.key = key

    def servername_cb(sock, hostname)
      # implement your own SNI handling callback. The default will
      # return the originally configured context.
    end

    def p.tls_successful_handshake
      # the handshake succeeded
    end

    def p.tls_failed_handshake(e)
      # the ssl handshake failed, probably due to the client rejecting
      # your certificate. =)
    end

    def p.unbind
      # unbind handler, called regardless of handshake success
    end

    def p.receive_data(data)
      # do something with the unencrypted stream
      p.send_data("some message") # data to be encrypted then sent to the client
    end

  end
}

Note: During initialize and post_init, this class does not have access to its socket yet. Instead, use tls_pre_start or the code block you pass to .start to initialize the SSLContext, and use tls_post_accept to do anything once the SSL handshake has completed. You can also override servername_cb to perform the SNI callback.