commit a6c4c4ce29b1d442ace5fccb015b05c06680d18b
Author: nyxnor <nyx...@protonmail.com>
Date: Fri Jun 25 15:21:32 2021 +0000
Update contents.lr
---
content/onion-services/advanced/https/contents.lr | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/content/onion-services/advanced/https/contents.lr
b/content/onion-services/advanced/https/contents.lr
index c49fd7a..196b9e8 100644
--- a/content/onion-services/advanced/https/contents.lr
+++ b/content/onion-services/advanced/https/contents.lr
@@ -23,7 +23,9 @@ When visiting a site over the onion services protocol, the
Tor protocol prevents
No certificate authority is required for this proof, because that name is the
actual public key used to authenticate the underlying connection.
As ".onion" is a [special top level domain
name](https://tools.ietf.org/html/rfc7686), most Certificate Authorities don't
have support for issuing X.509 certificates for onion sites.
-Right now, HTTPS certificates are only provided by DigiCert with an Extended
Validation (EV) TLS certificate, which means a considerable cost for an
organization.
+Right now, HTTPS certificates are only provided by
+- [DigiCert](https://www.digicert.com/) with an Extended Validation (EV) TLS
certificate, which means a considerable cost for an organization.
+- [Harica](https://www.harica.gr) with Domain Validation (DV) TLS certificates.
That said, there are some specific cases where you would need or want to have
an HTTPS for your onion site.
_______________________________________________
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
