Skip to content

BC Migration Guide: update Chapter 5 with CA cert gen with pathLen constraint#258

Open
cconlon wants to merge 1 commit intowolfSSL:masterfrom
cconlon:bcMigrationPathLen
Open

BC Migration Guide: update Chapter 5 with CA cert gen with pathLen constraint#258
cconlon wants to merge 1 commit intowolfSSL:masterfrom
cconlon:bcMigrationPathLen

Conversation

@cconlon
Copy link
Member

@cconlon cconlon commented Mar 11, 2026

This PR updates the Bouncy Castle Migration Guide with the addition of instructions for generating CA certificates with the Basic Constraint pathLen constraint set to zero/0.

Goes along with source code changes from wolfSSL/wolfssljni#341 and wolfSSL/wolfssl#9940

Copilot AI review requested due to automatic review settings March 11, 2026 20:23
@cconlon cconlon self-assigned this Mar 11, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates Chapter 5 of the Bouncy Castle Migration Guide to document how to generate CA certificates with a BasicConstraints path length constraint (specifically pathLen=0) when migrating to wolfSSL JNI.

Changes:

  • Adds an in-place note/example for BasicConstraints(0) (CA + pathLen=0) alongside the existing Basic Constraints example.
  • Extends the API comparison table to include the wolfSSL JNI addExtension(..., pathLen, ...) overload for Basic Constraints.
  • Adds a new dedicated section with end-to-end Bouncy Castle vs wolfSSL JNI examples for self-signed CA generation with pathLen=0.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@cconlon cconlon force-pushed the bcMigrationPathLen branch from 5e06f04 to 6b3c1de Compare March 11, 2026 21:45
@cconlon cconlon assigned wolfSSL-Bot and unassigned cconlon Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants