News for hackers. Stuff that matters.
Re:Fishing for Hackers: Analysis of a Linux Server Attack by fragmede on Tuesday May 06, 2014 @02:07PM (#7706107)
So a DO/Rackspace/AWS VPS with a guessable root password can expect to be cracked in ~4 hours?

That's terrible!

AFAIK, AWS defaults to ssh-key logins with password logins disabled. Can someone comment about Rackspace/DO?

Re:Fishing for Hackers: Analysis of a Linux Server Attack by wazoox on Tuesday May 06, 2014 @04:13PM (#7706814)
This is not limited to AWS/rackspace... Here's from my home PC:

$ uptime

  22:09:07 up 30 days, 12:19,  2 users,  load average: 0,17, 0,09, 0,07
$ sudo fail2ban-client status ssh-iptables

Password:

Status for the jail: ssh-iptables

  |- filter
  |  |- File list:	/var/log/messages 
  |  |- Currently failed:	1
  |  `- Total failed:	1757
  `- action
     |- Currently banned:	0
     |  `- IP list:	
     `- Total banned:	242
1757 attempts from 242 IP address in the past 30 days...
Re:Fishing for Hackers: Analysis of a Linux Server Attack by akx on Wednesday May 07, 2014 @10:28AM (#7710290)
My home NAS is also exposed to the internet.

    up 298 days, 20:42,  1 user,  load average: 0.00, 0.01, 0.05
"zgrep ssh auth.log* | grep -i failed" has no traces of any intrusion attempts whatsoever, just me not being able to type.

The distinction is, though, that the SSHd on that box is running on a non-standard port (220)... so that certainly makes a difference.

Re:Fishing for Hackers: Analysis of a Linux Server Attack by gighi on Tuesday May 06, 2014 @02:11PM (#7706131)
Absolutely not, as I said in the article, I went out of the "wise" way and manually enabled:

1) Password authentication 2) Root authentication 3) Changed root password to "password"

All the providers offer fairly safe defaults, either using very random passwords or just enabling SSH keys.

Re:Fishing for Hackers: Analysis of a Linux Server Attack by fragmede on Tuesday May 06, 2014 @02:33PM (#7706283)
I covered that with 'guessable root password'

It is good to know that all providers have safe defaults, I only have experience with AWS in that regard.

Re:Fishing for Hackers: Analysis of a Linux Server Attack by fduran on Tuesday May 06, 2014 @02:45PM (#7706354)
In my case it was 5 hours http://www.fduran.com/blog/honeypots/ so although that's just another anecdote if you put up a server with an obvious dictionary ssh password, expect it to be compromised within hours.
Re:Fishing for Hackers: Analysis of a Linux Server Attack by pmh on Tuesday May 06, 2014 @11:44PM (#7708510)
At least in the early days of EC2, there were more than a few higher profile AMIs with password logins enabled, e.g. some of Oracle's AMIs used a trivial default password.

As far as I know, you can still create/publish AMIs where password auth is enabled, but all of Amazon's stock images only allow ssh-key auth.