age: tighten STREAM last chunk #13
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, a 64 KiB payload could be encrypted as one or two chunks. All known implementations do the former. Remove the complexity and ambiguity by requiring that.
dconnolly
approved these changes
Jun 29, 2022
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this pull request
Jan 18, 2023
ChangeLog: age v1.1.1 age v1.1.1 is a patch release to fix go install filippo.io/age/...@latest. age v1.1.0 Breaking changes If -i is used, passphrase-encrypted files are now rejected. Previously, a passphrase-encrypted file was auto-detected and the identity file was ignored. This could lead to unexpected behavior, such as a script blocking for user interaction, based on potentially untrusted input files. Now, age -d must be invoked without -i arguments to decrypt passphrase-encrypted files. A helpful error is printed otherwise. This should not break any automated system as passphrase decryption was always interactive. Empty final chunks are now rejected. If a payload was a multiple of 64KiB long, there were two valid encryptions for it: with a "full" last chunk encrypting 64KiB, or with an additional "empty" chunk encrypting 0 bytes. age, rage, and all other known implementations only ever produced the former. (Note that age will forever decrypt files it generated.) The latter is now rejected. The specification has been updated (C2SP/C2SP#13) and test cases are included in the test suite. Minor changes PKCS#8-encoded Ed25519 private keys (such as 1Password exports) are now supported as SSH identities. If an armored file is pasted into the terminal, age will now attempt to wait until the end of the file before prompting for a password. Some invalid files are now correctly rejected, in particular encrypted files with trailing data. (Yay for the test suite!) If /dev/tty is present but can't be opened, age will now fallback to trying to treat stdin as a terminal as if /dev/tty wasn't present. (Thanks @brandsimon!) Input prompts now go to the terminal, even if standard error is redirected. Values of the new armor.Error type are now returned wrapped in decryption errors when appropriate. Windows binary releases are now signed. (Thanks @technion!) Documentation and error messages were improved.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, a 64 KiB payload could be encrypted as one or two chunks.
All known implementations do the former. Remove the complexity and
ambiguity by requiring that.