-
Notifications
You must be signed in to change notification settings - Fork 31
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
New release w/o chrono dep #63
Comments
I'm a bit annoyed by the fact that this causes these warnings. yasna does not use the offending API of the chrono crate, but it does/did use the fact that chrono supports leap seconds. Lacking leap second support can introduce actual bugs to programs. So the CVE warning pushes yasna from one solution that has no issues to another solution that does have issues, worsening security not helping with it. Maybe we should just do our time handling ourselves, idk. |
Bump? |
+1 bump on release |
Resolved now. See rustls/rcgen#66 (comment) for why it took so long. |
qnighy/yasna.rs#63 is resolved
qnighy/yasna.rs#63 is resolved
Can we get a new release with #61? I'd really love for my downstream CI to stop yelling at me about the CVE.
The text was updated successfully, but these errors were encountered: