3 ms·
There is a native way in .ssh/config. I just added a reply to a different post.
by Hnrobert42 6y ago
There is a native way in .ssh/config. I just added a reply to a different post.
- mfontani 6y agoThat only restricts the blast radius to one key. One is unawares of when, how, and for what purposes that key is used - as forwarding the key means it's available for use by any user process (as the mechanism behind the forwarding is user-owned) or root (as root can see everything). Touch-to-authorize helps mitigate that. If one seees the prompt come up when they've just performed a git pull, it's expected and likely non-malicious. Allow. If it pops up after having ran "ls" or "randomly" in the course of a session - what's going on? Deny.
- Hnrobert42 6y agoYou are correct. Touch to authorize is lower risk. I don’t know a way to do that natively. Sorry if I misunderstood.