PDA

View Full Version : OnlyKey isn't working after a recent update



5aru
2017-12-19, 05:29
On Dec 12th, I updated my laptop and after that, my OnlyKey (https://crp.to/) started giving me weird outputs. I thought that it might be a defective key, so I tested my spare and I was having the same issue. I even went and tested it out on different setups and the keys seemed to work fine on other computers. I've had a spare desktop lying around for a while and have been meaning to use it, so I took the opportunity to see if Kali might be the problem. Everything seemed to work on the live disk, but after an install and update I began having the same issue. So the problem seems to be with something installed in that updated. I've checked config files, scouring /etc and dpkg-reconfigure, but I haven't been able to find the problem.

This seems to only be happening within the X server environment; both XFCE and KDE are having the same problem. I've opened up a tty a couple times just to test it out, and it works just fine in there.

So below I've included some output...

cat /var/log/dpkg.log | grep -E '2017-12-12 0' | grep -E 'status installed'


The output was too long, I've included it here (https://pastebin.com/rhg0bnpU)


dmesg


[ 3658.524723] usb 1-11: New USB device found, idVendor=16c0, idProduct=0486
[ 3658.524728] usb 1-11: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3658.524732] usb 1-11: Product: Keyboard/RawHID
[ 3658.524734] usb 1-11: Manufacturer: Teensyduino
[ 3658.524737] usb 1-11: SerialNumber: 4294967295
[ 3658.526177] input: Teensyduino Keyboard/RawHID as /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/0003:16C0:0486.0003/input/input25
[ 3658.584302] hid-generic 0003:16C0:0486.0003: input,hidraw0: USB HID v1.11 Keyboard [Teensyduino Keyboard/RawHID] on usb-0000:00:14.0-11/input1
[ 3658.585583] hid-generic 0003:16C0:0486.0004: hiddev0,hidraw1: USB HID v1.11 Device [Teensyduino Keyboard/RawHID] on usb-0000:00:14.0-11/input0


lsusb -v


Bus 001 Device 006: ID 16c0:0486 Van Ooijen Technische Informatica Teensyduino RawHID
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x16c0 Van Ooijen Technische Informatica
idProduct 0x0486 Teensyduino RawHID
bcdDevice 1.00
iManufacturer 1 Teensyduino
iProduct 2 Keyboard/RawHID
iSerial 3 4294967295
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 66
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 85
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 28
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Device Status: 0x0000
(Bus Powered)


setxkbmap -print -verbose 10


Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: pc105
layout: us
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+inet(evdev)
geometry: pc(pc105)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(evdev)" };
xkb_geometry { include "pc(pc105)" };
};


cat /var/log/Xorg.0.log (snippet)


[ 376.213] (II) config/udev: removing device Teensyduino Keyboard/RawHID
[ 376.213] (II) event1 - (II) Teensyduino Keyboard/RawHID: (II) device removed
[ 376.237] (II) UnloadModule: "libinput"
[ 3658.690] (II) config/udev: Adding input device Teensyduino Keyboard/RawHID (/dev/input/event1)
[ 3658.690] (**) Teensyduino Keyboard/RawHID: Applying InputClass "libinput keyboard catchall"
[ 3658.690] (II) Using input driver 'libinput' for 'Teensyduino Keyboard/RawHID'
[ 3658.690] (**) Teensyduino Keyboard/RawHID: always reports core events
[ 3658.690] (**) Option "Device" "/dev/input/event1"
[ 3658.690] (**) Option "_source" "server/udev"
[ 3658.692] (II) event1 - (II) Teensyduino Keyboard/RawHID: (II) is tagged by udev as: Keyboard
[ 3658.692] (II) event1 - (II) Teensyduino Keyboard/RawHID: (II) device is a keyboard
[ 3658.692] (II) event1 - (II) Teensyduino Keyboard/RawHID: (II) device removed
[ 3658.720] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/0003:16C0:0486.0003/input/input25/event1"
[ 3658.720] (II) XINPUT: Adding extended input device "Teensyduino Keyboard/RawHID" (type: KEYBOARD, id 11)
[ 3658.720] (**) Option "xkb_model" "pc105"
[ 3658.720] (**) Option "xkb_layout" "us"
[ 3658.720] (WW) Option "xkb_variant" requires a string value
[ 3658.720] (WW) Option "xkb_options" requires a string value
[ 3658.722] (II) event1 - (II) Teensyduino Keyboard/RawHID: (II) is tagged by udev as: Keyboard
[ 3658.722] (II) event1 - (II) Teensyduino Keyboard/RawHID: (II) device is a keyboard


journalctl -xe


Dec 19 00:22:01 localhost kernel: usb 1-11: new full-speed USB device number 7 using xhci_hcd
Dec 19 00:22:01 localhost kernel: usb 1-11: New USB device found, idVendor=16c0, idProduct=0486
Dec 19 00:22:01 localhost kernel: usb 1-11: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 19 00:22:01 localhost kernel: usb 1-11: Product: Keyboard/RawHID
Dec 19 00:22:01 localhost kernel: usb 1-11: Manufacturer: Teensyduino
Dec 19 00:22:01 localhost kernel: usb 1-11: SerialNumber: 4294967295
Dec 19 00:22:01 localhost kernel: input: Teensyduino Keyboard/RawHID as /devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/0003:16C0:048
Dec 19 00:22:01 localhost kernel: hid-generic 0003:16C0:0486.0005: input,hidraw0: USB HID v1.11 Keyboard [Teensyduino Keyboard/RawHID] on
Dec 19 00:22:01 localhost kernel: hid-generic 0003:16C0:0486.0006: hiddev0,hidraw1: USB HID v1.11 Device [Teensyduino Keyboard/RawHID] on
Dec 19 00:22:01 localhost upowerd[997]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0/0003:16C0:0486
Dec 19 00:22:01 localhost upowerd[997]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0
Dec 19 00:22:02 localhost systemd-logind[755]: Watching system buttons on /dev/input/event1 (Teensyduino Keyboard/RawHID)
Dec 19 00:22:02 localhost upowerd[997]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/0003:16C0:0486
Dec 19 00:22:02 localhost upowerd[997]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1
Dec 19 00:22:02 localhost upowerd[997]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-11


If you have and idea what is going on, I would really appreciate the help. I use this key for work and it's getting frustrating. If we can pin this down, I'll be happy to file the bug report.

5aru
2017-12-19, 17:14
I just realized that I forgot to give an example of how it is actually screwing up

For example (Not actual passwords):


The correct password would be:
Ggjsr2fwy*XL#3vNr<T}RE<Q/4+4YUV:vTBq:!!HA$zZBH3fK-"pZ

And the OnlyKey is giving me:
ggjsr2fwy8Xl33vNr<t]re<q/4=4yuV;vtBq;11ha4zZBh3fk-'pZ

5aru
2017-12-20, 02:52
A couple days ago I posted to the OnlyKey support forums. And I finally got a lead on the issue. Apparently someone has already written a patch that will be included in the next firmware update.

https://groups.google.com/forum/#!category-topic/onlykey/linux-issues/ch5dMPEf-z0