[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACCP0GrRu4FV4K01ehyzh031pB2QFqGZny0FU=4khkXeZ5M7Lw@mail.gmail.com>
Date: Wed, 4 Dec 2013 18:13:52 +0000
From: Raphael Cohn <raphael.cohn@...rmmq.com>
To: musl@...ts.openwall.com
Subject: Re: ruserok et al
I'm not sure I'll get anywhere with upstream... There's other dubious stuff
in Linux PAM, too. Indeed a quick list of stuff that looks at least suspect
to my mind is:-
wheel (sudo et al are a better solution)
userdb (why? Isn't /etc/passwd already a local database?)
tally (defunct)
time (obsolecent; why restrict logins to certain times in this day and age
when not using time shared systems and dial up)
pwhistory (stores previous passwords ?potentially recoverably)
permit (insecure)
nologin (security risk; forces root to be special)
mail (old-fashioned and of limited use in a server or desktop today)
group (security risk; unnecessary extra complexity in addition to
/etc/group)
ftp (in 2013? And it reckons it's easily spoofed in its own man page)
debug (unnecessary)
but none of that has to do with musl (although dropping time means there's
less patching to do to support legacy NIS junk)...
Anyway, now I'm off-topic.
On 4 December 2013 17:05, Rich Felker <dalias@...ifal.cx> wrote:
> On Wed, Dec 04, 2013 at 02:12:31PM +0000, Raphael Cohn wrote:
> > Dear List,
> >
> > Whilst compiling pam_rhosts in Linux PAM 1.1.8 (pam_rhosts.c), it tries
> to
> > use the function 'ruserok'. I believe this, and its siblings, aren't in
>
> This is part of the legacy rhosts API for source-IP-address-based
> authentication. It's useless, dangerous, and really disturbing that
> PAM even supports something that was obsolete and known-dangerous a
> decade before PAM was invented... My first reaction would be to say
> "patch it out and send a bug report upstream".
>
> > musl. Quite correctly, I suspect - I presume these relate to the legacy
> 'r'
> > commands that no one in their right mind should be using. I'll be
> patching
> > my installation to remove this module from the build (*sigh* Linux pam
> > doesn't make choosing a subset of modules easy).
>
> Yes, this is the right solution, but we should try (diplomatically :)
> to get upstream fixed too.
>
> > Would it make sense, for completeness to add stubs to musl to do either:-
> > - return the failure outcome;
> > - or, return a nasty warning and a failure outcome? And a syslog on
> runtime
> > use to really give users a kick?
>
> A stub that just returns failure would not be such a bad thing, but
> when it's such a harmful a function that only a single package has
> been caught using, I'd rather try to get it fixed upstream.
> Compatibility with broken apps/libs is a continuous stream of choices
> whether to work around the brokenness in musl (often this has tiny
> marginal cost but that cost builds up over time with lots of broken
> packages) or make the efforts to get the upstream fixed.
>
> > Alternatively, it might be a good idea to not do this, but have a wiki
> page
> > somewhere listing deliberately unimplemented and stub functions.
>
> That might be a good idea anyway even if we don't add more such
> functions.
>
> Rich
>
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
