= 27d567bc2d48d9f40e9ccc20ea370b15)
gwern comments on Anti-akrasia remote monitoring experiment - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (114)
Sharing a list of running processes and DNS lookups would be more privacy-sensitive. (I have no idea how to implement the latter, but the former could at least be done on Linux, and possibly Windows, using ksysguard) You might not want to share your screen with a random stranger, but would you share process names and DNS lookups? How about open sockets?
Process names should be safe to share, since all users on a system can see them and a system is supposed to be secure for a user even with other malicious users. No sane software puts keys or passwords into stdargs where it can be seen through a
psor something.DNS lookups should also be secure in a sense since no one in their right mind would write server software where the port/address is the key, but privacy might also be a problem. (Then again, if you are browsing FreePorn.com while doing this, maybe you deserve any consequences.)
FYI, I think on Windows you can only see processes for your user unless your user is an Admin.
Windows Vista/7 makes not running as Admin more common.
Yes, well, Windows doesn't have a very good history when it comes to supporting multiple users - not nearly as good as Unix systems, anyway. So draconian measures are to be expected.