...Which data do you think needs to be encrypted using SSL and thus be protected from the node operator...
you keep bringing this up. but the node operator gets the correlation data, regardless of if ssl is or is not used. Besides,Its not the node operators that I need anyone is concerned with.
Can you please name what you are trying to protect with SSL? Is it transaction data? Is it the accountSecret parameter in URLs? Is it the IP number of the NXT client end user? ...EDIT: I've read your post again and I think you are trying to protect the IP of the NXT client end user...
With Tor, neither the exit node operator nor the NRS node operator know the IP address of the end user.
It is the correlation data between account/IP address. Your point where you state "With Tor, neither the exit node operator nor the NRS node operator know the IP address of the end user." isnt true for all cases of all time - this is why I referenced the near-impossible requirements of an end user implementing tor correctly in some previous posts. When it comes down to it, tor isnt a simple 100% obfuscated cloud with a user on 1 side and a random exit node on the other. The research shows the correlation is possible unless the user never uses the same home location. Perhaps whoever does your research paper bounty offer will provide more info for you on this.
I think there was a link posted in the firehose thread that had a fairly good description on the "proper" use of tor, and the near-impossible method of proper implementation, but given that firehose thread, I dont think Ill be able to find it.