Invalid filename char in serial number
swsnyder at snydernet.net
Mon Apr 11 18:25:11 BST 2011
># ekey-ulusbd -b002 -d007 -p/var/run/entropykeys/EKxxxxx -P/var/run/ekey-ulusbd-EKxxxxx.pid -D
Using the method above I got my CentOS 5.6 system to at least recognize that this device is present.
>I am unsure what the kernel situation is on CentOS5. If the CDC-ACM is fixed
>in that kernel then you don't need the ulusbd. However I would be careful when
>testing that, as some of the failure modes seen with CDC-ACM involve crashing
>the host kernel entirely.
I'd like to avoid the user-space app if possible, and don't mind locking up my kernel once or twice to test CDC-ADM method.
Given that my ancient udev won't automatically create the /dev/entropykey devnode, what is my next course of action? The instructions assume that the devnode is created automatically, so already I'm off the path just by not having this devnode present for detection of ekeyd.
Behavior with udev using rules in file 60-UDEKEY01.rules: udev will create a /dev/ttyACM0 devnode, but will monopolize the USB device, precluding the use of the ekey-ulusbd scheme.
Behavior with udev using rules in file 60-UDEKEY01-UDS.rules: leaves the USB device available to ekey-ulusbd, but creates no devnodes (as far as I can tell).
Bus 003 Device 001: ID 0000:0000
Bus 003 Device 002: ID 20df:0001 Simtec Electronics Entropy Key [UDEKEY01]
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
]# ekeydctl list
5,NO,Long-Term-Key is bad,/var/run/entropykeys/XXXXXXXXXXXXXXXX,XXXXXXXXXXXXXXXX
More information about the EntropyKey-users