sporksmith
Joined 17 years ago
Joined 17 years ago
ie the annoying way that LLMs interact with users
> The switch is useless in either of these threat models:
> To prevent cell tower triangulation, you can simply enable airplane mode and it is just as effective.
Folks interested in this space might also be interested in the system I spend most of my time working on: Shadow. It also performs deterministic simulation of a network of hosts, but it intercepts network and system interactions at the syscall level via seccomp. As such it can work with binaries compiled from ~any language, usually without any code modification or special compilation. https://shadow.github.io/
On recent Linux distros, by default you can't ptrace (or read memory via /proc/x/mem etc) of non-child processes https://www.kernel.org/doc/html/latest/admin-guide/LSM/Yama....
When I started long boarding at ~38, I practiced throwing myself into a roll first from a crouch, then standing, then standing on the board - onto grass of course. It helped a lot when I did inevitably have unplanned falls on the pavement.
The example I'm most familiar with, because I work on it, is Shadow. We used ptrace for a bit but now use seccomp.
For when I'm feeling very self conscious I have a script that turns off echoing to the terminal and streams everything I write to the clipboard (in case I decide I want to review/save after all)
The larger concern for deanonymization is typically flooding the network with relays, since it increases the ability to do e.g. timing-based de-anonymization attacks. This is a bit of an arms race. As @ajvs points out though, the known cases of tor users being de-anonymized were not due to attacking Tor itself, but via other channels. I'm not aware of any known real-world cases of users being deanonymized by attacking or analyzing Tor itself, let alone users being "arrested regularly"
As always it's probably a good idea to reach out to chat about what you have in mind before getting too far with implementation. #tor-dev on OFTC IRC (bridged to Matrix)
https://www.torproject.org/contact/ https://blog.torproject.org/entering-the-matrix/
The community does a lot of active monitoring to kick out misbehaving relays. "Misbehaving" includes running multiple relays without correctly setting the family attribute to identify them as being run by a single entity.
The main danger of malicious exit relays beyond other relays is that they perform some man-in-the-middle active attack. This is largely mitigated by end-to-end encryption. Tor Browser will soon be HTTPS only (other than explicit manual overrides) to help avoid inavertent non-e2e protected connections.
More in another recent blog post: https://blog.torproject.org/malicious-relays-health-tor-netw...
The lead dev on this feature, who also wrote the blog post, is taking some well deserved r&r after getting this feature out the door. I was somewhat tangentially involved (I work on the Shadow simulator, which we used to test, evaluate, and tune this feature) but can take a stab at answering questions.
Otoh comments on the blog post itself are likely to be seen by more experienced tor devs than myself :)
Disclaimer: am a Tor developer and employee.