fix(v3): skip padding check in DES decryption - #30
Open
jason-cts wants to merge 1 commit into
Open
Conversation
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.
Hi, I have fix (or workaround?) an issue about cyrpto-rust feature,
it happens on Cisco SG300 switch, which is only supports DES priv mode.
this switch is padding with 0, not PKCS-like scheme.
after I take a look at RFC3414, in 8.1.1.2, it mentioned "The actual pad value is irrelevant."
so I remove whole PKCS padding stub in
fn decrypt_des()below is the screenshot of Wireshark, I have censored something might sensitive.
