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 for Android: free password hash cracker in your pocket

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

Message-ID: <20110224173436.GJ4876@ownco.net>
Date: Thu, 24 Feb 2011 12:34:37 -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 12:27:29PM -0500, jf wrote: 
> 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.
>
Erm, slightly misunderstood what you were saying-- although overall statement still sorta holds. Doing this locally is obviously going to incurr a lot more side-channel information leakage chances. I'd still prefer to see those addressed over abandonment of it all together. 

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