From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Imminent bugfix release (1.97.1)
Date: Mon, 09 Nov 2009 14:50:36 +0100 [thread overview]
Message-ID: <4AF81E2C.2090700@gmail.com> (raw)
In-Reply-To: <ca0f59980911090533r5cb2f242h76b0f78437891ea9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
Bean wrote:
> On Mon, Nov 9, 2009 at 9:04 AM, Robert Millan <rmh@aybabtu.com> wrote:
>
>> A security problem [1] was found in our password-checking routines,
>> which affects GRUB 1.97. I'll be releasing 1.97.1 tomorrow.
>>
>> Additionally, I cherry-picked fixes for a few problems that should
>> have made it to the release, like GNU/Hurd support (see NEWS file
>> for details). The release branch is available in:
>>
>> sftp://bzr.savannah.gnu.org/srv/bzr/grub/branches/release_1_97/
>>
>> If you have time, please test this tree, specially password support,
>> to help find possible problems.
>>
>
> Hi,
>
> Actually, the function of grub_auth_strcmp puzzles me, why would it
> need to wait 100 ms to return the result ?
10 ms actually. The goal is to take same amount of time indpendently of
input values. But probably the delay should be around whole thing and
it's how I'll do but for this urgent release this will do it
> grub_auth_strcmp is used in
> many place, so the authorized could take some time to complete. And
> there is a hidden issue in it, grub_auth_strcmp can accept NULL
> pointer as input, but grub_strcmp doesn't check for NULL pointer.
>
>
Current codebase didn't use it
--
Regards
Vladimir 'phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2009-11-09 13:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 1:04 Imminent bugfix release (1.97.1) Robert Millan
2009-11-09 1:27 ` Robert Millan
2009-11-09 2:08 ` Jordan Uggla
2009-11-09 14:15 ` Robert Millan
2009-11-09 13:33 ` Bean
2009-11-09 13:50 ` Vladimir 'phcoder' Serbinenko [this message]
2009-11-09 14:18 ` Robert Millan
2009-11-09 14:21 ` Bean
2009-11-09 14:34 ` Vladimir 'phcoder' Serbinenko
2009-11-09 17:46 ` Duboucher Thomas
2009-11-09 18:10 ` Robert Millan
2009-11-09 18:15 ` Vladimir 'phcoder' Serbinenko
2009-11-09 18:25 ` Robert Millan
2009-11-09 18:36 ` Bean
2009-11-09 18:46 ` Vladimir 'phcoder' Serbinenko
2009-11-09 18:49 ` Bean
2009-11-09 21:13 ` Duboucher Thomas
2009-11-09 21:34 ` Vladimir 'phcoder' Serbinenko
2009-11-09 21:43 ` Duboucher Thomas
2009-11-09 22:06 ` Robert Millan
2009-11-09 22:46 ` Duboucher Thomas
2009-11-09 23:09 ` Darron Black
2009-11-09 23:50 ` richardvoigt
2009-11-09 23:56 ` Darron Black
2009-11-09 23:46 ` richardvoigt
2009-11-10 5:39 ` Bean
2009-11-10 8:28 ` Bean
2009-11-10 8:46 ` Bean
2009-11-10 8:52 ` Bean
2009-11-10 9:05 ` Bean
2009-11-10 12:37 ` Bean
2009-11-10 14:25 ` Duboucher Thomas
2009-11-10 14:47 ` Bean
2009-11-10 17:43 ` Duboucher Thomas
2009-11-10 19:01 ` Vladimir 'phcoder' Serbinenko
2009-11-10 19:04 ` Vladimir 'phcoder' Serbinenko
2009-11-10 21:29 ` Duboucher Thomas
2009-11-10 15:27 ` richardvoigt
2009-11-10 17:38 ` Duboucher Thomas
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=4AF81E2C.2090700@gmail.com \
--to=phcoder@gmail.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.