Non-ASCII characters in metadata statement description

51 views
Skip to first unread message

Andrey Paramonov

unread,
Mar 21, 2022, 4:45:12 PM3/21/22
to FIDO Dev (fido-dev)
Greetings,

The specification requires the description contain only ASCII characters, but the metadata blob downloaded from https://fidoalliance.org/metadata contains some statements with non-ASCII characters, e.g.

{
  "aaguid": "d821a7d4-e97c-4cb6-bd82-4237731fd4be",
  "metadataStatement": {
    ...
    "description": "Hyper FIDO® Bio Security Key",
    "timeOfLastStatusChange": "2021-02-09”
  }
}

Does anyone know if it’s supposed to be fixed in the upcoming blobs? Or once it's there it will stay like this forever?

Thanks
Andre

Ackermann Yuriy

unread,
Mar 22, 2022, 12:02:30 AM3/22/22
to Andrey Paramonov, FIDO Dev (fido-dev)
Is that for MDS2 or MDS3?

Yuriy Ackermann
FIDO, Identity, Standards
skype: ackermann.yuriy
github: @herrjemand
twitter: @herrjemand
medium: @herrjemand


This message (including any attachments) may contain confidential, proprietary, privileged and/or private information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited.

--
You received this message because you are subscribed to the Google Groups "FIDO Dev (fido-dev)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fido-dev+u...@fidoalliance.org.
To view this discussion on the web visit https://groups.google.com/a/fidoalliance.org/d/msgid/fido-dev/7e5ebb99-8478-4f6b-81f6-84d1d77dafben%40fidoalliance.org.

Andrey Paramonov

unread,
Mar 22, 2022, 9:17:29 AM3/22/22
to FIDO Dev (fido-dev), Ackermann Yuriy, FIDO Dev (fido-dev), Andrey Paramonov
MDS3

Andrey Paramonov

unread,
Apr 19, 2022, 1:31:43 PM4/19/22
to FIDO Dev (fido-dev), Andrey Paramonov, Ackermann Yuriy
In general, what's the procedure to correct invalid value found in the MDS3 metadata statement? Should there be a PR created in FIDO GitHub repo? or any form submitted?
Reply all
Reply to author
Forward
0 new messages