hey guys, anyone believes Tor still can provide anonymity to users ? just trying to ask politely.
Counter Galois Onion: Improved encryption for Tor circuit traffic
11–20 of 34 posts
Re: Counter Galois Onion: Improved encryption for Tor circuit traffic
#12hey guys, anyone believes Tor still can provide anonymity to users ? just trying to ask politely.
High stakes (military / nation state scale): no
Re: Counter Galois Onion: Improved encryption for Tor circuit traffic
#13hey guys, anyone believes Tor still can provide anonymity to users ? just trying to ask politely.
broadly yes, but the real question is: what's your threat model? https://ssd.eff.org/glossary/threat-model
Re: Counter Galois Onion: Improved encryption for Tor circuit traffic
#14hey guys, anyone believes Tor still can provide anonymity to users ? just trying to ask politely.
This FUD comes up whenever Tor is mentioned on Hacker News. The answer is: let's say you think Tor isn't 100% flawless. What are you going to do? Not use Tor? It's better than any other option.
I've been writing a system like this in Erlang, intended to be short enough that you can take a picture of the source code and then type it in by hand in a reasonable amount of time, as a sort of protest against Chat Control. I'm not sure I'm going to release it-- after all, they haven't passed it yet, and there are all sorts of problems that this thing could needlessly accelerate, but I've started fiddling with it more intensively recently.
Re: Counter Galois Onion: Improved encryption for Tor circuit traffic
#15Earlier quoted context omitted.
This FUD comes up whenever Tor is mentioned on Hacker News. The answer is: let's say you think Tor isn't 100% flawless. What are you going to do? Not use Tor? It's better than any other option.
What you'd do is that you'd write a distributed remailer where fixed-size messages are sent on fixed timeslots, possibly with some noise in when it's transmitted, with a message always being sent on its timeslot, even if a dummy message must be sent. I've been writing a system like this in Erlang, intended to be short enough that you can take a picture of the source code and then type it in by hand in a reasonable am…
Except that every user is also a node, thereby mixing their personal traffic into a share of network traffic. Or so I understand it.
Re: Counter Galois Onion: Improved encryption for Tor circuit traffic
#16Earlier quoted context omitted.
What you'd do is that you'd write a distributed remailer where fixed-size messages are sent on fixed timeslots, possibly with some noise in when it's transmitted, with a message always being sent on its timeslot, even if a dummy message must be sent. I've been writing a system like this in Erlang, intended to be short enough that you can take a picture of the source code and then type it in by hand in a reasonable am…
Don’t things like Freenet do similar? Except that every user is also a node, thereby mixing their personal traffic into a share of network traffic. Or so I understand it.
My target size is also <500 lines, and I think <200 is feasible, whereas Freenet is apparently 192,000 lines.
Re: Counter Galois Onion: Improved encryption for Tor circuit traffic
#17Cool! Congrats! Awesome work. Small typo: “observing predicatable changes“
Re: Counter Galois Onion: Improved encryption for Tor circuit traffic
#18Cool! Congrats! Awesome work. Small typo: “observing predicatable changes“
I think you’re getting downvoted because you’re reporting the typo in an odd and likely unproductive place. I’m not sure what you expect HN readers to do about the typo. There is a comment section on the blog itself :)
Re: Counter Galois Onion: Improved encryption for Tor circuit traffic
#19Why is this necessary if every layer of the onion is a trustable encrypted link?
Re: Counter Galois Onion: Improved encryption for Tor circuit traffic
#20Earlier quoted context omitted.
I think you’re getting downvoted because you’re reporting the typo in an odd and likely unproductive place. I’m not sure what you expect HN readers to do about the typo. There is a comment section on the blog itself :)
It's not unusual that the author (or someone of the team) see the trafic peak an appears in HN to reply the questions.
But instead of just reporting it directly, we instead get this unsubstantive comment (“Cool! Great! Btw you spelled a word wrong.”). Essentially just noise, nothing that provokes curiosity or interesting discussion.