Tony Arcieri
Tony Arcieri
Looks like there are a few imports that need to be changed
@xTachyon it needs a PR with functionality similar to #17 (or perhaps we could upstream the core of that somewhere so it can be reused)
Is there a use case where this would actually make sense? Otherwise it seems like an error condition to me
But in particular I'm asking about miscomputing the size and causing the error case. Why is it being miscomputed? Why is it being passed explicitly instead of inferred?
But more specifically, what is an example of a case where `random_bits_with_precision` is being preferred over `random_bits`, where the caller wants to pass an explicit precision but for some reason...
Shouldn't the answer for those cases be "use `random_bits` instead of `random_bits_with_precision`"?
@mikelodder7 added to the list random < n implemented in RustCrypto/utils#508. Will cut a release with that fairly soon. Re: signed integers, yes that's definitely planned but not on this...
@mikelodder7 what kind of API are you looking for there? Would a `Choice` suffice, or are you looking for a secret-dependent/vartime API?
@mikelodder7 it looks like it might be interesting to adapt the code in `glass_pumpkin` for (safe) prime generation, that is if we could get your blessing to license the resulting...
Absolutely, that'd be the goal. Generic modpow seems a bit tricky, or at least our last attempt at it didn't work. One option would be to have a trait for...