-
-
Notifications
You must be signed in to change notification settings - Fork 479
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
[spec] Per-recipient format is unspecified #9
Comments
Yeah, I realized line wrapping should not be defined in encode at all, but in the ssh-rsa definition, since it's the only multiline one. |
As a start, I moved the wrapping part to the ssh-rsa block, which should be a no-op. |
Based on my current understanding of the format, I suggest something like the following:
|
This issue needs to be resolved in order to clear up the definition of what a "recipient line" is, which constraints how implementations ignore unknown recipient types, and how future recipient lines are implemented. |
In str4d/rage#52 I am parsing unknown recipient lines using the above format, with the additional constraints that |
This is now fixed in the spec, I will make available some test cases of valid weird age files with arbitrary recipients or unknown versions.
|
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
The spec currently says:
This is insufficiently-specified, and does not indicate how arguments and additional lines should be parsed. In particular:
The text was updated successfully, but these errors were encountered: