mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Solar Designer <solar@openwall.com>
To: musl@lists.openwall.com
Subject: Re: Todo for release?
Date: Tue, 14 Aug 2012 02:06:01 +0400	[thread overview]
Message-ID: <20120813220601.GA8817@openwall.com> (raw)
In-Reply-To: <20120813215344.GB27715@brightrain.aerifal.cx>

On Mon, Aug 13, 2012 at 05:53:44PM -0400, Rich Felker wrote:
> On Mon, Aug 13, 2012 at 11:31:54PM +0200, Szabolcs Nagy wrote:
> > md5 based crypt is not recommended anymore
> > http://phk.freebsd.dk/sagas/md5crypt_eol.html
> 
> Indeed. But is it used in existing Linux user databases on any
> significant scale?

It is.

> If not, I agree we can just drop it.

We should support it.

Maybe use my MD5 code, but for md5crypt write new code to avoid the
beerware license (I would be happy to buy phk a beer, but having to
mention another license for a component in musl's license is not nice).

> I'm confused by all the SHA names (1/2/256/512)...

You need sha512crypt and sha256crypt.  SHA-1 is irrelevant (not used in
any common crypt(3) flavor).  SHA-2 is a common name for the
SHA-224/256/384/512 primitives (although these are actually different).

Of sha512crypt and sha256crypt, only the former is commonly used, but
you may choose to support both anyway (systems generally support both).

The high-level structure of md5crypt, sha512crypt, and sha256crypt is
similar, but it'd be tricky/unreasonable to exploit that for reduced
code size as you'd likely increase source code complexity and make the
code slower (important in case of sha512crypt and sha256crypt, which
support variable iteration counts).

Alexander


  reply	other threads:[~2012-08-13 22:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 18:53 Rich Felker
2012-08-13 21:31 ` Szabolcs Nagy
2012-08-13 21:53   ` Rich Felker
2012-08-13 22:06     ` Solar Designer [this message]
2012-08-14 15:02       ` Szabolcs Nagy
2012-08-15  0:30         ` Szabolcs Nagy
2012-08-13 22:20   ` Solar Designer
2012-08-14  1:46     ` Rich Felker
2012-08-14  2:13       ` Solar Designer
2012-08-14  2:35         ` Rich Felker
2012-08-14  2:49           ` Solar Designer
2012-08-14  2:58             ` Rich Felker
2012-08-14  3:35               ` Solar Designer
2012-08-14  4:49                 ` Rich Felker
2012-08-15  4:08 ` Rich Felker
2012-08-15  8:55   ` Daniel Cegiełka
2012-08-15 10:20     ` Szabolcs Nagy
2012-08-15 10:53       ` Daniel Cegiełka
2012-08-15 13:10         ` John Spencer
2012-08-15 13:23           ` Daniel Cegiełka
2012-08-15 13:32       ` Szabolcs Nagy
2012-08-15 14:36         ` Rich Felker
2012-08-17  9:49           ` Szabolcs Nagy
2012-08-17 12:10             ` Rich Felker
2012-08-22 17:45               ` Daniel Cegiełka
2012-08-22 18:57                 ` Rich Felker
2012-08-22 19:15                   ` Daniel Cegiełka
2012-08-22 20:24                   ` Richard Pennington
2012-08-22 22:44                     ` Rich Felker
2012-08-15 12:36     ` Rich Felker
2012-08-15 12:57   ` Luca Barbato
2012-08-15 14:34     ` Rich Felker
2012-08-15 18:28       ` Luca Barbato
2012-08-15 18:35         ` Rich Felker
2012-08-15 21:25         ` Rich Felker
2012-08-16 17:11           ` Luca Barbato
2012-08-15 13:27   ` Richard Pennington
2012-08-15 22:44 ` boris brezillon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120813220601.GA8817@openwall.com \
    --to=solar@openwall.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).