-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serialization #11
base: devel
Are you sure you want to change the base?
Serialization #11
Conversation
Hi @YSaxon, thank you for your contribution. I'm just wondering if it's a good idea to bring in I guess that leaving the binary serialization out-of-scope would make the feature (and the library itself) more versatile ? Do you have any thoughts or strong preferences here ? |
@bodik |
excelent, thank you |
…apping.enabled future function would change currently expected data representation ``` You are using deprecated functionality which will change in the next major version of ... This changes the keys and values used by the webauthn data classes when accessed using the Mapping (dict) interface (eg. user_entity["id"] and the from_dict() methods) to be JSON-friendly and align with the current draft of the next WebAuthn Level specification. For the most part, this means that binary values (bytes) are represented as URL-safe base64 encoded strings instead. ``` also concerns bodik#13
@YSaxon I've made some changes and squashes. would you review the current PR please ? |
@YSaxon ping, still interested in this ? |
A couple of methods to serialize the software token, (optionally with a password on the private key).