sshttp SNI proxy trickery

The sshttp protocol muxer has been updated to support
SNI muxing. When muxing SSH/HTTPS, the ClientHello message
of the TLS handshake may contain a SNI, which is parsed by
sshttpd  and can be routed to an alternative port (rather than to the regular https port specified with -H).
This is of particular interest with the drops p2p network,
as it is using TLS with the SNI of drops.v2.
This way you can hide sshd and drops behind your https server.

Drops trickery

In the past months I have been working on a project
for a distributed p2p messenging platform, featuring
the opmsg format. opmsg is usually attached to emails.
Emails however leave meta data traces such as email addresses and
header content. Not so with drops, which is ready for testing !

As its a p2p network, it lives from participating people.
So even when you dont use opmsg yourself, you can setup
a drops node so the network gets more distributed and
stable.

Its now in beta testing, and some features such as
sandboxing are yet missing.

Dont be worried by the spartanic README, it will get
updated and there will also be a document describing
the techical details.