TOR is compromised

Browser Requests: d2nxq2uap88usk.cloudfront.net firefox.settings.services.mozilla.com ec2-52-35-220-92.us-west-2.compute.amazonaws.com ec2-34-242-33-12.eu-west-1.compute.amazonaws.com server-13-33-240-52.hel50.r.cloudfront.net Links (Ironically Cuсkflared) https://archive.fo/zrNov https://archive.fo/II2BU https://archive.fo/T9m3m https://archive.fo/x6XnQ https://archive.is/OCJEx https://www.ieee-security.org/TC/SP2013/papers/4977a080.pdf https://anonfiles.com/h4EdLdw5u6/4977a080_pdf

How about you actually explain your point instead of expecting people to click on a bunch of links/PDFs?

For those of us with less time to spend or no inclination to actually open arbitrary PDFs from this site, could you at least bother to include a summary of what you're talking about in your OPs. It isn't that hard. That paper has a DOI, fuarrrking provide it. DOI:10.1109/SP.2013.15 And yes, this is old news. 2013.

I'm really hoping Nym takes off. It would be awesome for everyone to shift to a network where global adversaries are part of the threat model from day one.

>>15809 I'm very skeptical of anything which involves cryptocurrency-like incentivization systems.

>>15810 Same. Speaking of which:do you think crypto has any use besides the nonsense currently going on? At least monero fulfills its purpose as a digitak currency, but it has the same scalability isues as the otehr soykafcoins.

>>15811 I don't think so. As far as I understand it, the problems in cryptocurrencies in terms of efficiency are pretty much inherent to any multiple-writer distributed system that can't allow arbitrary writes. For partly-anonymous transactions there's GNU Taler that is somewhat promising and far more energy-efficient and scalable, but it does so at the cost of not being distributed.

>>15811 continuing >>15812 Oh right, I should mention that I mainly responded to the currency aspect, as I view the exchange-rate gaming/gambling to be a drawback or design flaw, rather than a legitimate use.

>archive.fo Nice pigchan crosspost. Upload to proper archive first if you want to be taken seriously.

>>15812 >>15813 makes sense. Anything interesting outside of the currency aspect? Interesting things I picked up: metanet... and that's it. Of course some industry use-cases (eg. shipping verification), but nothing that makes crypto essential, mostly corporations being entrapped by hype. I don't buy into NFTs either, although the idea is genius for a cash grab. it's even genius as a concept. But it doesn't really do what it claims to do: the proof of ownership isn't really more worth than ye good ole signature. The distributed aspect, since it's on the blockchain, is a certain benefit, but I am not impressed.

>>15814 What archive site? .org is hot garbage

>>15827 As long as it: 1. does not ask to solve captcha on almost every visit 2. links don't look like click farming shortener garbage, provide clear indication what web address is archived without visiting 3. most pages retain accessibility without JavaScript, as well as some miniature single-page JavaScript applications are preserved for future offline use 4. provides direct download for any kind of saved file, not just images, styles and markup it is not a "hot garbage" as you have phrased it. Archive.today is a smaller amateur project, so it's obvious they can not cater to all users, and have to resort to poorly configured Cloudflare even on their onion domain forbidding Tor and public data center IP address users (public proxies and most commercial VPNs-as-a-service) to jump trough ridiculous humiliating hoops. However, OP is clearly an uninformed fedchan crossposter who does not know three crucial things: - Tor is spelled this way - Archive.today page saving interface provides option to include source page address instead of short link, and Internet Archive does it by default - Every published scientific paper has a searchable number, so we can look it up independently of sources OP has provided

>>15828 Literally zero if you bitch and moan about your pre-requisites no archive sites brother.

>>15828 Most of these sites came from TOR git itself (And no I will spell it like if it was and acronym fuarrrk you.

>>15804 it had always been compromised ever since that one guy funded the project and after a core developer had to quit due to "muh rape".

>>15834 Please expand on this. Thank you.

>>15839 He probably means IOError. What do you need to expand?

Nothing is 100% anonymous. There will never be a safe place to carelessly browse. Assume everything is compromised and always tread carefully. This is nothing new.

>>15810 I'd rather have something with that much overhead incentivized. It's going to be a lot more resource intensive than Tor. The low number and lack of diversity in Tor nodes is quite disturbing. >>15811 Scalability in Monero is much better than other trustless coins due to dynamic block sizes and chain pruning. I don't like the electricity use in Monero, but unfortunately I don't see much as far as viable alternatives go.

>>15804 >Cloudfront & Amazon servers in connections list Did you configure Tor Browser to use Meek bridges? That could explain it, cuz Meek relies on domain fronting, and usually, servers of these companies are not blocked. Don't like it? Switch to obfs4.

>>15855 Oxen seems promising, but it's too early to say.

>>15804 Not recommended. I won't even touch that purple browser. >can crash dump on its own or crash itself to activate your system's crash dump which were mentioned in the docs >plenty of wikileak etc. crap confirming it does oopsies and poopies >had plenty of intentional "oops" during a ESR version switch where even the users warn others from making the switch/update >bridges/nodes whatever are all big megacorps >doesn't even jump 7 or more proxies The browser isn't recommended but the network, maybe, along with a headless browser or manage the entire connectivity but in general anonymity isn't as basic as just opening up a box and pressing three buttons. You'll have to do better than that but whatever comes after is well-deserved.

>>15843 >Assume everything is compromised and always tread carefully. This really should just be common practice at this point. Not to veer off topic, but I've been convinced the Linux kernel has some kind of NSA tracker in it. Granted, I'm well aware how the kernel is audited, but I remain convinced. The Linux kernel has around 27.8 million lines of code in its Git repository, up from 26.1 million a year ago, while systemd now has nearly 1.3 million lines of code, according to GitHub stats analysed by Michael Larabel at Phoronix. That's A LOT of code to audit.

>>15904 I think you're just paranoid about it. I mean we have multiple groups of security experts, watchdogs and users like you so the odds of it is really really LOW.

>>15905 the nsa has all of those too

>>15904 an outright tracker would be very hard to insert in any codebase. but i'm sure they managed to slip some kind of backdoor that isn't obvious at first glance, or at fifth glance. which means that your process table is probably not actively monitored by the NSA or something, but if they wanted to target *you* specifically, they could probably exploit that vulnerability easily

>>15906 Yes. They have the freedom to act as secure just like you.

>>15904 if they did some complete sperg would have found it by now

>>15901 They explicitly stated that global adversaries are not in their threat model. In my opinion that makes it dead on arrival.

As a general rule anyone who writes TOR doesn't know what they're talking about. https://support.torproject.org/about/#why-is-it-called-tor

>>15908 >>15904 If you use gnome and gnome related stuff yes. look up at-spi >>15908 It's not even an outright tracker at this point since your processors be it Ayymd or Intel-igenceAgency both have ring negative and currently with the modern standard EFI enables the ring negative be interfaced over ring 0,1,2,3 insecurely so it's just as easy as having one vulnerability on bind/unbound and voila, combine with the fact they now standardized pipewire so it's so fuarrrking easy now to turn your distro to be RAT or RDP-infested might as well be using windows with RDP since it's pretty much the same, oh don't forget those weird ass opus webm and webp soykaf that has issues with crashing and possibly remote execution from the only two browser standard, might as well spell it out yourself "I am pwned by them, I am cattle".

>>15940 So what you're saying is we should reimplement all media decoders in memory-safe languages? That sounds reasonable.

>>15919 Jokes on you. The in crowd writes it TOR now to filter out the posers. Keep up.

>>15804 OP the PDF you included is for an ancient version of TOR...

>>15908 There's a bunch of kernel vulns. The more code they add, the more vulns.

>>15908 >backdoor Why would they ever need that? The NSA can deanonymize you passively with a correlation attack, since a global adversary is not within their threat model.

kek just change the hosts file to redirect the traffic to localhost

>>15855 > I don't like the electricity use in Monero Makes sense why you don't like incentives. Imagine not being alive you illogical buffoon. Dumbest mindset ever.

>>16216 What kind of word salad are you vomiting here? Inefficiency is undesirable in essentially all cases regardless of the possibility of offsetting its monetary cost.

I don’t want to give off “I know it all vibes” but some people here need to read this. There is not such thing as being fully 100% private on the internet. There are ways that you can ensure your anonymity however that depends on how good you are at what you’re doing. If you are looking to do something illegal (I advice against that) I suggest getting gud. Take of that what you will. As for tor being compromised, The browser itself is just trash to be honest. The network itself does work pretty well. tor on its own won’t magically make you fully anonymous; look up how the Silk Road guy got caught. You need to know your soykaf and have really good Opsec. If the NSA had some sort of a backdoor on the network it would’ve been way more swift than that. They instead fill up the entire fuarrrking network with honeypots. That’s all you need to know. Speaking of triple letter agencies, when it comes to intel me or amd PSP a lot of script kiddies don’t know why these actually exist. I suggest reading more. They do present a security risk however the main concern I see is “MUH NSA”, let me ask you something; how will the fuarrrking NSA activate that soykaf if you’re good enough that they didn’t even fingerprint your hardware? How will they activate it when they don’t even know where the fuarrrk you are? That’s like having a magical universal key and are presented with 100 million doors, you are then told there is a giant golden goat behind ONE of the doors. Get it? If you allowed the NSA to figure out where you’re at and fingerprint your hardware in the first place then you’re simply not good enough. The NSA has more efficient ways to pawn you anyways. If they’re your threat model then you need to be REALLY good and read a lot. You also HAVE to get really comfy with networking and other technical stuff. in the Snowden leaks he showed that the NSA prefers to pawn your ENTIRE network not just one of your devices… And use i2p. Also, watch this: https://youtu.be/zXmZnU2GdVk And this: https://youtu.be/6Chp12sEnWk I do not underestimate the NSA and I do acknowledge the fact they have an insane stockpile of Zero-Days BUT, your best bet is not to leave a trace. How are they going to exploit something when they don’t know wtf is it? If the agent doesn’t have a clue about your hardware or location you’re nothing but a ghost. God knows you might be using a Macbook on your end lmao. How can you become a ghost and be a FANCY HACKER MAN 1337 running kali on your smart fridge? Lurk more. Read more. Code more. Ask more. Get technical. Lurk more. Where to lurk? On the forums, Especially the i2p ones. Which forums? Idk what you’re talking about.

>>16484 Thread is over. There is nothing to do but to READ. Read academic articles, read books, even contribute tot he things you use to erase your trace.

Ten billionth tor is compromised thread, I'm not reading your fuarrrking PDF at least give a tldr if you're gonna do this soykaf

There is also [this][0] which has become an ever worsening problem since a little while now. >>16484 I2P isn't magic and is [vulnerable to timing analysis][1], it just fares a lot better than Tor due to having a much better architecture. [0]: https://www.techdirt.com/articles/20210824/07122747419/isps-give-netflow-data-to-third-parties-who-sell-it-without-user-awareness-consent.shtml [1]: https://geti2p.net/en/docs/how/threat-model#timing

>>15812 Where can I find a technical description of Taler's principles and ways it implements them?

>>17362 I think these links would provide a start. https://docs.taler.net/ https://taler.net/en/principles.html https://taler.net/en/features.html

>>17363 cont I should've included https://taler.net/en/faq.html It answers the question for example of how it implements privacy protection without having to read the whole spec.

This paper is from 2013 and describes techniques used to do various undesirable things to v2 hidden services. v3 onions don't suffer from any of these vulnerabilities. There is endless dumb FUD about Tor from people who don't know what they are talking about.

That's the browser's problem, not Tor itself. If it bothers you so much why not use Tor with Lynx.