3 ms·
We had a situation like this at work. My username was very common and got locked on our ssh proxies like clockwork with just the routine background internet sc
by darkhelmet 7y ago
We had a situation like this at work. My username was very common and got locked on our ssh proxies like clockwork with just the routine background internet scanning. I couldn't get any traction with getting this fixed. We had hardware 2FA (physical tokens), so brute forcing was effectively moot.
Then, strangely, various senior folks found their accounts getting locked 1-2 times a day, including the founder. That autolock policy died in a week, and they started looking for 2FA failures instead, as they should have.
I had considered "accidentally" setting up a ssh loop to do this but never quite got around to it. I assume somebody else did. I doubt that an infusion of sanity happened by accident.
- drblast 7y agoI did that to an overzealous sysadmin who wouldn't see the light about why a 30 minute password lock policy after three failed interactive tries with horrendous complexity requirements was a bad idea. Typed in his email address in front of him, hit enter three times, locked him out. Since this was a military base, typed in the commanding officer's email address, started to do the same thing, and suddenly the sysadmin saw the light shine down from heaven.