- From: Morgan Hedges <morgan.hedges@gosource.com.au>
- Date: Wed, 26 Oct 2022 09:50:26 +1100
- To: W3C Credentials CG <public-credentials@w3.org>
- Message-ID: <CAAsoEQyotcrtBKG5zJm9vky2CFoTW0vGeUEitvgvyUrVv__ruA@mail.gmail.com>
Hello CCG, Main question: Are there any FIPS compliant mechanisms for selective disclosure, or at least candidates? My understanding is that BBS+ is unlikely to become a FIPS standard due to the focus on post-quantum algorithms for new crypto work (please correct me here). One recently-discussed workaround seems to be using multiple proofs: e.g. one a FIPS compliant one, and a BBS+ one. But of course this means one can't use selective disclosure when interacting with a verifier who requires the FIPS proof. The especially naive bit- I think/presume it's not as easy as just using a FIPS compliant signature algorithm on some kind of "hash of hashes" (obvious example: a Merkle tree, something like MerkleDisclosureProof2021 <https://w3c-ccg.github.io/Merkle-Disclosure-2021/>), but despite spending some time with the FIPS-186-5 draft, I'm still not clear why this should be ruled out. Much appreciated if anyone shed some light. thanks, Morgan -- --- The content of this email and attachments are considered confidential. If you are not the intended recipient, please delete the email and any copies, and notify the sender immediately. The information in this email must only be used, reproduced, copied, or disclosed for the purposes for which it was supplied.
Received on Tuesday, 25 October 2022 22:50:51 UTC