full-disclosure - Re: targetted SSH bruteforce attacks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49489.1276807747@localhost>
Date: Thu, 17 Jun 2010 16:49:07 -0400
From: Valdis.Kletnieks@...edu
To: Paul Schmehl <pschmehl_lists@...rr.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: targetted SSH bruteforce attacks

On Thu, 17 Jun 2010 15:21:47 CDT, Paul Schmehl said:

> Why?  Ssh is encrypted, so you're not exposing a password when you login.  How 
> does public key authentication make you more secure (in a practical sense)?

Compare the work effort needed by an attacker to brute-force a password (I mean,
c'mon Paul - these ssh woodpeckers wouldn't keep hammering if it didn't work
once in a while) with how much woodpecking would be needed to brute-force
a key-authenticated login.

Content of type "application/pgp-signature" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/