Gutsy: cryptsetup leaves /dev/mapper/temporary-cryptsetup-[0-9]+ devices lying around
Bug #162582 reported by
Swâmi Petaramesh
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Debian) |
Fix Released
|
Unknown
|
|||
cryptsetup (Ubuntu) |
Fix Released
|
Undecided
|
Reinhard Tartler |
Bug Description
Binary package hint: cryptsetup
In some situations (I could not yet clearly determine in which exact conditions this happens), after running cryptsetup, a device /dev/mapper/
Looks like the same as reported in Debian bug #444914
Not sure what this device actually corresponds to or if it might allow unauthorized access to encrypted content, so I check this as a potential security vulnerability.
Changed in cryptsetup: | |
status: | Unknown → Fix Committed |
Changed in cryptsetup: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This looks to be the same bug I have been trying to analyze in Ubuntu bug #148003. It was reported there that the existence of this stale device node often prevents auto-mounting of encrypted USB memory sticks, etc.
There appears to be a race condition in the processes spawned by udev. The file /dev/mapper/ temporary- cryptsetup- XXXX is created and then almost immediately destroyed. But it appears that the "remove" event gets processed before the "add" event is finished, with unfortunate results.