| |||||||||||||
completioncompletionPosted Sep 30, 2013 12:53 UTC (Mon) by tialaramex (subscriber, #21167)In reply to: 30 years of GNU by Richard_J_Neill Parent article: 30 years of GNU
scp completion is rather dangerous, here's how:
1. Set a remote machine to disable SSH connections from hosts which pester with invalid credentials because maybe they're "script kiddies"
2. Change the credentials somewhere
3. Try to use SCP completion. Whack tab a few times wondering why it's not working
4. Congratulations you are now locked out of the remote machine with no clue as to what happened.
A systems administrator we hired locked himself out of his home systems this way, very amusing.
(Log in to post comments)
completion Posted Oct 3, 2013 5:07 UTC (Thu) by k8to (subscriber, #15413) [Link]
I'm not a fan of log-into-remote-systems-on-tab-complete for sure. If nothing else, it introduces *crazy* latency into tab completion, which isn't really very pleasant.
As for the script-kiddy lockout, the sane thing to do is expire that kind of thing after some time interval, possibly progressive, so that once you realized you screwed up you just wait 30 minutes and can get back in.
If one is so dense as to keep spamming it over and over for over 30 minutes, well... maybe the lockout could work to teach one lessons in patience and care. :-D I know a younger me could probably have used them.
|
|||||||||||||