-
Notifications
You must be signed in to change notification settings - Fork 135
Upgrade all crates to the 2024 edition and bump MSRV to 1.85 #913
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
436380a
to
e6cdcfb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opinion about RandomizedSignerMut
signature?
@@ -107,7 +107,7 @@ impl<Mode: LmsOtsMode> RandomizedSignerMut<Signature<Mode>> for SigningKey<Mode> | |||
|
|||
// Generate the message randomizer C | |||
let mut c = <Output<Mode::Hasher>>::default(); | |||
rng.fill_bytes(&mut c); | |||
rng.try_fill_bytes(&mut c).map_err(|_| Error::new())?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We kind of eat the error here. This might be a bad idea.
I wish we could do Error::from_source instead, but that would require the RandomizedSignerMut to change its signature to something like:
fn try_sign_with_rng<E: core:error::Error, R: TryCryptoRng<Error = E>>(
&mut self,
rng: &mut R,
msg: &[u8],
) -> Result<Signature<Mode>, Error> {
``
Not sure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can potentially consider something like that
prehash: &[u8], | ||
) -> Result<Signature<C>> { | ||
let z = bits2field::<C>(prehash)?; | ||
let mut ad = FieldBytes::<C>::default(); | ||
rng.fill_bytes(&mut ad); | ||
rng.try_fill_bytes(&mut ad).map_err(|_| Error::new())?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
similar situation here.
2e419ca
to
733b105
Compare
@baloo can you rebase? |
309e627
to
9d6fe57
Compare
9d6fe57
to
9a7625f
Compare
9a7625f
to
6ad65c7
Compare
Would it be possible to include new Currently,
I might be mistaken, but all I think needs to happen is:
If this is not the right place and/or time, I'm happy to create a separate issue for it :) |
@erik-3milabs we generally do releases in separate PRs to keep ones like this focused |
Just to mitigate expectations, I don't know if we'll be able to release elliptic-curve until the situation of |
In that case, would there be a point in raising an issue for this? |
Sure, please open a separate issue |
Anything else needed here? |
This currently excludes:
This depends on:
Sized
requirements on Rng traits#1767rand_core
from0.6.4
to0.9.0
crypto-bigint#762