|
William Parsons
|
accessing encrypted USB device
|
|
William Parsons
04/06/2011 6:39 AM
post84660
|
accessing encrypted USB device
I'm trying to get a McAfee encrypted USB stick to be usable under QNX4. I have succeeded to a certain extent, but not
to the extent of being able to remove the device and subsequently re-insert it and be able to access it. In particular
I'm performing the following steps:
1) Insert disk and finger-swipe to authenticate.
2) # io-usb
At this point, the output of usb shows that the device is recognized.
3) # Fsys.umass
At this point, the device /dev/hd1 is created.
4) # Fatfsys
At this point, the encrypted portion of the disk is accessible as /dos/c.
The unencrypted read-only portion does not appear.
5) # slay Fatfsys
/dos/c disappears.
6) # slay Fsys.umass
/dev/hd1 still exists.
7) # rm /dev/hd1
8) # slay io-usb
9) Remove and re-insert disk, and authenticate.
10) # io-usb
11) # Fsys.umass
=> "Can't attach to Fsys (Resource busy)
Any way I can recover? I'm using the July 2010 USB stack.
|
|
|
|
|
|
Pavol Kycina
|
Re: accessing encrypted USB device
|
|
Pavol Kycina
04/06/2011 7:10 AM
post84661
|
Re: accessing encrypted USB device
Hello,
do not slay Fsys.umass, just rm /dev/hd1 and it should terminate by itself.
Regards, PKY
|
|
|
|
|
|
William Parsons
|
Re: accessing encrypted USB device
|
|
William Parsons
04/06/2011 7:48 AM
post84665
|
Re: accessing encrypted USB device
Doesn't seem to. I tried
# rm /dev/hd1
but Fsys.umass keeps running.
If I now slay Fsys.umass and restart it, I still get the same error.
|
|
|
|
|
|
Pavol Kycina
|
Re: accessing encrypted USB device
|
|
Pavol Kycina
04/06/2011 8:33 AM
post84670
|
Re: accessing encrypted USB device
Are there any partitions on the drive?
output of " ls -l /dev/hd1* " shows only /dev/hd1?
Regards, PKY
> Doesn't seem to. I tried
> # rm /dev/hd1
>
> but Fsys.umass keeps running.
>
> If I now slay Fsys.umass and restart it, I still get the same error.
|
|
|
|
|
|
William Parsons
|
Re: accessing encrypted USB device
|
|
William Parsons
04/06/2011 9:48 AM
post84690
|
Re: accessing encrypted USB device
No. Running fdisk on /dev/hd1 shows no partitions of any type.
Incidentally, I tried the same sequence on a regular unencrypted disk and got the same results
(i.e., Fsys.umass does not go away if the device is removed, and if killed manually cannot be
restarted).
|
|
|
|
|
|
Oleg Bolshakov
|
Re: accessing encrypted USB device
|
|
Oleg Bolshakov
04/08/2011 7:44 AM
post84801
|
Re: accessing encrypted USB device
Hi William,
Please, post here output of following command. Launch it 1) before
starting Fsys.umass, 2) after this and 3) after slaying Fsys.umass and
removing /dev/hd1:
# ls -l /dev
It seems like several USB mass storage devices are present in your system.
--
Respectfully,
Oleg
> No. Running fdisk on /dev/hd1 shows no partitions of any type.
>
> Incidentally, I tried the same sequence on a regular unencrypted disk
> and got the same results (i.e., Fsys.umass does not go away if the
> device is removed, and if killed manually cannot be restarted).
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post84690
|
|
|
|
|
|
William Parsons
|
Re: accessing encrypted USB device
|
|
William Parsons
04/08/2011 1:42 PM
post84833
|
Re: accessing encrypted USB device
> Hi William,
>
> Please, post here output of following command. Launch it 1) before
> starting Fsys.umass, 2) after this and 3) after slaying Fsys.umass and
> removing /dev/hd1:
>
> # ls -l /dev
>
> It seems like several USB mass storage devices are present in your system.
>
I don't see that, but here's the output:
### After running io-usb:
total 3582371
brw------- 1 root root 2, 1 Dec 31 1969 cd0
crw--w--w- 1 root root 5, 1 Apr 08 13:28 con1
crw--w--w- 1 root root 5, 2 Apr 08 13:19 con2
crw-rw-rw- 1 root root 5, 3 Apr 08 13:13 con3
crw-rw-rw- 1 root root 5, 4 Apr 08 13:13 con4
crw-rw-rw- 1 root root 5, 5 Apr 08 13:13 con5
crw-rw-rw- 1 root root 5, 6 Apr 08 13:13 con6
brw------- 1 root root 2, 2 Dec 31 1969 hd0
brw------- 1 root root 2, 3 Dec 31 1969 hd0t77
brw------- 1 root root 2, 4 Dec 31 1969 hd0t78
crw------- 1 root root 6, 1 Apr 08 13:13 kbd
crw-rw-rw- 1 root root 4, 1 Apr 08 13:13 null
crw-rw-rw- 1 root root 8, 1 Apr 08 13:13 par1
crw-rw-rw- 1 root root 9, 1 Apr 08 13:13 ptyp0
crw-rw-rw- 1 root root 9, 2 Apr 08 13:13 ptyp1
crw-rw-rw- 1 root root 9, 3 Apr 08 13:13 ptyp2
crw-rw-rw- 1 root root 9, 4 Apr 08 13:13 ptyp3
crw-rw-rw- 1 root root 7, 1 Apr 08 13:13 ser1
crw-rw-rw- 1 root root 7, 2 Apr 08 13:13 ser2
drwxrwxrwt 2 root root 0 Dec 31 1969 shmem
crw-rw-rw- 1 root root 10, 1 Apr 08 13:13 ttyp0
crw-rw-rw- 1 root root 10, 2 Apr 08 13:13 ttyp1
crw-rw-rw- 1 root root 10, 3 Apr 08 13:13 ttyp2
crw-rw-rw- 1 root root 10, 4 Apr 08 13:13 ttyp3
cr--r--r-- 1 root root 13, 0 Apr 08 13:28 usb
### After running Fsys.umass:
total 6945063
brw------- 1 root root 2, 1 Dec 31 1969 cd0
brw------- 1 root root 14, 7 Apr 08 13:28 cd1
crw--w--w- 1 root root 5, 1 Apr 08 13:28 con1
crw--w--w- 1 root root 5, 2 Apr 08 13:19 con2
crw-rw-rw- 1 root root 5, 3 Apr 08 13:13 con3
crw-rw-rw- 1 root root 5, 4 Apr 08 13:13 con4
crw-rw-rw- 1 root root 5, 5 Apr 08 13:13 con5
crw-rw-rw- 1 root root 5, 6 Apr 08 13:13 con6
brw------- 1 root root 2, 2 Dec 31 1969 hd0
brw------- 1 root root 2, 3 Dec 31 1969 hd0t77
brw------- 1 root root 2, 4 Dec 31 1969 hd0t78
brw------- 1 root root 14, 8 Apr 08 13:28 hd1
crw------- 1 root root 6, 1 Apr 08 13:13 kbd
crw-rw-rw- 1 root root 4, 1 Apr 08 13:13 null
crw-rw-rw- 1 root root 8, 1 Apr 08 13:13 par1
crw-rw-rw- 1 root root 9, 1 Apr 08 13:13 ptyp0
crw-rw-rw- 1 root root 9, 2 Apr 08 13:13 ptyp1
crw-rw-rw- 1 root root 9, 3 Apr 08 13:13 ptyp2
crw-rw-rw- 1 root root 9, 4 Apr 08 13:13 ptyp3
crw-rw-rw- 1 root root 7, 1 Apr 08 13:13 ser1
crw-rw-rw- 1 root root 7, 2 Apr 08 13:13 ser2
drwxrwxrwt 2 root root 0 Dec 31 1969 shmem
crw-rw-rw- 1 root root 10, 1 Apr 08 13:13 ttyp0
crw-rw-rw- 1 root root 10, 2 Apr 08 13:13 ttyp1
crw-rw-rw- 1 root root 10, 3 Apr 08 13:13 ttyp2
crw-rw-rw- 1 root root 10, 4 Apr 08 13:13 ttyp3
cr--r--r-- 1 root root 13, 0 Apr 08 13:28 usb
### After slaying Fsys.umass and removing /dev/hd1:
total 4032935
brw------- 1 root root 2, 1 Dec 31 1969 cd0
brw------- 1 root root 14, 7 Apr 08 13:28 cd1
crw--w--w- 1 root root 5, 1 Apr 08 13:28...
View Full Message
|
|
|
|
|
|
Oleg Bolshakov
|
Re: accessing encrypted USB device
|
|
Oleg Bolshakov
04/08/2011 2:17 PM
post84835
|
Re: accessing encrypted USB device
William,
Cd1 device is also appeared. Do you have USB CD-ROM plugged? If so then
you have to remove /dev/cd1 as well as /dev/hd1. Please note that you have
to remove all devices which have been created by Fsys.umass before
restarting the driver.
--
Respectfully,
Oleg
> > Hi William,
> >
> > Please, post here output of following command. Launch it 1) before
> > starting Fsys.umass, 2) after this and 3) after slaying Fsys.umass
> > and removing /dev/hd1:
> >
> > # ls -l /dev
> >
> > It seems like several USB mass storage devices are present in your
> > system.
>
> I don't see that, but here's the output:
>
> ### After running io-usb:
> total 3582371
> brw------- 1 root root 2, 1 Dec 31 1969 cd0
> crw--w--w- 1 root root 5, 1 Apr 08 13:28 con1
> crw--w--w- 1 root root 5, 2 Apr 08 13:19 con2
> crw-rw-rw- 1 root root 5, 3 Apr 08 13:13 con3
> crw-rw-rw- 1 root root 5, 4 Apr 08 13:13 con4
> crw-rw-rw- 1 root root 5, 5 Apr 08 13:13 con5
> crw-rw-rw- 1 root root 5, 6 Apr 08 13:13 con6
> brw------- 1 root root 2, 2 Dec 31 1969 hd0
> brw------- 1 root root 2, 3 Dec 31 1969 hd0t77
> brw------- 1 root root 2, 4 Dec 31 1969 hd0t78
> crw------- 1 root root 6, 1 Apr 08 13:13 kbd
> crw-rw-rw- 1 root root 4, 1 Apr 08 13:13 null
> crw-rw-rw- 1 root root 8, 1 Apr 08 13:13 par1
> crw-rw-rw- 1 root root 9, 1 Apr 08 13:13 ptyp0
> crw-rw-rw- 1 root root 9, 2 Apr 08 13:13 ptyp1
> crw-rw-rw- 1 root root 9, 3 Apr 08 13:13 ptyp2
> crw-rw-rw- 1 root root 9, 4 Apr 08 13:13 ptyp3
> crw-rw-rw- 1 root root 7, 1 Apr 08 13:13 ser1
> crw-rw-rw- 1 root root 7, 2 Apr 08 13:13 ser2
> drwxrwxrwt 2 root root 0 Dec 31 1969 shmem
> crw-rw-rw- 1 root root 10, 1 Apr 08 13:13 ttyp0
> crw-rw-rw- 1 root root 10, 2 Apr 08 13:13 ttyp1
> crw-rw-rw- 1 root root 10, 3 Apr 08 13:13 ttyp2
> crw-rw-rw- 1 root root 10, 4 Apr 08 13:13 ttyp3
> cr--r--r-- 1 root root 13, 0 Apr 08 13:28 usb
> ### After running Fsys.umass:
> total 6945063
> brw------- 1 root root 2, 1 Dec 31 1969 cd0
> brw------- 1 root root 14, 7 Apr 08 13:28 cd1
> crw--w--w- 1 root root 5, 1 Apr 08 13:28 con1
> crw--w--w- 1 root root 5, 2 Apr 08 13:19 con2
> crw-rw-rw- 1 root root 5, 3 Apr 08 13:13 con3
> crw-rw-rw- 1 root root 5, 4 Apr 08 13:13 con4
> crw-rw-rw- 1 root root 5, 5 Apr 08 13:13 con5
> crw-rw-rw- 1 root root 5, 6 Apr 08 13:13 con6
> brw------- 1 root root 2, 2 Dec 31 1969 hd0
> brw------- 1 root root 2, 3 Dec 31 1969 hd0t77
> brw------- 1 root root 2, 4 Dec 31 1969 hd0t78
> brw------- 1 root root 14, 8 Apr 08 13:28 hd1
> crw------- 1 root root 6, 1 Apr 08 13:13 kbd
> crw-rw-rw- 1 root root 4, 1 Apr 08 13:13 null
> crw-rw-rw- 1 root root 8, 1 Apr 08 13:13 par1
> crw-rw-rw- 1 root root 9, 1 Apr 08 13:13 ptyp0
> crw-rw-rw- 1 root root 9, 2 Apr 08 13:13 ptyp1
> crw-rw-rw- 1 root root 9, 3 Apr 08 13:13 ptyp2
> crw-rw-rw- 1 root root 9, 4 Apr 08 13:13 ptyp3
> crw-rw-rw- 1 root root 7, 1 Apr 08 13:13 ser1
> crw-rw-rw- 1 root root 7, 2 Apr 08 13:13 ser2
> drwxrwxrwt 2 root root ...
View Full Message
|
|
|
|
|
|
William Parsons
|
Re: accessing encrypted USB device
|
|
William Parsons
04/08/2011 3:31 PM
post84837
|
Re: accessing encrypted USB device
> William,
>
> Cd1 device is also appeared. Do you have USB CD-ROM plugged? If so then
> you have to remove /dev/cd1 as well as /dev/hd1. Please note that you have
> to remove all devices which have been created by Fsys.umass before
> restarting the driver.
>
No USB CD, *but* apparently the read-only portion of the encrypted disk shows
up as a CD, which I didn't notice before! So, removing the "CD" allows Fsys.umass
to be restarted. Thanks a lot!
--
William
|
|
|
|
|
|
