{"push_id":3018375832,"size":1,"distinct_size":1,"ref":"refs/heads/attestation-type-trust-path","head":"010884de3c3dc120cec34d1f762a60be9e29b234","before":"f4a834cb6aa784d74f2b624b3d46aa259511bd10","commits":[{"sha":"010884de3c3dc120cec34d1f762a60be9e29b234","author":{"name":"Bart de Water","email":"07181460b52b61d40b5a8ef68188eaccc50d36e4@gmail.com"},"message":"feat: expose attestation type and trust path after validation\n\nThe WebAuthn spec notes the following:\n\n> Attestation statements conveying attestations of type AttCA use the same data structure as attestation statements conveying attestations of type Basic, so the two attestation types are, in general, distinguishable only with externally provided knowledge regarding the contents of the attestation certificates conveyed in the attestation\n\nRetrieving and managing this external data from the FIDO Metadata Service is (for now) up to the implementing application if so desired.","distinct":true,"url":"https://api.github.com/repos/bdewater/webauthn-ruby/commits/010884de3c3dc120cec34d1f762a60be9e29b234"}]}
{"actor":{"display_login":"bdewater"}}