7 ms·
another comment here rightly pointed out that what we want is to protect our files from being read by unrelated processes. there are no good implementations of
by nathants 4y ago
another comment here rightly pointed out that what we want is to protect our files from being read by unrelated processes.
there are no good implementations of this yet to my knowledge. encrypted fuse with snitch like rules and prompts is probably the play.
any network snitch program would have caught this and prevented exfill. a prompt would have been displayed for a new connection to sketchy.io udp 53. from pytorch or some child process. most eyebrows would rise. many requests would be denied.
on mac you have little snitch and at least one foss alternative. on linux you have opensnitch, or can roll your own on libnetfilter_queue[1] or lsm hooks[2].
hopefully soon somebody implements encrypted fuse snitch. until and even after then, wrap yourself in network snitch safety blankets and feel warm and cozy.
1. https://github.com/nathants/tiny-snitch https://github.com/nathants/tiny-snitch
2. https://github.com/nathants/mighty-snitch https://github.com/nathants/mighty-snitch
- cozzyd 4y agoI'm curious if SELinux as configured by default on Fedora/EL would prevent reading private ssh keys. I guess pretty easy to test...
- nathants 4y agoanything without interactive notifications will need restrictive rules, but should work. ufw preventing all udp 53 to anywhere but 1.1.1.1 might have worked. it’s the raised eyebrows that are the most important part. ttre, time to raised eyebrow. random network nonsense should not pass invisibly.