100 karma · joined August 29, 2019
I’d rather give a dollar to the local homeless shelter and watch them burn fuel with it at night, than my cent going straight to corrupt governments and militias.
https://web.archive.org/web/20180504001844/https://8ch.net/b...
Yes, people would rather give their entire packet to a hacker than five eyes, wouldn’t they?
Also I’ve convinced my company to run nodes with their VPS credit. 6 nodes, 30GB per day per node. It costs them 30$.
The fundamental question is: why not implement this stupid feature in the first place?
It’s even not that hard to implement, it’s just they are valuing their stupid politics and philosophy over user experience.
I’m trying to think but so far there seems no way to justify limiting searches.
But remember: What tor is doing is hard. They are doing complex crypto, networking, security.... The hard stuff. The real stuff. Torproject is a nonprofit organization with limited capabilities. They are doing their best. It took 3 years to design and implement dos mitigation techniques, for example.
Your proposed plan could take over 10 years, even for a well funded corporation. It might take time and fail. It might create huge vulnerability due to code complexity. Afaik, tor can’t risk that.
From tor blog:
A new relay, assuming it is reliable and has plenty of bandwidth, goes through four phases: the unmeasured phase (days 0-3) where it gets roughly no use, the remote-measurement phase (days 3-8) where load starts to increase, the ramp-up guard phase (days 8-68) where load counterintuitively drops and then rises higher, and the steady-state guard phase (days 68+).
Second, to anyone crawling hidden services or crawling over tor, please run a relay or decrease your hop. Don’t sacrifice other’s desperate need for anonymity for your $whatever_purpose_thats_probably_not_important. It could be some fun thing to do for you, but some people are relying on tor to use the free, secure and anonymous Internet.
Maybe respect others privacy before using the ‘democracy and freedom is at stake’ rhetoric.
And blocking https packets with mere confidence is impossible.
Think DNS over TLS. Okay. You think $ip:$port is a dns connection. You send query with DoT protocol. You get answers. Bingo! It’s DNS.
If it’s DNS over HTTPS, you can’t tell. What domain(dns.quad9.net or cloudflare-dns.com or dns.google or whatever you can imagine) is it? What endpoint and method(/dns-query?url= or whatever you can imagine) is it? You can’t tell.
HTTP adds complexity. Complexity adds security.
Your explained method is nearly impossible to implement for medium to large scale networks.
DNS over TLS can be easily blocked by blocking port 853. To block DNS over HTTPS you need to block the entire HTTPS traffic.
I can’t understand this move. Firefox should retreat from this default.
Don’t get me wrong, I use Linux extensively. I spend nearly half of my computer time on a SSH terminal. I just hate the graphical part of it.