All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] password command implementation
Date: Tue, 7 Aug 2007 21:04:41 +0200	[thread overview]
Message-ID: <200708072104.41790.okuji@enbug.org> (raw)
In-Reply-To: <ed88bdf20708070517u650a596ldd3bc87859684194@mail.gmail.com>

Hello,

>  - md5.c/h comes from Grub Legacy, just a bit adapted to use Grub2 memory
> functions (malloc, memset, endianness). Therefore, code works correctly, or
> at least in a coherent way with respect to Grub Legacy. I can try to make
> the code clearer if needed... Other code is made from scratch.

IMO, we should stop using MD5 for the encryption, because it is nowadays 
considered to be not secure enough. At least SHA1 should be used, although 
even SHA1 is considered to be vulnerable in near future... You can take an 
implementation from gnulib.

>  - limit to password of 64 chars is to have a max buffer size when asking
> for the password. It could be greater if required. But will someone really
> use >64chars plain text password ?

I don't think so. For me, this is an acceptable limitation.

>  - plain text passwords are indeed very insecure, but I kept them, as it
> was possible in Grub legacy. Should I remove them ?

Yes. Basically we don't need to keep compatibilty with GRUB Legacy, thus 
insecure things should be abandoned.

Thanks,
Okuji



      parent reply	other threads:[~2007-08-07 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 18:38 [PATCH] password command implementation Julien RANC
2007-08-07 10:12 ` Marco Gerards
2007-08-07 12:17   ` Julien Ranc
2007-08-07 12:45     ` Jordi Mallach
2007-08-08 14:57       ` Marco Gerards
2007-08-07 19:04     ` Yoshinori K. Okuji [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=200708072104.41790.okuji@enbug.org \
    --to=okuji@enbug.org \
    --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.