 | | | How does USB work in RHEL? | How does USB work in RHEL? 2003-11-11 - By Your Name
Back
Ok, leave off the obvious answers... I am looking for soemthing specific...
We have been trying with three different USB keys and have found that
Red Hat does NOT automount them as drives when inserted. It also adds
the key ID to a database somewhere (/proc/usb perhaps?) so whenever a
particular key is inserted, it is given the same scsi device every time.
The problem arrises when you want to be able to automount a usb key on
several different machines, or more importantly, automount several
different keys on several differetn machines.
Sure, I could sit down with every key I have and set up autofs on each
machine to automount the keys, BUT that would be a lot of work for a
company or group with more than a handfull of machines and keys.
Why is it that Red Hat handles USBKeys in this manner?
What handles the transaction? What decides that this key gets
/dev/sda1, and that key gets /dev/sdb1??
Also, why does the key info in /proc not get erased when the key is
removed???
I can plug various keys in and out of a machine wiht SuSE SLES8 all day
long, and every time the key is scanned, assigned a drive ID, and
mounted to a mount point, all without me having to do anything but plug
it in.
With RHEL 3, however, out of the box, straight install, all that happens
is the scan and the assignment of drive ID. No automounting, or anyting
of that nature.
I understand the security implications of such a thing, but it seems to
me that there should be a differetn way of doing it... perhaps a
passcode challenge before the key is mounted, or soemthing like that.
At the very least, if I knew where to look in the source code, I could
find the part that removes the USB info from /proc and maybe change that
so that the drive designation disappears when the key is removed. that
way any USB Key I am using will be assigned /dev/sda1, unless there is
another key already present.
Any ideas???
Cheers
Jeff
|
|
|