full-disclosure - Re: sshd logins without a source

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]

Date: Sat, 24 Sep 2011 07:55:00 +1000
From: paul.szabo@...ney.edu.au
To: laurelai@...echan.org
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: sshd logins without a source

Dear all,

>>>> I do not think that sshd normally logs its source. ...
> Really? ...

Sorry about the confusion I may have caused. I guess my comments apply
to some older version sshd (or maybe old, wrong configs): surely that is
when, wanting better logs, I put in that hosts.allow logger. Perusing my
logs more carefully, I now see lines like:

DATE SRV sshd[PID]: Connection source HOST port PORT
DATE SRV sshd[PID]: Accepted keyboard-interactive/pam for USER from IP port PORT ssh2

where the second line came from sshd itself.

Cheers, Paul

Paul Szabo   psz@...hs.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of Sydney    Australia

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