mirror of
https://github.com/trezor/trezor-firmware.git
synced 2024-11-25 00:48:19 +00:00
8f1d33d5f9
for firmware builds we still use arm-none-eabi-gcc via $(PREFIX)gcc [no changelog] |
||
---|---|---|
.. | ||
.gitignore | ||
dev.cc | ||
dsa_sig.c | ||
dsa_sig.h | ||
hash-internal.h | ||
hidapi-udp.c | ||
hidapi.h | ||
HIDTest.cc | ||
LICENSE | ||
Makefile | ||
p256_ec.c | ||
p256_ecdsa.c | ||
p256_ecdsa.h | ||
p256.c | ||
p256.h | ||
README | ||
sha256.c | ||
sha256.h | ||
u2f_hid.h | ||
u2f_util.cc | ||
u2f_util.h | ||
u2f.h | ||
U2FTest.cc | ||
UPSTREAM |
WHAT: A couple of self-contained u2f HID device conformance tests: HIDTest to check compliance at the usb HID communication layer. U2FTest to check compliance at the application layer. DEPENDENCIES: git clone https://github.com/signal11/hidapi git clone -b lollipop-release https://android.googlesource.com/platform/system/core linux: sudo apt-get install libudev-dev BUILD: linux, mac: make windows: nmake -f Makefile.win - if you have an old vc compiler, consider adding http://msinttypes.googlecode.com/svn/trunk/stdint.h or similar to your vc include directory. RUN: ./list to find path of device to test (e.g. /dev/hidraw3) ./HIDTest $PATH [args]? to test low level communications with device. On windows? - Make sure to keep the quotes around the path. - Try https://github.com/adoxa/ansicon to get ANSI colors. On linux? - Make sure path is rw for your uid. Typically, a udev rule that adds rw for group plugdev goes a long way. ./U2FTest $PATH [args]? to test u2f application layer functionality of device. Additional commandline arguments: Add -a to continue execution after an error. Add -p to pause after each error. Add -v and -V to get more verbose output, down to the usb frames with -V. Add -b to U2FTest in case fob under test is of the insert / remove class and does not have a user-presence button.