Mailinglist Archive: opensuse-bugs (12871 mails)

< Previous Next >
[Bug 464079] Mounting encrypted file system on USB HDD fails
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sat, 17 Jan 2009 07:46:34 -0700 (MST)
  • Message-id: <20090117144634.3AB4B245390@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=464079

User user2304@xxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=464079#c3


Peter Puncher <user2304@xxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |user2304@xxxxxx




--- Comment #3 from Peter Puncher <user2304@xxxxxx> 2009-01-17 07:46:32 MST ---
Not sure, if i got same problem with openSuSE 11.1:

When connecting an external usb-hdd with following partitions:

Platte /dev/sdc: 320.0 GByte, 320072933376 Byte
255 Köpfe, 63 Sektoren/Spuren, 38913 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Disk identifier: 0x5b6ac646

Gerät boot. Anfang Ende Blöcke Id System
/dev/sdc1 * 1 2433 19543041 83 Linux ## Unencrypted
Ext2
/dev/sdc2 2434 38913 293025600 83 Linux ## LuksEncrypted

i get an PopUp in KDE3 to provide passwort (attachment 1). After - surely !
-providing right password, i get an "wrong password" error.

Dumped the header by "cryptsetup luksDump /dev/sdc2" and got:

LUKS header information for /dev/sdc2
Version: 1
Cipher name: aes
Cipher mode: cbc-essiv:sha256
Hash spec: sha1
...

But unlike in 11.0 i can't mount it manually,

tplgsb:/dev/mapper # cryptsetup luksOpen /dev/sdc2 sdc2

results in

Command failed: Can not access device

Interestingly - i didn't saw this in 11.0 - two new devices were created
instantly after connecting the harddrive:

Platte /dev/dm-6: 320.0 GByte, 320072933376 Byte
255 Köpfe, 63 Sektoren/Spuren, 38913 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Disk identifier: 0x5b6ac646

Gerät boot. Anfang Ende Blöcke Id System
/dev/dm-6p1 * 1 2433 19543041 83 Linux
/dev/dm-6p2 2434 38913 293025600 83 Linux

But they cannot be openend via the cryptsetup-command, too.

Furthermore, instantly after connecting the harddrive, in /dev/mapper there are
new devices, too:

/dev/mapper/
insgesamt 0
drwxr-xr-x 2 root root 240 17. Jan 15:08 ./
drwxr-xr-x 12 root root 4740 17. Jan 15:08 ../
brw-r----- 1 root disk 253, 6 17. Jan 15:08 1WD_3200BEV_External
brw-r----- 1 root disk 253, 7 17. Jan 15:08 1WD_3200BEV_External_part1
brw-r----- 1 root disk 253, 8 17. Jan 15:08 1WD_3200BEV_External_part2

I figured out, that i can

cryptsetup luksOpen /dev/mapper/1WD_3200BEV_External_part2 sdc2

and then mount /dev/mapper/sdc2.

But why so complicated now ? I didn't saw this behaviour in other systems
(11.0, sysresccd) and i suppose, KDE can't handle this.

Is there an error in handling luks-encrypted media ?

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
< Previous Next >
References