You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Back in the late-80s my friends and I would lay similar traps for people on the systems at UC Irvine. Most common was leveraging the stupidity of '.' at the start of $PATH. Write a script to do something funny, call it 'ls', put it in ~cmacfarl/ and wait for hilarity.
This did not require access to anyone else's account and managed to catch people who would snoop around in other people's home directories. Being the ethical students we were, we never grabbed passwords. Although I did know someone who wrote a brute force dictionary attack in 1988 and cracked my password, with my permission, in about 20 minutes. Learned my lesson there.
The text was updated successfully, but these errors were encountered:
Back in the late-80s my friends and I would lay similar traps for people on the systems at UC Irvine. Most common was leveraging the stupidity of '.' at the start of $PATH. Write a script to do something funny, call it 'ls', put it in ~cmacfarl/ and wait for hilarity.
This did not require access to anyone else's account and managed to catch people who would snoop around in other people's home directories. Being the ethical students we were, we never grabbed passwords. Although I did know someone who wrote a brute force dictionary attack in 1988 and cracked my password, with my permission, in about 20 minutes. Learned my lesson there.
The text was updated successfully, but these errors were encountered: