5 ms·
It's the sensible, pragmatic thing for them to do. Allowing .onion to be allocated as a "real" TLD would just be disruptive and confusing at this point. The im
by duskwuff 11y ago
It's the sensible, pragmatic thing for them to do. Allowing .onion to be allocated as a "real" TLD would just be disruptive and confusing at this point.
The implications with regard to SSL certificates are interesting, though, and I'm curious how long it'll take for SSL providers to start supporting that. :)
- finnn 11y agoDigicert has already issued at least one certificate to a .onion address[0]. See [1] for additional info [0]: https://blog.digicert.com/anonymous-facebook-via-tor/ https://blog.digicert.com/anonymous-facebook-via-tor/ [1]: https://blog.digicert.com/the-current-state-of-onion-certificates-and-what-happens-next/ https://blog.digicert.com/the-current-state-of-onion-certifi...
- celticninja 11y agoblockchain.info also has an SSL cert on their .onion site
- buu700 11y agoFun fact: Cyph's certificate from DigiCert is the first EV cert ever deployed to a .onion address (https://cyphdbyhiddenbhs.onion https://cyphdbyhiddenbhs.onion).
- jlgaddis 11y agoWhat are the benefits to using SSL/TLS certificates on a hidden service? Perhaps a better question is: are there any benefits other than just providing an additional layer of encryption that a potential attacker would have to defeat -- there's already end-to-end encryption when using hidden services (even if there isn't any encryption at the application layer)? ETA: I just remembered that hidden services use 1024-bit RSA keys and there's been some arguments lately that that may not be enough bits. For some sites, using (at least) a 2048-bit key may be necessary.
- jandrese 11y agoWell, it would encrypt the traffic from your TOR endpoint to the application. Usually this is on the same box so it's not a big deal, but not always.
- dogma1138 11y agoAll traffic to TOR hidden services is encrypted end to end, SSL can add additional level of authentication tho. If it's not a hidden service then you can't really use an .onion address anyhow.
- jlgaddis 11y agoYou're correct, but I think his point was that the Tor endpoint (i.e. the host connected to the Tor network) and, e.g., the host actually serving up the content aren't necessarily one and the same (although they usually are). In those instances, an SSL certificate would provide encryption all the way from the "Tor client", through the Tor network, the rendevous point, Tor endpoint, and to the actual application server. Without additional encryption in use at the application layer, the link from the Tor (hidden service) endpoint and the actual server would not be encrypted and, thus, vulnerable. To (perhaps) explain better, this would be similar to how Cloudflare offers SSL for all sites and while the path from the end user to Cloudflare is (can be) encrypted, the link from Cloudflare back to the origin server isn't necessarily encrypted. Alternatively, think of the link from an SSL terminating device to the backend web servers. Again, in most cases, this is a non-issue but there certainly are some instances in which it would apply (and this is probably more likely the bigger a site (hidden service) is).
- deleted 11y ago[deleted]
- vbezhenar 11y agoEV certificates add green buttons with company names. Registrar checked that this company indeed exists and legal. So you can be sure, that you didn't mistype URL. And may be some users are comfortable with HTTPS scheme. Another concern is that major browsers might obsolete HTTP scheme, so their UI will warn user about insecure connection. I'm not sure whether browsers will be able to distinct between onion sites and regular sites in that aspect.