OPS packet: Default to new packet format#2347
Open
vanitasvitae wants to merge 1 commit into
Open
Conversation
Contributor
|
I've uploaded a new jar to https://www.bouncycastle.org/betas - with the patch, I changed it as the original one is on the parser, I suspect just an accident. One thing, it defaults to new for V6, but legacy will still work okay, if you set PacketFormat.CURRENT it should run with the new style for everything though. |
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
2 participants
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.
Hey!
Someone noticed that BC still defaults to the old legacy packet format when emitting OnePassSignaturePackets.
This patch changes the default value to the new packet format.