From: Raphael Cohn <raphael.cohn@stormmq.com>
To: musl@lists.openwall.com
Subject: ruserok et al
Date: Wed, 4 Dec 2013 14:12:31 +0000 [thread overview]
Message-ID: <CACCP0GqVBiv78stBjVu25GhCzFO7otKSe_cdpi6KL6eq0o9E9g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
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
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).
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?
Alternatively, it might be a good idea to not do this, but have a wiki page
somewhere listing deliberately unimplemented and stub functions.
Raph
Raphael Cohn
Chief Architect, stormmq
Co-Chair, OASIS MQTT Standard
Secretary, OASIS AMQP Standard
raphael.cohn@stormmq.com
+44 7590 675 756
UK Office:
Hamblethorpe Farm, Crag Lane, Bradley BD20 9DB, North Yorkshire, United
Kingdom
Telephone: +44 845 3712 567
Registered office:
16 Anchor Street, Chelmsford, Essex, CM2 0JY, United Kingdom
StormMQ Limited is Registered in England and Wales under Company Number
07175657
StormMQ.com
[-- Attachment #2: Type: text/html, Size: 1683 bytes --]
next reply other threads:[~2013-12-04 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 14:12 Raphael Cohn [this message]
2013-12-04 17:05 ` Rich Felker
2013-12-04 18:13 ` Raphael Cohn
2013-12-04 18:34 ` Daniel Cegiełka
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=CACCP0GqVBiv78stBjVu25GhCzFO7otKSe_cdpi6KL6eq0o9E9g@mail.gmail.com \
--to=raphael.cohn@stormmq.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).