GNU GRUB - Bugs: bug #8436, Reassigned item: grub-md5-crypt...
You are not allowed to post comments on this tracker with your current authentication level.
bug #8436: Reassigned item: grub-md5-crypt does not return a hash value but instead returns to the command prompt
Submitter: | None | ||
Submitted: | Sat 03 Apr 2004 08:34:21 PM UTC | ||
Category: | None | Severity: | Major |
Priority: | 5 - Normal | Item Group: | None |
Status: | Invalid | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Originator Email: | -email is unavailable- | Open/Closed: | Closed |
Release: | None | Release: | SuSE 9.1 |
Reproducibility: | None | Planned Release: | None |
Sun 04 Apr 2004 03:28:35 PM UTC, comment #2: |
Yoshinori K. Okuji <okuji> |
Sat 03 Apr 2004 08:34:21 PM UTC, comment #1: This item has been reassigned from the project Savannah Administration bugs tracker to your tracker. |
Sylvain Beucler <Beuc> |
Sat 03 Apr 2004 08:34:21 PM UTC, original submission:
I have SuSE 9.1 installed using grub-.93-106. I am trying to secure my grub bootloader by password encrypting it. I wanted to use md5 via the grub-md5-crypt command with no luck. When I run the command, it asks for the password twice but then it does not return a hash. Instead it just returns the command prompt like nothing happend. |
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2004-04-04 | okuji | Status | None | Invalid | |
Open/Closed | Open | Closed | |||
Release | SuSE 9.1 | ||||
2004-04-03 | Beuc | Reassign item | From group Savannah Administration, bugs tracker | To group GNU GRUB, bugs tracker |
Powered by Savane 3.13-bb6a.
Corresponding source code
We cannot accept this report, because the bug reporter did not
login or specify his/her identity when submitting the report. As
fixing bugs is a collaborative process, we need to know how to
contact bug reporters.