Lightnion: Tor in the Browser
github.com
Lightnion: Tor in the Browser
1–10 of 11 posts
Re: Lightnion: Tor in the Browser
#2So all the speed, black listing and endless unsolvable captchas of Tor but with none of that annoying anonymity!
Re: Lightnion: Tor in the Browser
#3So all the speed, black listing and endless unsolvable captchas of Tor but with none of that annoying anonymity!
tor speed is an improvement, it impedes on social network addiction :p
Re: Lightnion: Tor in the Browser
#4Could be useful for people in controlled software environments, though it would require new, special types of bridges...
Re: Lightnion: Tor in the Browser
#5Found an associated paper here: https://madweb.work/papers/paper10.pdf
Re: Lightnion: Tor in the Browser
#6javascript? URGH
Re: Lightnion: Tor in the Browser
#7Nice, this could be another way to solve the problem of hosting an anonymous website without forcing the user to install a new browser. Only needs someone to host a proxy website.
Re: Lightnion: Tor in the Browser
#8My understanding of Tor is that proxy keys are shared in a gossip network, and that without access to that gossip network you're vulnerable to being sybil attacked. How does Lightnion solve this? Or am I misunderstanding Tor?
Re: Lightnion: Tor in the Browser
#9Appears to be a public TCP-to-websocket proxy to a Tor client w/ a JS wrapper. I assume the host could be an onion service address which does have value, but you're still going through a proxy.
At that point, you might as well have your own web server side connect to Tor and do what you want, it's not hard w/ libs out there. Otherwise, if I see this on your site, I just might start using your proxy as my new tor2web, heh (not that there is real value over just my own Tor client running locally).
Re: Lightnion: Tor in the Browser
#10My understanding of Tor is that proxy keys are shared in a gossip network, and that without access to that gossip network you're vulnerable to being sybil attacked. How does Lightnion solve this? Or am I misunderstanding Tor?
There's a consensus made on the global state of the Tor network made between several well-known parties: just as a regular Tor client, Lighnion downloads the consensus document, parses it, validates its signatures and perform a path selection algorithm on it. It's several megabytes to downloaded by the Javascript client (itself being few kilobytes) and is currently a limitation of the protocol.
If the "walking onions" proposal gets maintstream (i.e. private retrieval of a consensus subset), we can hope for improvements (see https://gitweb.torproject.org/torspec.git/tree/proposals/300...).