News for hackers. Stuff that matters.
Re:Onion names reserved by the IETF by johnmaguire2013 on Wednesday October 28, 2015 @02:32PM (#10466346)
I believe the exit node may still be able to view traffic in plaintext. This is part of the reason that running an exit node is so "dangerous" in the US.

edit: Though with a quick Google, I'm led to believe that an exit node is only important when you are leaving the onion network (i.e. when entering into the Internet), and thus it sounds like SSL on a hidden service would indeed be superfluous to me.

However, SSL also proves authenticity, not just encryption. It would let you know that the hidden service you are accessing is indeed who you think it is.

Re:Onion names reserved by the IETF by icebraining on Wednesday October 28, 2015 @02:58PM (#10466501)
However, SSL also proves authenticity, not just encryption. It would let you know that the hidden service you are accessing is indeed who you think it is.

So do .onion address; they are an hash of the key pair you get when you generate a new one, and the client verifies that the server it's connecting to does in fact control the associated private key.

By abdicating readable domains, the Tor hidden services system eliminates the need for external authentication mechanisms like CAs; the address is all you need.

https://www.torproject.org/docs/hidden-services.html.en

Re:Onion names reserved by the IETF by johnmaguire2013 on Wednesday October 28, 2015 @03:36PM (#10466769)
Assuming a .onion's key were to be bruteforced or stolen however, you would also need to steal the SSL private key in order to continue to appear authentic.

I'm not saying Tor doesn't cover authenticity, but that SSL provides an additional authenticity check on top of that.

edit: On the topic of bruteforcing, the linked Stack Overflow post leads me to believe it's not terribly infeasible.

Additionally, stealing the .onion's key would likely expose the SSL private key as well (as you'd likely have access to the server at that point), unless the .onion's key is exposed due to misconfiguration or another form of human error.

I also think, lastly, that the point about the browser understanding its dealing with a secure connection and enforcing general browser SSL rules has merit.

edit 2: Forgot the link - https://security.stackexchange.com/questions/29772/how-do-yo...

Re:Onion names reserved by the IETF by ikeboy on Wednesday October 28, 2015 @11:56PM (#10469184)
14:2.6 million years
Re:Onion names reserved by the IETF by johnmaguire2013 on Friday October 30, 2015 @05:00PM (#10480515)
With a single core.
Re:Onion names reserved by the IETF by ikeboy on Monday November 02, 2015 @02:05PM (#10494209)
So a million cores still takes years. What would you consider infeasible, may I ask?

Also, you're wrong about bruteforcing the domain implying you can decrypt if not for ssl. If you bruteforce (for millions or billions), you won't get the same key. You'll get a key that shares the first 80 bits of its hash with the other key used. So you can use it to mitm or impersonate the site, but you can't use it passively to decrypt connections to the onion.

Re:Onion names reserved by the IETF by mnx on Wednesday October 28, 2015 @03:41PM (#10466810)
Aren't bruteforces of .onion plausible in the mid-future by powerful actors?
Re:Onion names reserved by the IETF by Natanael_L on Wednesday October 28, 2015 @05:37PM (#10467610)
That's why the Tor project is planning a cipher suite upgrade in the near future
Re:Onion names reserved by the IETF by noondip on Wednesday October 28, 2015 @02:40PM (#10466393)
Exit nodes are not involved when making connections to Hidden Services. See https://www.torproject.org/docs/hidden-services.html.en
Re:Onion names reserved by the IETF by johnmaguire2013 on Wednesday October 28, 2015 @02:49PM (#10466446)
I edited my comment a minute after posting to reflect that. Thanks.
Re:Onion names reserved by the IETF by banthar on Wednesday October 28, 2015 @02:37PM (#10466369)
That's onion -> web. If you are connecting to onion address, your packets do not enter plain text internet. Unless you are using some sort of "enter node".