full-disclosure - Re: What the f*** is going on?

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: <20110224172729.GI4876@ownco.net>
Date: Thu, 24 Feb 2011 12:27:29 -0500
From: jf <jf@...co.net>
To: Michal Zalewski <lcamtuf@...edump.cx>,
	full-disclosure@...ts.grok.org.uk
Subject: Re: What the f*** is going on?

On Thu, Feb 24, 2011 at 01:20:32PM -0800, Michal Zalewski wrote: 
> >> this is only true for remote attackers hitting network service auth.
> > Mhmm, and runas, su et al couldn't benefit from this?
> 
> Not a whole lot. You can likely tell a successful login from a failed
> one within several miliseconds by watching /proc or so.

I'd agree that remote auth obviously benefits more; but I'm not sure that an implementation issue entirely invalidates the point. Also, IIRC you can just ^C back to the shell instead of waiting on su to timeout.

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