Right now most of the USB problems have been dealt with and we have moved on to the implementation of the U2F functionality.
First of was the implementation of the generation of key handles. A key handle for U2F is a unique tag that the device assigns on a trusty party and it uses that one for subsequent authentication requests. In our approach we don't store the key handle, but we compute from the appID, which stays the same for every trusted party, and we wrap the private device key as a key handle.
A lot of these actions include the use of PolarSSL, which is a library for the ARM architecture which deals with common cryptographic and hashing algorithms. I don't a lot to tell yet about that, as I'm still learning about how to use it, but I'll keep you posted.
First of was the implementation of the generation of key handles. A key handle for U2F is a unique tag that the device assigns on a trusty party and it uses that one for subsequent authentication requests. In our approach we don't store the key handle, but we compute from the appID, which stays the same for every trusted party, and we wrap the private device key as a key handle.
A lot of these actions include the use of PolarSSL, which is a library for the ARM architecture which deals with common cryptographic and hashing algorithms. I don't a lot to tell yet about that, as I'm still learning about how to use it, but I'll keep you posted.
