commit 4c648889e0e8866f3f4f532771806480f8c9c67c
Author: gus <[email protected]>
Date: Fri Jun 25 12:31:03 2021 -0300
Minor fix
---
content/onion-services/advanced/https/contents.lr | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/onion-services/advanced/https/contents.lr
b/content/onion-services/advanced/https/contents.lr
index 4641444..b3166c8 100644
--- a/content/onion-services/advanced/https/contents.lr
+++ b/content/onion-services/advanced/https/contents.lr
@@ -25,7 +25,7 @@ No certificate authority is required for this proof, because
that name is the ac
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](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.
+- [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
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
