UAF1.1 Server-Reg-Resp-4/F-8 FinalChallengeParams.channelBinding with "empty" string: wrong content is sent

[purrema1]

By submitting this issue you are acknowledging that any information regarding this issue will be publicly available.

If you have privacy concerns, please email conformance-tools@fidoalliance.org

FIRST PRE CHECK

• [X] I SOLEMNLY SWEAR THAT I HAVE SEARCHED DOCUMENTATION AND WAS NOT ABLE TO RESOLVE MY ISSUE

What protocol are you implementing?

• [ ] FIDO2 Server
• [ ] CTAP2.0
• [ ] CTAP2.1
• [X] UAF 1.1
• [ ] U2F 1.1
• [ ] U2F 1.2

NOTE: UAF 1.0 certification have been officially sunset. U2F 1.2 only supported version of U2F.

What is your implementation class?

• [ ] Security Key / FIDO2 / U2F authenticators
• [X] Server
• [ ] UAF Client-ASM-Authenticator combo
• [ ] UAF Client
• [ ] UAF ASM-Authenticator

If you are platform authenticator vendor, please email conformance-tools@fidoalliance.org

What is the version of the tool are you using?

v1.6.37

What is the OS and the version are you running?

For desktop tools

• [ ] OSX
• [X] Windows
• [ ] Linux

For UAF mobile tools

• [ ] iOS
• [ ] Android

Issue description

In UAF 1.1 Server test scenario: 'Server-Reg-Resp-4/F-8 FinalChallengeParams.channelBinding with "empty" string', the tool sends erroneously an empty dictionary ({}), instead of an "empty" string ('').

As an empty dictionary is valid (see #640) we cannot reject it and therefore we cannot pass this test scenario.

[yackermann]

Resolved in 1.6.46

[purrema1]

@herrjemand thx! ok!