Support multiple age recipients - #115
Merged
Merged
Conversation
besendorf
marked this pull request as ready for review
July 27, 2026 13:09
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Allow
key.txtto contain multiple age recipients, one per line, so every listed recipient can decrypt the resulting acquisition archive.The recipient file now follows age’s standard recipient-file syntax, including support for blank lines and comments beginning with
#. The encryption stream is created for all parsed recipients, and the user documentation describes the supported format.Previously, androidqf parsed the entire file as a single X25519 recipient, so adding a second recipient made the key file invalid.
Closes #30