From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Stéphane Aulery" <saulery-GANU6spQydw@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
528015-forwarded-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] securetty.5: Note that the pam_securetty module also uses this file
Date: Sun, 08 Mar 2015 09:21:58 +0100 [thread overview]
Message-ID: <54FC06A6.7070206@gmail.com> (raw)
In-Reply-To: <1425744418-26003-1-git-send-email-saulery-GANU6spQydw@public.gmane.org>
On 03/07/2015 05:06 PM, Stéphane Aulery wrote:
> Debian Bug #528015 reported by "Nicolas FRANCOIS (Nekral)" <nicolas.francois-Fa7rcPG4DJn7nK0/Xc0eeg@public.gmane.org>
>
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528015
>
> This patch is a modified version of the one proposed without specific part to
> Debian.
Thanks, Stéphane. Applied.
Cheers,
Michael
> Signed-off-by: Stéphane Aulery <saulery-GANU6spQydw@public.gmane.org>
> ---
> man5/securetty.5 | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/man5/securetty.5 b/man5/securetty.5
> index 99f6c57..88f9fb6 100644
> --- a/man5/securetty.5
> +++ b/man5/securetty.5
> @@ -29,17 +29,26 @@ securetty \- file which lists terminals from which root can log in
> .SH DESCRIPTION
> The file
> .I /etc/securetty
> -is used by (some versions of)
> -.BR login (1).
> -The file contains the device names of terminal lines
> +contains the names of terminals
> (one per line, without leading
> .IR /dev/ )
> +which are considered secure for the transmission of certain authentication
> +tokens.
> +.P
> +It is used by (some versions of)
> +.BR login (1)
> +to restrict the terminals
> on which root is allowed to login.
> See
> .BR login.defs (5)
> if you use the shadow suite.
> +.P
> +On PAM enabled systems, it is used for the same purpose by
> +.BR pam_securetty (8)
> +to restrict the terminals on which empty passwords are accepted.
> .SH FILES
> .I /etc/securetty
> .SH SEE ALSO
> .BR login (1),
> -.BR login.defs (5)
> +.BR login.defs (5),
> +.BR pam_securetty (8)
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-03-08 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090510105952.GA19341@nekral.nekral.homelinux.net>
[not found] ` <20090510105952.GA19341-pDMkYksm/NDBVznEOA0nCqMXiC8k1aZu0e7PPNI6Mm0@public.gmane.org>
2015-03-07 16:06 ` [PATCH] securetty.5: Note that the pam_securetty module also uses this file Stéphane Aulery
[not found] ` <1425744418-26003-1-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-08 8:21 ` Michael Kerrisk (man-pages) [this message]
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=54FC06A6.7070206@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=528015-forwarded-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=saulery-GANU6spQydw@public.gmane.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 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).