Skip to content

Conversation

@Spomky
Copy link
Contributor

@Spomky Spomky commented Feb 16, 2025

Target branch: 5.1.x
Resolves issue #681

  • It is a Bug fix
  • It is a New feature
  • Breaks BC
  • Includes Deprecations

Updated trust path serialization and deserialization in tests, fixed parameter usage in TrustPathDenormalize.

@Spomky Spomky added the bug Something isn't working label Feb 16, 2025
@Spomky Spomky added this to the 5.1.2 milestone Feb 16, 2025
@Spomky Spomky self-assigned this Feb 16, 2025
@Spomky Spomky force-pushed the bugs/trustpath-serialization branch from 2c665d1 to df2b041 Compare February 16, 2025 09:56
Ensure the 'x5c' key contains an array before creating a CertificateTrustPath. This prevents potential errors caused by invalid 'x5c' data structures during denormalization.
@Spomky Spomky force-pushed the bugs/trustpath-serialization branch from df2b041 to f086af7 Compare February 16, 2025 09:59
@Spomky Spomky merged commit 9d46f22 into 5.1.x Feb 16, 2025
15 checks passed
@Spomky Spomky deleted the bugs/trustpath-serialization branch February 16, 2025 10:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Serialization of trust path results in extra nested trust path on every serialize

2 participants