Clément Delafargue

yeah, relying on deny policies is a bit more risky indeed. From what I understood of your case, putting group info in the same fact as the user id seems...

would `reject if` be a good solution now that it is available?

Third-party blocks carry the public key that can be used to verify them, so the external signatures are only verified once, with the public key carried in the block. The...

everything has been merged except the FFI branch so no need for this branch anymore

Thanks for the report. The spec indeed mentions the preferred encoding to be url-safe base64, which refers to base64 with an URL-safe alphabet, according to the relevant RFC. This base64-variant...

> I'm not decided yet on the best name for the functions still allowing the old format, between `Biscuit::unsafe_deprecated_deserialize` and `UnverifiedBiscuit::unsafe_from` I’d go for the most explicit. I read `unsafe_from`...

I think we should document the signature scheme to make a few things clearer: - imo the version should be signed (if defined) - the previous key should not be...

Yeah, my idea was to catch the exception and display a message advising to run it from `git-bash` or to use putty (I'm not sure it's doable to use putty...

I have limited knowledge in the go standard libs and its idioms, so contributions on this front would be great. I can help aligning the API with the expected use...

I think that would be useful, yes. For reference, the rust implementation exposes quite detailed information about the failed checks / policies: https://github.com/biscuit-auth/biscuit-rust/blob/main/biscuit-auth/src/error.rs#L174 Having the check code without the block...