W3C home > Mailing lists > Public > public-webauthn@w3.org > January 2022

Re: [webauthn] Provide request deserialization, response serialization (#1683)

From: Firstyear via GitHub <sysbot+gh@w3.org>
Date: Thu, 20 Jan 2022 02:12:26 +0000
To: public-webauthn@w3.org
Message-ID: <issue_comment.created-1017050324-1642644745-sysbot+gh@w3.org>
> > As the author of Webauthn-RS, who implemented the demo site and examples for all client side browser elements in WASM and NOT Javascript, I'd like to disagree. There is also a huge and growing interest in WASM for client side elements in replacement of JS.
> 
> Can you elaborate on this example of client side usage via WASM which is outside local demonstration purposes?

What is there that needs elaborating? Instead of using JS, you use WASM. As a result, and changes to make it easier to get from JSON -> navigator.credentials.get/create need to work in a WASM context. 


> 
> Also, do you have specifics in mind for ways to make the deserialization/serialization more accessible to WASM outside providing the helpers for a consistent format being already described here, e.g. serialization and deserialization formats for requests and responses?

Yes, I have previously described these here https://github.com/w3c/webauthn/issues/1619 


-- 
GitHub Notification of comment by Firstyear
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1683#issuecomment-1017050324 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 January 2022 02:12:32 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:45 UTC