fix(deps): update module filippo.io/age to v1.2.0 #8
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.
This PR contains the following updates:
v1.0.0
->v1.2.0
Release Notes
FiloSottile/age (filippo.io/age)
v1.2.0
: age v1.2.0Compare Source
A small release to build the release binaries with a more recent Go toolchain, and to fix a couple CLI edge cases (https://github.com/FiloSottile/age/issues/491, https://github.com/FiloSottile/age/issues/555).
The Go module now exposes a plugin package that provides an age plugin client. That is, Recipient and Identity implementations that invoke a plugin binary, allowing the use of age plugins in Go programs.
Finally, Recipients can now return a set of "labels" by implementing RecipientWithLabels. This allows replicating the special behavior of the scrypt Recipient in third-party Recipients, or applying policy useful for authenticated or post-quantum Recipients.
v1.1.1
: age v1.1.1Compare Source
age v1.1.1 is a patch release to fix
go install filippo.io/age/...@​latest
.See the release notes for v1.1.0 for changes since v1.0.0.
v1.1.0
: age v1.1.0: plugin and YubiKeys supportCompare Source
age is a simple, modern and secure file encryption tool, format, and Go library. It features small explicit keys, no config options, and UNIX-style composability. Learn more by reading the README, the age(1) man page, the Go API reference, the format specification, or the full release changelog. Watch the repository or follow @[email protected] to be notified of new releases.
🛠️ FYI, age now has an extensive test suite which all age implementations are encouraged to adopt.
Plugin support
The age CLI now supports plugins, such as age-plugin-yubikey by @str4d. To try it on macOS with Homebrew:
Plugins must be loaded explicitly by using their respective recipient or identity, and are not tied to a specific header stanza type. This means plugins can be used not only to support new recipient types such as PIV tokens (i.e. YubiKeys) or cloud KMS solutions, but also to produce passphrase-encrypted files that can be decrypted without plugins, to store age native private keys on secure elements, or even for agent functionality or to proxy decryption operations to remote machines.
Plugins operate over a simple textual stdin/stdout protocol (https://github.com/C2SP/C2SP/pull/5). Developers are encouraged to reach out with plugin ideas and announcements. Read more in the relevant man page section.
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 (https://github.com/C2SP/C2SP/pull/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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.