-
Notifications
You must be signed in to change notification settings - Fork 104
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
v0.9 Breaking Change? #421
Comments
Further info - trying to recreate the file anew with rage v0.9.2 on my system gives me the following head-scratching message:
The underlying call is simply to
|
It looks like this was caused by #349, in which the Now, it was "fine" to make this change in 0.9 because that was a breaking change release (as are all 0.Y releases under Rust SemVer). However, this should have been documented in the 0.9.0 changelog; I will do so. I will also consider adding a flag for overriding the maximum RSA key size (as |
Hmm, looking further at the EDIT: Nope, the way I implemented this in |
Ah, the key size strikes again. I thought I had squashed all of my 8192 keys. This caused me to finish my upgrade to all ED25519 keys and re-encrypt the files. So there is no immediate issue for me. Likely a comment in the release notes is good enough. |
I've updated the changelog in #425 as well as adding a new error to handle this case. I'm not going to add a flag to override the maximum modulus size at this time. |
Environment
What were you trying to do
Read files encrypted with a version of rage < 0.9.0
What happened
The file is read-able with versions of rage up through 0.8.1, but versions after 0.9.0 fail to read the file. In this case the file was originally created with version 0.7.2 of rage through the agenix tool.
The same behavior is witnessed with v0.9.2.
The text was updated successfully, but these errors were encountered: