From: Ludwig Nussel <ludwig.nussel@suse.de>
To: util-linux@vger.kernel.org
Cc: Thorsten Kukuk <kukuk@suse.de>
Subject: Re: PAM-only login(1)
Date: Mon, 22 Aug 2011 13:19:44 +0200 [thread overview]
Message-ID: <4E523B50.8080204@suse.de> (raw)
In-Reply-To: <20110812115758.GC1843@nb.net.home>
Karel Zak wrote:
> I'd like to clean up login(1) code for v2.21. The current code is
> mess with many #ifdef and support for some unused (and badly tested)
> features (e.g. non-PAM support for /etc/securetty and /etc/usertty).
>
> What about to finally create nice and readable PAM-only login(1) for
> Linux?
+1
On openSUSE we already use a pam-only login program¹. It was forked
from util-linux > ten years ago AFAICT. It also includes features
from shadow-utils, like reading settings from /etc/login.defs.
cu
Ludwig
[1] https://build.opensuse.org/package/files?package=login&project=Base%3ASystem
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2011-08-22 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 11:57 PAM-only login(1) Karel Zak
2011-08-22 11:19 ` Ludwig Nussel [this message]
2011-08-22 12:01 ` Karel Zak
2011-08-22 12:34 ` Ludwig Nussel
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=4E523B50.8080204@suse.de \
--to=ludwig.nussel@suse.de \
--cc=kukuk@suse.de \
--cc=util-linux@vger.kernel.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.