All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: John Lane <grub@jelmail.com>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH 5/5] Cryptomount support for hyphens in UUID
Date: Wed, 29 Jul 2015 19:51:12 +0300	[thread overview]
Message-ID: <20150729195112.751a7ec9@opensuse.site> (raw)
In-Reply-To: <55B87800.3060802@jelmail.com>

В Wed, 29 Jul 2015 07:51:44 +0100
John Lane <grub@jelmail.com> пишет:

> On 29/07/15 04:08, Andrei Borzenkov wrote:
> > I still believe that generally ignoring hyphens for every future crypto
> > implementation is wrong. In future we simply should avoid mangling
> > UUID. So this should be restricted to LUKS only, where the problem
> > exists.
> >
> >
> Andrei I modified this in response to your earlier feedback so that it
> doesn't modify the user-supplied data and doesn't have any effect beyond
> the three places I mentioned.

That not what I mean. This patch ignores hyphens in UUID for any
current and future crypto backends. This means that it cannot
distinguish between 11-122 and 111-22 as UUID. And we cannot be sure we
never meet such backend. And GELI as far as I can tell does not
actually use hyphens.

We already made mistake of mangling native UUID, I'd rather avoid
continue to do it.

Can we restrict this to LUKS only? 

>                              These have no negative impact on uuid
> values used elesewere. If you don't want to support this fair enough -
> this can be dropped without impacting the other patches.
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel



  reply	other threads:[~2015-07-29 16:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 14:30 Cryptomount enhancements - revised John Lane
2015-06-29 14:30 ` [PATCH 1/5] Cryptomount support LUKS detached header John Lane
2015-06-29 14:30 ` [PATCH 2/5] Cryptomount support key files John Lane
2015-06-29 14:30 ` [PATCH 3/5] cryptomount luks allow multiple passphrase attempts John Lane
2015-06-29 14:56   ` John Lane
2015-06-29 14:30 ` [PATCH 4/5] Cryptomount support plain dm-crypt John Lane
2016-02-12 15:19   ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-06-29 14:31 ` [PATCH 5/5] Cryptomount support for hyphens in UUID John Lane
2015-06-29 14:52   ` John Lane
2015-07-29  3:08   ` Andrei Borzenkov
2015-07-29  6:51     ` John Lane
2015-07-29 16:51       ` Andrei Borzenkov [this message]
2015-07-29 18:53         ` John Lane
2015-07-28 18:51 ` Cryptomount enhancements - revised John Lane
2015-07-28 21:38   ` Vladimir 'phcoder' Serbinenko
2015-07-29  6:48     ` John Lane
2015-07-29 17:21       ` Andrei Borzenkov
2015-08-01 16:22         ` John Lane

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=20150729195112.751a7ec9@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=grub@jelmail.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.
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.