Bug#314645: ssh password mappings result

2005-06-21 Thread Justin Pryzby
On Tue, Jun 21, 2005 at 09:10:20AM -0700, Greg Webster wrote: > Completely agreedI don't want to know the passwords. What I'd like > to see is, over the long term, are these scans making more attempts at > non-system, first-name valid accounts that do exist than random chance > should allow, an

Bug#314645: ssh password mappings result

2005-06-21 Thread Greg Webster
Completely agreedI don't want to know the passwords. What I'd like to see is, over the long term, are these scans making more attempts at non-system, first-name valid accounts that do exist than random chance should allow, and a clear indication that more attempts at valid accounts are made tha

Bug#314645: ssh password mappings result

2005-06-21 Thread Justin Pryzby
Sure, but what do you plan to do with the data? Rather, how do you plan to analyze it? It seems to me that this could be done without knowing what passwords are tried. The data lined up pretty well last night, when I discovered the first ssh scan; I had to remove some blank lines from /etc/ssh-l

Bug#314645: ssh password mappings result

2005-06-20 Thread Greg Webster
Hi Justin, Part of what I'd like to (dis)prove is that they are making a 'second run' from this or another machine to hit that accounts that it believes are valid...any chance you could keep your testing up for a while? Thx, Greg On Mon, 2005-20-06 at 23:15 -0400, Justin Pryzby wrote: > Includ

Bug#314645: ssh password mappings result

2005-06-20 Thread Justin Pryzby
Included is a list of usernames and corresponding passwords used in an ssh scan I observed. It indicates to me that it is trying statistically common (aka dumb) passwords on common usernames; I see no evidence of an attempt to measure timings to discover valid accounts. Justin Starred accounts a