Skip to content

Refactor PemPrivateKeyParser to use DerElement #39162

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

Closed
wants to merge 1 commit into from

Conversation

Wzy19930507
Copy link
Contributor

If oid resolution algorithms failed, back to brute force.

Closes #37426

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jan 17, 2024
@wilkinsona wilkinsona changed the title Reactor PemPrivateKeyParser to use DerElement Refactor PemPrivateKeyParser to use DerElement Jan 17, 2024
@philwebb philwebb changed the title Refactor PemPrivateKeyParser to use DerElement Refactor PemPrivateKeyParser to use DerElement Jan 17, 2024
@philwebb philwebb self-assigned this Jan 17, 2024
@philwebb philwebb added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Jan 17, 2024
@philwebb philwebb modified the milestones: 3.1.x, 3.1.8 Jan 17, 2024
philwebb pushed a commit that referenced this pull request Jan 17, 2024
Update `PemPrivateKeyParser` so that the algorithm is read using
DerElement whenever possible.

See gh-39162
@philwebb philwebb closed this in 8147b7a Jan 17, 2024
@philwebb
Copy link
Member

Thanks very much @Wzy19930507!

@Wzy19930507 Wzy19930507 deleted the GH-37426 branch January 18, 2024 01:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refactor PemPrivateKeyParser to use DerElement
3 participants