Entropy Key - Operating system known issues
===========================================

The following is the list of operating systems known to have issues
with the Entropy Key.

CentOS 5
--------

The Kernel (2.6.18-128.el5) in CentOS 5 appears to have significant
issues with the CDC ACM code in it.  Within moments of an Entropy Key
being accessed in this manner, the kernel will lock solid requiring a
reboot of the system.

This means that the use of the ekey-ulusbd is required on CentOS 5.

Unfortunately the version of udev in CentOS 5 is not supported by our
udev rules at this time.  As a result, Entropy Keys will not
automatically start properly but can be added manually.

Do not, under any circumstance, use the TTY interface when using
Entropy Keys under CentOS 5.

If you require to use an Entropy Key under CentOS 5, the following may
be of use:


1. To determine the bus and device number of an Entropy Key, run 'lsusb'

E.g.

[root@centos5 ~]# lsusb
Bus 001 Device 001: ID 0000:0000  
Bus 002 Device 007: ID 20df:0001  
Bus 002 Device 001: ID 0000:0000  
Bus 002 Device 002: ID 0e0f:0002  

Note the line which has ID 20df:0001.  This is the Entropy Key.  On
more modern operating systems, or if you have manually updated the
usb.ids file from the Linux USB ID database, the name 'Simtec
Electronics Entropy Key [UDEKEY01]' will also be displayed on this
line.

For the following you will need to know the Entropy Key's serial
number which looks something like: NwBvBlg3OTBJORFD

2. To start the ekey-ulusbd, run:

[root@centos5 ~]# mkdir -p /var/run/entropykeys
[root@centos5 ~]# ekey-ulusbd -b002 -d007 -p/var/run/entropykeys/keyserialnumber -P/var/run/ekey-ulusbd-keyserialnumber.pid -D

3. To attach the key to a running ekeyd, then run:

[root@centos5 ~]# ekeydctl add /var/run/entropykeys/keyserialnumber

4. To check the status, run:

[root@centos5 ~]# ekeydctl list

