4 ms·
I get an invalid certificate, as the root ca is ca.cypherpunks.ru, which is not trustworthy. You might want to look into that, because I like the idea. :)
by MrGilbert 6y ago
I get an invalid certificate, as the root ca is ca.cypherpunks.ru, which is not trustworthy.
You might want to look into that, because I like the idea. :)
- clarry 6y agoI also like the idea of being my own CA instead of pretending a bunch of random companies are trustworthy.
- rakoo 6y agoWhat's the point ? This effectively makes the whole encryption worthless, might as well serve your site in plain HTTP
- KCUOJJQJ 6y agoThe visitor cannot be sure that he really is connected to git.cypherpunks.ru. But doesn't encryption work anyway?
- rakoo 6y agoEncryption is active with a host you don't know. It's TOFU, which is OK if you can verify the identity through persistent uses (ie with SSH you'll have connections with the same server over a long period of time, or with IM you'll talk to those people over a long period of time). In the case of HTTP you'll only get the content now and potentially not visit the site anymore for a long time, especially if it's a personal site. A few years ago self-signed certificates made some sense, today with Let's Encrypt there is absolutely no good reason to continue doing this on the open web