fido-alliance / jovasco-u2f-ref-code Goto Github PK

This is a bug in Windows, fixed in PR #6 , only tested with 1.2 patch applied.

I have Windows 10 and Visual Studio Community 2017.
I installed the default environment for Desktop C/C++ application and among other modules:

• VC++ 2015.3 v14 toolset for desktop
• Windows Universal CRT SDK

When I try to build the projet I get:
Error C1107 could not find assembly 'platform.winmd': please specify the assembly search path using /AI or by setting the LIBPATH environment variable

I then installed Visual Studio 2015, still got same error but on other file: Windows.winmd

I found some pointers on these issue but it requires to change some parameters in Project Properties > C/C++ but I don't have this section available (the project seems not to be identified as a C++ project, in ProjectDefaults I have the field .NET Target Framework Version).

I found the required files (for example platform.winmd) in Visual Studio folder but cannot acces the corresponding parameter to set in properties.

Hi,
I was reviewing the BLE Testing Tool Source Code and realized a delay for 2000 ms in u2f-ref-code/u2f-tests/BLE/BLETest/BLETransportTests.cpp:227 that helps Testing Tool to collect all Error Replies (Error Messages starts with 0xBF).

However, waiting 2000 ms creates a race conditions kErrorWaitMillis (which is 2000 ms, please see U2F BLE 1.1 Spec for kErrorWaitMillis). We believe that 2000ms is way to long to collect error messages.

If we would like to wait to collect error messages, 1000 ms is more than enough in my opinion.

What do you think about this?

Thank you,

Hi,
Would you please comment on which spec justifies this test case? It would be generally very helpful to match the test cases with the ISO spec so that we can also refer to it as common ground.

As far as I see it and in line with ISO/IEC 7816, 0x6700 is not the right response.

Thank you!

I have download BLE test tools from github and successfully compiled it.
After I executed the later version of test tools (1.1.2 and 1.1.3 which have BLECertificationTool.exe), I found the test tools didn’t receive response of commands (PIN, Message, …). But after executing 1.0 test tool (BLETest.exe), the new test tools executed behind will successfully receive the responses and will go on for further testing items.

I checked the source codes and found almost no difference in major functions except the latest codes support only for visual studio 2015. And I guess the registering notifications is not succeeded because the request is received and replied in my BLE devices.
Maybe there are some difference between test tools in the very beginning process before first request. Please help me to find solution.

My working station is win10, 64-bit, build 14393. The bluetooth module is Qualcomm Atheros.

PR #4

Build:
BLECertTool-1.2.0.zip