Quote from: rjk on June 27, 2012, 05:16:33 PM

Quote from: jl2012 on June 27, 2012, 05:14:18 PM

Quote from: rjk on June 27, 2012, 05:09:14 PM

I know you meant that, and you are incorrect. The private key of the SSL certificate is stored on the .onion site, not on the torwallet.net server. Perhaps you should look closer at how socat works: it has the option to serve up its own certificate, but that is not in use here. It is simply concatenating data between ports 443 and 9050, in both directions.

I mean the private key of the SSL certificate of torwallet.net, not the SSL certificate of the .onion site ......

The SSL private key for torwallet.net is stored on the .onion server, and the .onion server does all the encryption and decryption. That's why it's a little slow; all the traffic must pass through tor first to get to and from the remote .onion server

torwallet.net does not have a private key of its own stored on it or in use for it.

This is exactly correct. We actually posted the incorrect socat command earlier so that may have led to some confusion. This is what we are actually using, pasted straight from the torwallet.net server.

socat TCP4-LISTEN:443,fork,su=nobody,reuseaddr SOCKS4A:127.0.0.1:nci2szjrwjqw2zbi.onion:443,socksport=9050

The torwallet.net server does not decrypt the SSL session, it only forwards encrypted data between the .onion and the client.