Mikaela/mikaela.github.io
1
0
Fork 0
mirror of https://github.com/mikaela/mikaela.github.io/ synced 2025-02-19 23:10:46 +01:00
Code Issues Projects Releases Wiki Activity

ZNC160SSL: mention overlay networks...

Browse Source 
...and how I have changed my mind on allowing invalid certificates with
them as .onions and Yggdrasil/Cjdns/Tor addresses already confirm that the
service is what I want as long as I got them from a reliable source.
This commit is contained in:
Aminda Suomalainen 2018-11-10 20:06:55 +02:00
parent 1f7c5ac12a
commit 76e1f764c1
No known key found for this signature in database
GPG Key ID: 0C207F07B2F32B67
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
_posts/2015-02-24-znc160-ssl.md
View File

@ -115,6 +115,17 @@ network.
it's own CA storage. See (and comment if you encounter this) it's own CA storage. See (and comment if you encounter this)
[znc/znc#909](https://github.com/znc/znc/issues/909). [znc/znc#909](https://github.com/znc/znc/issues/909).
* * * * *
Section added on 2018-11-10: I have started using the new option to allow
invalid SSL certificates in some cases as this post is only written with
clearnet in mind.
I am on some networks over Yggdrasil or Cjdns which already have E2EE like
Tor hidden services so as long as they are accessed directly, all benefits
of TLS are there already and TLS certificates are an additional burden as
with LetsEncrypt they will change often and LetsEncrypt doesn't support
any network I mentioned.
* * * * * * * * * *