fix: always try CLI fallback after native PFX import failure#10
Merged
vitormattos merged 1 commit intomainfrom Mar 22, 2026
Merged
fix: always try CLI fallback after native PFX import failure#10vitormattos merged 1 commit intomainfrom
vitormattos merged 1 commit intomainfrom
Conversation
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
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
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
Why
The same legacy PFX can surface different native OpenSSL errors depending on context, including digital envelope unsupported and nested ASN.1 errors.
Restricting the fallback trigger to a single error string still allowed emission failures in the web flow.
Validation