Earlier quoted context omitted.
30 years ago you could just sniff the passwords on the local subnet because everyone was using telnet and ftp in the clear.
20 years ago you could also sniff passwords for all Windows users in the same subnet as you. Windows used the NTLM scheme which was known to be weak even back then. An AMD K6 running overnight cracked almost all of them at my university's lab, including the Active Directory domain admin.
Ken Thompson's Unix Password
601–610 of 665 posts
Re: Ken Thompson's Unix Password
#602I remember cracking the password from a Windows system in high school. There was a centralized login mechanism using Novell but everything was cached locally. So you could boot a Linux CD and copy the password file to a memory stick, and crack at home. I think I used lophtcrack? The head admin account for the entire school district (basically root) had the password “north”. It took like a fraction of a second to crac…
You could save the *.pwl files to a floppy, take them home, and crack them in a few minutes. All you needed was a PC that a teacher had logged into recently.
Re: Ken Thompson's Unix Password
#603Earlier quoted context omitted.
> In an imaginary perfect criminal justice system, charges/penalties are based on damage done. Hell no. Otherwise you could just set up one gigantic crime by comitting a bunch of small "no damage done" crimes along the way-say, stealing a string of credentials one at a time, but not actually using them until you have all of them together and then you commit your major heist/crime.
Well, the imaginary perfect criminal justice system would probably arrest you right as you had completely committed to causing the damage, instead of afterwards. But it should still be justifying the arrest based on the act that caused damage, not the harmless acts that set you up to be ready to do it.
Re: Ken Thompson's Unix Password
#604Earlier quoted context omitted.
> Would you still feel safe if a burglar broke into your house and left a note saying they didn't take anything? That doesn't make it okay, but it certainly should result in a much lesser sentence than if the perpetrator had damaged or stolen property.
No. The serious crime is breaking in. Usually when someone's house is broken into they don't care about the stuff at all. They care that their personal space and sense of security has been violated. Also the criminal doesn't know what they'll find when they get in in but they are setting up a situation that can escalate quickly. Kids home alone? Someone with a shotgun? The very act of breaking in means they are ready…
You really believe this? What makes you think you speak for people in general, or know the mind of the average burglar?
And how far does your equivalence view stretch, if someone trespasses and uses your pool is that the same as taking your outdoor furniture? Why not?
Re: Ken Thompson's Unix Password
#605This brings back memories of a common exploit w/tftp, such that you could download an unshodowed /etc/passwd file from a remote machine, decrypt it, log into that remote system, collect new hosts from /etc/hosts, then rinse and repeat. Hash rate were pretty slow back then, but the fact that people used passwds straight out of dictionaries helped, so I'm told...
Better yet, open the /etc/passwd and see the root user's password wasn't set... Back in college I ran ToneLoc overnight and would try ftp on the successful hits. One server didn't have root set, so I telnet'ed, when prompted for the password, and I was in. I ran 'who', saw a user logged in. Decided to wall them a message of "You should really set your root password." and logged out. A couple of days later, I got an e…
https://www.youtube.com/watch?v=SF2fZ2iOXhk
Imagine the anecdote coming from the person you wall'd.
Re: Ken Thompson's Unix Password
#606Re: Ken Thompson's Unix Password
#607Earlier quoted context omitted.
I think that if someone boasts that they've cracked everyones password, reporting them is the right thing to do.
Perhaps the discretionary thing to do in the case where the perpetrator is relatively whitehat is to mention to IT that "it appears common knowledge that all admin passwords are compromised" without exposing their identity.
What an interesting alternate reality that would be.
Re: Ken Thompson's Unix Password
#608Re: Ken Thompson's Unix Password
#609Earlier quoted context omitted.
Want better password hygiene in the workplace? Encourage rude passwords!
Password rule N+1: "A password must contain at least one word from our list of banned URLs." At a former job I could not go to one of global corp Tata sites, because tata.
Re: Ken Thompson's Unix Password
#610I remember cracking the password from a Windows system in high school. There was a centralized login mechanism using Novell but everything was cached locally. So you could boot a Linux CD and copy the password file to a memory stick, and crack at home. I think I used lophtcrack? The head admin account for the entire school district (basically root) had the password “north”. It took like a fraction of a second to crac…
I was expelled from university for pulling off the exact same exploit with the "workstation only" feature in Novell. In my case, they put a computer in every dorm room, and every single one of them had a domain-wide administrator account cached in its SAM file. It was inevitable that a student would find it. It's been almost 15 years now but I believe the password was rac3c4r or something trivial like that. I ran Oph…
You broke rules for personal enjoyment and weren't even good enough to not get caught. You didn't beat them, they beat you. It doesn't matter if you went unnoticed for several months, the fact is standard monitoring and logs were your down fall. Nobody ever thinks of the log files and network monitoring tools as being part of security. Not being prevented from accessing the system is not the same thing as successfully hacking a system unless you aren't caught either.