17 Commits (49645ba2778c4bf0070bf8232f9933692fd6474d)

Author	SHA1	Message	Date
Saleem Rashid	25b9bfd97b	timer: Use Cortex-M3 SysTick timers ... Removed `usbDelay(uint32_t cycles)`, added `usbSleep(uint32_t millis)` The same method signature could cause silent code breakage at runtime, as opposed to noisy code breakage at compile time which is the better kind.	8 years ago
Pavol Rusnak	5e57a1ceaf	Merge branch 'u2f'	8 years ago
Pavol Rusnak	b1e3c52b08	remove DialogIcon enum, use bitmap structure directly	8 years ago
Jochen Hoenicke	73e7d82e3f	Allow initialize() to abort PIN wait	8 years ago
Jochen Hoenicke	053fe7cb66	Remove Cancel Option ... U2F doesn't allow cancellation on device. Also fix button state in protect. This fixes the following bug: 1. wipe device 2. press and hold right button, click left button to cancel. 3. release all buttons. 4. wipe device again, now automatic.	8 years ago
Jochen Hoenicke	68b34af19e	More standard conform behaviour ... Tested with u2f-ref-code/u2f-tests. Known incompatibility: - changed challenge invalidates button press.	8 years ago
Jochen Hoenicke	da98a3a6fd	Don't reflash storage after each PIN entry ... Instead of reflashing the whole storage, we use a designated area in the second storage block, where we mark each PIN failure by a single zero bit. This is because one can set bits in flash to zero but not to one. If the PIN was entered successfully the whole word is set to zero and the next word stores the new PIN failure counter.	8 years ago
Jochen Hoenicke	218b9984bb	New usbDelay that delays and handles USB requests ... Added usbDelay that polls usb port (for system requests) while delaying. This is called instead of delay in the button and pin delay functions. Experimental evaluation gave that the cycle count should be roughly divided by 28.5.	9 years ago
Pavol Rusnak	7d8fb375f0	seconds counter during pin lockdown	9 years ago
Jochen Hoenicke	286ee0525c	PIN handling - constant time. ... This diff contains three changes. 1. Make timing isPinCorrect independent of storage.pin, to avoid timing attacks 2. Only update failed PIN counter if the user entered a PIN. Of course, the fail counter is still incremented, before the PIN is checked. 3. Don't cache the PIN, but just the fact that the PIN was entered. The cache should be in sync with storage.pin in any case.	10 years ago
Pavol Rusnak	40efefc571	rework pin handling	10 years ago
Pavol Rusnak	012d38a9a0	increasePinFails before asking PIN	10 years ago
Pavol Rusnak	849e758eb4	double the delay before buttonupdate	10 years ago
Pavol Rusnak	465ec2104b	throw UnexpectedMessage failure on unknown messages	10 years ago
Pavol Rusnak	2b68813a4c	adjust script_sig size for use with multisig ... adjust delays used when wrong pin is entered	10 years ago
Pavol Rusnak	d7169a342c	fix initialize handling in interactive mode	10 years ago
Pavol Rusnak	0d0a1ab5f2	import v1.0.0	10 years ago