[bug #45889] cryptomount thinks locked device is: already mounted as cryptoX

[TJ]

URL:
  <http://savannah.gnu.org/bugs/?45889>

                 Summary: cryptomount thinks locked device is: already mounted
as cryptoX
                 Project: GNU GRUB
            Submitted by: intuitivenipple
            Submitted on: Sun 06 Sep 2015 12:45:15 GMT
                Category: Security
                Severity: Major
                Priority: 5 - Normal
              Item Group: Software Error
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: 2.02~beta1
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

Boot disk with 3 LUKS/dm-crypt GPT partitions

(hd0,gpt3) (hd0,gpt4) (hd0,gpt5)

grub is in (hd0,gpt3). The others have a LVM VG each.

Using GRUB_ENABLE_CRYPTODISK=y

I deliberately fail the first pass-phrase entry to get the rescue environment.
I then

cryptomount hd0,gpt3
 
(crypto0) device is now present and prefix/root are set correctly.

I insmod some other modules (exploring available functions) and

set debug=cryptodisk

I try to

cryptomount hd0,gpt4
cryptomount hd0,gpt4

and see the message

disk/cryptodisk.c:978: already mounted as crypto0

But ls shows only (crypto0)

source-code in grub-core/disk/cryptodisk.c shows 

dev = grub_cryptodisk_get_by_source_disk(disk)

must be returning a reference to the existing crypto0, which suggests a
problem in grub_cryptodisk_insert() or grub_cryptodisk_get_by_source_disk()




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45889>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/