Hi Oli,
On 2019-12-13 22:46:44, you wrote to me:
WV>> But it seems to work. Can anyone test my node? TLS/SSL connects to my
WV>> binkd for node 2:280/464 should go to fido.vlzn.nl:24553
Ol> It works.
Thanks for testing! ;)
Ol> I will use it for all connections to your node from now on. Let's see
Ol> how stable it is (I don't expect any problems).
Me neither: The config is set, so it should survive a reboot; a cronjob is
active to renew my letsencrypt certificates...
But I don't see it's absolute usefullness. Because binkd already encrypts
(most) sessions. Only the initial connection setup is unencrypted. But that
only contains already public information. Maybe if you live under a really
surpressive regime, and you want to hide the fact you are communicating in
fidonet? Maybe it helps a bit... But not if they take a closer look, at which
IP's you communicate with all the time...
Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)
|