Live data from Hacker News

Don't use 1234 as your password

nortonwang.com

31–40 of 56 posts

Re: Don't use 1234 as your password

#33
Why not disable password logins completely, use PKI for all connections, and while we're at it, restrict logins to known hosts?

Also, don't use passwordless keys.

Then there's moving sshd off of port 22 to provide some obscurity.

Yada yada yada... How many times will we have to go over this subject?

Re: Don't use 1234 as your password

#34

The very first time I tried Linux, after spending an entire day downloading Slackware, copying it to a set of install diskettes, partitioning a hard drive and installing it, I set my root password to "12345". I was around 10 at the time, 1995 plus or minus a year or two. After booting for the first time, I dialed up AOL and logged on to a Linux-topic IRC channel. I talked to the strangers there about how excited I wa…

Nitpick: `cd` would not get command not found because it is a builtin, and must be so since an external program can't update the working directory of its parent process.

Re: Don't use 1234 as your password

#35
post #15

I found a 68K SGI Iris 2400 machine up and running in college in about 2004. It had a sticker with the hostname on it. Later on that week, I went to the department homepage, got the staff roster and tried to guess the usernames. I telnetted to port 25 and tried RCPT TO hypothesized names, like so $ telnet host 25 MAIL FROM: a@a.com 250 Sender OK RCPT TO: afranks 550 Recipient not found RCPT TO: arty.franks 250 Recipi…

If you still had access today, it would be a perfect platform for Bitcoin mining.

Did you not see those specs? Or is it that for some strange quirk of something my Iris is a great money making machine?

Re: Don't use 1234 as your password

#37
post #14

The very first time I tried Linux, after spending an entire day downloading Slackware, copying it to a set of install diskettes, partitioning a hard drive and installing it, I set my root password to "12345". I was around 10 at the time, 1995 plus or minus a year or two. After booting for the first time, I dialed up AOL and logged on to a Linux-topic IRC channel. I talked to the strangers there about how excited I wa…

I had a similar experience around the same age and year, except it was with FreeBSD. I got it to boot once, then tried to change the bootloader setup to allow dual booting with the existing MS-DOS 5.x installation. You can imagine how well that went, as a 10 or 11 year old with no previous FreeBSD/Linux experience. My parents were not quite so understanding about why I had broken their $3000+ computer and lost all th…

LOL I did the exact same thing with my parents' computers back then >:D

Re: Don't use 1234 as your password

#38

I'm pretty sure, based on that post, that you have a fair bit more system administration experience than I do, which makes the whole thing even more boggling. I feel like a professional auto mechanic is telling me, all serious-like, that he just learned the hard way why you shouldn't try to drive while running alongside your car, reaching through the window to work the steering wheel, with a brick on the accelerator.

It takes a real professional to admit when he's screwed up.

Or.

The more skilled one is, the more confident one is that he can do dumb things and get away with it.

Re: Don't use 1234 as your password

#40

Quick and simple solution. If you are only using key based logins then just disable password SSH logins, add: ChallengeResponseAuthentication no PasswordAuthentication no UsePAM no To your sshd config and then you don't need to worry as much about if one of your accounts has a password of 1234.

If any of your accounts get compromised, a simple su to the account with a weak password will give them everything. It's a big improvement, but the weak password is still a vulnerability.
Post reply on HN