From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] system/skeleton: add the shadow-group file
Date: Tue, 1 Jan 2013 10:26:06 +0100 [thread overview]
Message-ID: <20130101102606.258d780e@skate> (raw)
In-Reply-To: <201212311918.08866.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
Happy New Year!
On Mon, 31 Dec 2012 19:18:08 +0100, Yann E. MORIN wrote:
> Wrong. Groups can have passwords. And users can change-group with:
>
> $ newgrp [-] groupname
>
> If the user is a member of that group, or the group is paswrod-less, then
> no password is asked for, and the current group-id has changed (it is a bit
> like 'su', but to just change group)
>
> If the user is not a member that group, and the group is not restricted (eg.
> password is not '*' and does not start with '!', then the user is asked to
> enter the group password.
>
> See:
> group(5) gshadow(5) newgrp(1)
>
> I hope that was enough to explain addition of gshadow. ;-)
Interesting, I didn't know about this.
The next question that comes up is: do we really need to support this
in Buildroot?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-01 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 23:26 [Buildroot] [pull request] Pull request for branch yem-package-create-user Yann E. MORIN
2012-12-30 23:26 ` [Buildroot] [PATCH 1/3] system/skeleton: add the shadow-group file Yann E. MORIN
2012-12-31 17:18 ` Thomas Petazzoni
2012-12-31 18:18 ` Yann E. MORIN
2013-01-01 9:26 ` Thomas Petazzoni [this message]
2013-01-01 15:36 ` Yann E. MORIN
2013-01-01 21:08 ` Peter Korsgaard
2012-12-30 23:26 ` [Buildroot] [PATCH 2/3] packages: add ability for packages to create users Yann E. MORIN
2012-12-30 23:26 ` [Buildroot] [PATCH 3/3] package/tvheadend: use a non-root user to run the daemon Yann E. MORIN
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=20130101102606.258d780e@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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