From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Re[2]: 'password' command in GRUB 2?
Date: Thu, 20 Aug 2009 18:32:14 +0200 [thread overview]
Message-ID: <20090820163214.GA2856@thorin> (raw)
In-Reply-To: <d7ead6de0908190817r4381d425w300f6a49c87aedfa@mail.gmail.com>
On Wed, Aug 19, 2009 at 05:17:13PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Wed, Aug 19, 2009 at 5:08 PM, Robert Millan<rmh@aybabtu.com> wrote:
> >
> > I agree with this proposal in general. Except with the concept of "users",
> > which I think might be overkill. GRUB is not a Un*x with its /home and
> > per-user settings. These passwords just protect resources, so I'm not sure
> > if there's a point in managing users as an intermediate layer between
> > passwords and the restricted resource.
> The concept of users allows to use other authentication methods then
> password. Consider a possibility of fingerprint authentications. 2
> users needing superuser privilegies can share the same password but
> have trouble sharing fingerprints. Another possibility is LUKS
> authentication - user is considered ok if his password unlocks the
> slot number N. If we ask users to share the same keyslot on luks we
> get in the way of luks keyphrase revocation.
> Additionally this simplifies the configuration as you don't need to
> write password at every menuentry directive.
> While the concept of users isn't strictly necessary it allows easy
> management of multiple authentication methods and is really helpful
> even for just managing multiple passwords
Ok. Then it might be a good thing to have those in our current model, even
if we don't support fingerprints yet.
I'm fine with the proposed design.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
prev parent reply other threads:[~2009-08-20 16:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 17:36 'password' command in GRUB 2? Colin Watson
2009-06-05 17:55 ` Vladimir 'phcoder' Serbinenko
2009-06-05 18:17 ` Re[2]: " Julien RANC
2009-07-26 14:40 ` Felix Zielcke
2009-07-26 16:20 ` Vladimir 'phcoder' Serbinenko
2009-07-26 21:29 ` Vladimir 'phcoder' Serbinenko
2009-08-20 16:44 ` Robert Millan
2009-08-21 11:30 ` Vladimir 'phcoder' Serbinenko
2009-08-22 19:47 ` Vladimir 'phcoder' Serbinenko
2009-08-23 10:14 ` Robert Millan
2009-08-24 22:36 ` Robert Millan
2009-08-24 23:58 ` Vladimir 'phcoder' Serbinenko
2009-08-25 14:35 ` Felix Zielcke
2009-08-25 14:50 ` Vladimir 'phcoder' Serbinenko
2009-08-25 18:55 ` Michal Suchanek
2009-08-25 19:54 ` Vladimir 'phcoder' Serbinenko
2009-08-26 11:51 ` Michal Suchanek
2009-08-26 17:32 ` Vladimir 'phcoder' Serbinenko
2009-08-28 12:37 ` Robert Millan
2009-08-19 15:08 ` Robert Millan
2009-08-19 15:17 ` Vladimir 'phcoder' Serbinenko
2009-08-20 16:32 ` Robert Millan [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=20090820163214.GA2856@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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.