- From: Arshad Noor via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Aug 2021 16:56:30 +0000
- To: public-webauthn@w3.org
You could continue to be "lazy" if you used an open-source, FIDO Certified server that supports most, if not all, attestation formats. You could even get "lazier" by not having to write any FIDO code and just focus on the business application. :-D https://sourceforge.net/projects/strongkeyfido https://github.com/strongkey/fido2 Arshad Noor StrongKey On 8/6/21 8:24 AM, DanielSanchezDiaz wrote: > Hmm. Well the first thing that comes to mind is the case in which the > relying party only supports one kind of attestation type format and > would like to convey that to the authenticator. I'm thinking then it > would be useful for an authenticator to support more than one > attestation type format. > That being said, another solution is for the relying party to simply > implement support for whatever attestation type format the authenticator > uses. > My hope was that I could be lazy and goad most authenticators into using > packed to avoid more work haha. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webauthn/issues/1659#issuecomment-894335428>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABWSVTQ4HTKOIWWZVAGWIW3T3P5B3ANCNFSM5BVAUEUA>. > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>. > -- GitHub Notification of comment by arshadnoor Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1659#issuecomment-894389254 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 August 2021 16:56:31 UTC