Szczepan Zalega

> > The 14-bytes difference should not make the call divided into multiple parts. > > By the way, even a 19-character passphrase did not trigger the issue. This starts...

@robinkrahl do attempt counters change after executing the test?

I do not see anything in the firmware regarding the PIN validation so far. To check with the actual debugging.

Hi! Thank you for linking this very interesting read! We will take a look into applying the concluded fixes. Confirming we are using not affected GCC version at the moment...

Update: currently merged with a static value set on the stack protector constant. To be done: - [ ] get stack protector constant from the MCU's memory, updated in the...

Hi! 1. The firmware update feature is available only since v0.11, meaning the Nitrokey Pro v0.10 devices and older cannot be updated by solely software means as well. Additionally one...

@tlaurion Hi! I do not think we ended up with the proper mounting for the development, but will pass the question further and get back if there would be anything...

@tlaurion Attaching image of the pogo pin adapter below (centered on the actual pins connecting to the PCB): 

Hi! Sorry for delay. I believe smart card synchronization code is indeed at fault here. I can add a workaround to libnitrokey to avoid this case. Is it still blocking...

Just to show current state - current memory limit for: - OTP: 512 bytes+ - PWS: 2*512 bytes Additionally, one USB packet (USB 1.1) cannot take more than 64 bytes...