>>5242
Everything between the hydrus client and server now works on https with self-signed certificates. This means all traffic is encrypted, but no verification occurs. This isn't as good as I would like, but it covers most scenarios. The guy listening to your traffic at a wifi cafe won't be able to see what you are doing, but a hypothetical government that has full access to your ISP and infrastructure to perform a man-in-the-middle attack would be able to attack it.
I'd like to add certificate verification in a future network update. I'll write a new service that works as a certificate authority and a bit of gui so you can review and manage the certificates your client knows about and trusts. I also have to update some behind-the-scenes connection code to support this.
If you are interested, going to:
https://hydrus.no-ip.org:45871/
Should load up a welcome page for my PTR. You'll be asked to add the certificate exemption first in your browser (precisely because it is self-signed). Viewing that cert should give a SHA-256 fingerprint of:
D9:19:E8:44:65:C8:E8:B9:DF:19:7C:C3:A7:3A:E9:26:07:DD:47:A7:04:8B:AC:7C:76:D3:03:51:B9:78:0B:DA