Posted: 2014-12-08 20:26
-----BEGIN PGP SIGNED MESSAGE-----
I just enabled https for LCWO.net, which means you can now optionally connect using an encrypted connection to https://lcwo.net/.
The certificate for the site (SHA1 fingerprint FC:A2:A8:7B:E7:9D:C0:E8:D6:C6:3A:16:1D:4C:E9:CC:0D:A6:82:ED) is self-signed, which means that your browser will most likely give you a warning message when you first connect to it. Depending on your browser, it will take a few clicks to add an exception for LCWO.net and accept the certificate.
Using https may be a good idea when you're accessing LCWO.net from a network you do not trust (such as an open wifi in a public place), at your work place (during your lunch break, of course), or when travelling in strange places. Or just because you can.
The connection to the servers providing the audio are still unencrypted; I am going to add encryption to those at a later stage.
If you're using the encrypted site, please let me know if you encounter any problems, warning messages etc. Thanks!
(Message signed with my PGP key B77621F7, so you can verify the certificate's SHA1 fingerprint, in case you're as paranoid as I am.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----
Posted: 2016-05-20 05:12
wäre es möglich, das selbstsignierte Zertifikat durch eines von Let's Encrypt zu ersetzen? Dann gäbe es auch keine Fehler mehr in Browsern.