Firstyear

@emlun An extra reason to follow my previous comment, is for the RP if the authenticator sends an unsolicited discoverable credential, this wouldn't be indicated in credProps, so having the...

> > Some protos like CTAP2.1 enforce that if rk was sent from the browser to the device it MUST create an rk or error ( https://fidoalliance.org/specs/fido-v2.1-rd-20210309/fido-client-to-authenticator-protocol-v2.1-rd-20210309.html#op-makecred-step-rk ) but this...

To expand on this to make it a bit clearer. Apple's Passkeys will *not* register if you request attestation conveyance direct/indirect. As a result, when people go to use Passkeys,...

Hey there, I think splitting this up is not a good idea. We require crossbeam to eventually become system-level packaged in an RPM else we are unable to use it...

So for clarity: * Crossbeam will remain a single crate on crates.io despite the multi-git approach? * The single crate on crates.io will expose all the libraries of crossbeam, ie...

That second point is the important one I think. It really needs to expose all the required parts. Like I think it would be complex to have a crate for...

But this comes back to: Do you then have an rpm for crossbeam, and an rpm for crossbeam-epoch? do they become separate crates? If this happens it creates barriers to...

Having both available inside of crossbeam would probably be a good option too, because then structures could be build using the choice of EBR or HP that suited correctly.

I can not code in PHP, so I can not contribute sorry.

Code looks good to me :)