When inserted, the ironkey creates two block devices. In my case, /dev/scd1, which is an emulated USB cd-rom containing the unlock program, which gets automatically mounted, and /dev/sdb which appears as a removeable media usb storage device. To unlock, you need write access directly to /dev/sdb. Once unlocked, the media is "inserted" into /dev/sdb. It is an unpartitioned disk, by default, so there is no partition table on /dev/sdb. I'll include the output of /dev/sdb and /dev/scd1. It appears that my user (jbebel) gets write access to /dev/scd1, but not /dev/sdb.
brw-rw---- 1 root disk 8, 16 2008-09-30 11:31 /dev/sdb getfacl: Removing leading '/' from absolute path names # file: dev/sdb # owner: root # group: disk user::rw- group::rw- other::--- P: /block/sdb N: sdb S: disk/by-id/usb-IronKey_Secure_Drive_851D01065a6817201217-0:1 S: disk/by-path/pci-0000:00:1d.7-usb-0:4:1.0-scsi-0:0:0:1 E: DEVTYPE=disk E: ID_VENDOR=IronKey E: ID_MODEL=Secure_Drive E: ID_REVISION=1.00 E: ID_SERIAL=IronKey_Secure_Drive_851D01065a6817201217-0:1 E: ID_SERIAL_SHORT=851D01065a6817201217 E: ID_TYPE=disk E: ID_INSTANCE=0:1 E: ID_BUS=usb E: ID_PATH=pci-0000:00:1d.7-usb-0:4:1.0-scsi-0:0:0:1 brw-rw----+ 1 root cdrom 11, 1 2008-09-30 11:31 /dev/scd1 getfacl: Removing leading '/' from absolute path names # file: dev/scd1 # owner: root # group: cdrom user::rw- user:jbebel:rw- group::rw- mask::rw- other::--- P: /block/sr1 N: scd1 S: disk/by-id/usb-IronKey_Secure_Drive_851D01065a6817201217-0:0 S: disk/by-path/pci-0000:00:1d.7-usb-0:4:1.0-scsi-0:0:0:0 S: sr1 S: cdrom1 S: cdrom2 E: ID_CDROM=1 E: ID_CDROM_MRW=1 E: ID_CDROM_MRW_W=1 E: ID_CDROM_RAM=1 E: DEVTYPE=disk E: ID_VENDOR=IronKey E: ID_MODEL=Secure_Drive E: ID_REVISION=1.00 E: ID_SERIAL=IronKey_Secure_Drive_851D01065a6817201217-0:0 E: ID_SERIAL_SHORT=851D01065a6817201217 E: ID_TYPE=cd E: ID_INSTANCE=0:0 E: ID_BUS=usb E: ID_PATH=pci-0000:00:1d.7-usb-0:4:1.0-scsi-0:0:0:0 E: GENERATED=1 -- ironkey requires root access to unlock https://bugs.launchpad.net/bugs/269177 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
