From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/2051 Path: news.gmane.org!not-for-mail From: Solar Designer Newsgroups: gmane.linux.lib.musl.general Subject: Re: crypt() non-DES support Date: Wed, 3 Oct 2012 18:07:49 +0400 Message-ID: <20121003140749.GA22452@openwall.com> References: <20120608172323.3c569902@sibserver.ru> <20120608140857.GI163@brightrain.aerifal.cx> <20121003095442.GC24157@port70.net> <20121003140135.GD24157@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1349273302 14964 80.91.229.3 (3 Oct 2012 14:08:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 3 Oct 2012 14:08:22 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-2052-gllmg-musl=m.gmane.org@lists.openwall.com Wed Oct 03 16:08:27 2012 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1TJPcH-0007EK-9A for gllmg-musl@plane.gmane.org; Wed, 03 Oct 2012 16:08:01 +0200 Original-Received: (qmail 17500 invoked by uid 550); 3 Oct 2012 14:07:55 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 17490 invoked from network); 3 Oct 2012 14:07:55 -0000 Content-Disposition: inline In-Reply-To: <20121003140135.GD24157@port70.net> User-Agent: Mutt/1.4.2.3i Xref: news.gmane.org gmane.linux.lib.musl.general:2051 Archived-At: This is offtopic for the musl list, but on topic for the crypt-dev list, also hosted by Openwall. Anyhow, I'd rather not spend much time discussing SHA-3 before having played with it for real. On Wed, Oct 03, 2012 at 04:01:35PM +0200, Szabolcs Nagy wrote: > tl;dr: don't use sha3 for passwd hash At a high level, I fully agree. If someone simply puts SHA-3 in a loop, the result won't be great. But there's more to it: hardware implementations of password hashing are possible (I mean "defensive" ones), and parallelized implementations of SHA-3 (multiple inputs/outputs at once) in software might actually be very fast (so one of them can be used as a primitive for a password hashing method, just like I was thinking of building a password hashing method on top of bitslice DES in ~1998 - easily scalable to any SIMD vector width). Alexander