Closed Stebalien closed 1 week ago
🔒 Could not start CI tests due to missing safe PR label. Please contact a DEDIS maintainer.
🔒 Could not start CI tests due to missing safe PR label. Please contact a DEDIS maintainer.
🔒 Could not start CI tests due to missing safe PR label. Please contact a DEDIS maintainer.
🔒 Could not start CI tests due to missing safe PR label. Please contact a DEDIS maintainer.
Issues
2 New issues
0 Accepted issues
Measures
0 Security Hotspots
60.3% Coverage on New Code
0.0% Duplication on New Code
Now that we have the notion of Scheme for bdn, I wonder if the masks shouldn't just be embedded in these and just have new exported methods on the Scheme to manage participants and public keys, as well as a method taking an aggregate signature and returning the list of participants or so?
IMO, it's best to keep scheme independent of the participants. But I can make Mask
BDN specific and probably simplify it a bit.
Issues
6 New issues
0 Accepted issues
Measures
0 Security Hotspots
88.4% Coverage on New Code
0.0% Duplication on New Code
@AnomalRoil I've moved Mask into BDN and removed the abstraction. This is significantly cleaner.
@AnomalRoil could you give this a final review? I think Steb has addressed your last outstanding comments
Honestly, no rush; our deadlines aren't your deadlines. Given the interface-based decoupling in kyber, we were able to pretty cleanly vendor just the BDN package so we're not blocked on any of our PRs.
Issues
6 New issues
0 Accepted issues
Measures
0 Security Hotspots
88.4% Coverage on New Code
0.0% Duplication on New Code
Originally filed against drand's fork as https://github.com/drand/kyber/pull/60 and https://github.com/drand/kyber/pull/61.
This set of patches:
I've also added some test fixtures for BDN at @AnomalRoil's request and added a benchmark for the CachedMask.