33 ms·
This makes me wonder, is it easy enough to write a kernel extension such that whenever any process that tries to open(2) my ssh private key, or any hardlinks or
by kccqzy 10y ago
This makes me wonder, is it easy enough to write a kernel extension such that whenever any process that tries to open(2) my ssh private key, or any hardlinks or symlinks pointing to it, it checks against a known whitelist, and if the process is not in the whitelist, a dialog pops up and asks me for my permission. Is this easy to implement?
Frankly I can only think of a small number of processes that need to automatically access the file: backupd, sshd, and Carbon Copy Cloner. Everything else should require my attention.
- lloeki 10y agoAlternatively, sidestep open(2) by implementing a SSH agent so that you can do creative things like https://krypt.co https://krypt.co does, so the key is not laying right on your main filesystem in the first place (and possibly not even ever on the workstation).
- deleted 10y ago[deleted]
- j_s 10y agoGood idea! Talk to this guy: https://objective-see.com/products.html https://objective-see.com/products.html
- sneak 10y agoIt's called Little Flocker. Essential OSX software. Looks like F-Secure just bought it in the last month or two. :(