From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: shadow.h
Date: Wed, 27 Feb 2013 11:52:33 -0500 [thread overview]
Message-ID: <20130227165233.GI20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAPLrYEQP78x+Hn=ssukPOC-hBCyquS_O_bn+hTY8EesVi8_UeQ@mail.gmail.com>
On Wed, Feb 27, 2013 at 09:24:40AM +0100, Daniel Cegiełka wrote:
> 2013/2/27 Szabolcs Nagy <nsz@port70.net>:
>
> > /etc/shadow requires priviledge escalation for password changes
> > so putspent is dangerous, pam_unix should be deprecated on
> > modern systems
> >
> > http://www.openwall.com/tcb/
> >
> > (i think this already came up a few times, maybe it should be in a faq..)
>
> owl's tcb and musl? It's harder than it seems.
>
> 1) __crypt_blowfish() in musl isn't compatible with
> __crypt_blowfish_rn().. so lack of support for owl's
This is intentional. __-prefixed functions are not intended to be
externally visible except for a small set (e.g. stdio_ext.h) with
historical precedent or ABI things like __errno_location.
I hope we can work with owl to get a good solution. I'm not sure why
they don't just use crypt_r, since it would certainly do the job, but
if they want to use the special functions when available, they could
still include a fallback to crypt_r.
> __crypt_gensalt_ra() and crypt_ra/rn() etc. (owl's salt and tcb
> prefixes):
My feeling was that salt generation doesn't belong in libc. Just
adding these functions into the owl pam code should do the trick.
Rich
next prev parent reply other threads:[~2013-02-27 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 22:54 shadow.h Daniel Cegiełka
2013-02-26 23:19 ` shadow.h Szabolcs Nagy
2013-02-27 8:24 ` shadow.h Daniel Cegiełka
2013-02-27 16:52 ` Rich Felker [this message]
2013-02-27 17:18 ` shadow.h Daniel Cegiełka
2013-02-26 23:35 ` shadow.h Rich Felker
2013-02-27 9:09 ` shadow.h Daniel Cegiełka
2013-02-27 16:54 ` shadow.h Rich Felker
2013-02-27 17:04 ` shadow.h Daniel Cegiełka
2013-02-27 17:06 ` shadow.h Rich Felker
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=20130227165233.GI20323@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).