Skip to content

export-p12: Move inline file to 'inline/private' folder #1356

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

Merged
merged 6 commits into from
Jun 24, 2025

Conversation

TinCanTech
Copy link
Collaborator

No description provided.

Includes, export-p12: Rename inline file extension to '.inline-p12'

Signed-off-by: Richard T Bonhomme <[email protected]>
Includes, export-p12: Rename inline file extension to '.inline-p12'

Signed-off-by: Richard T Bonhomme <[email protected]>
@TinCanTech TinCanTech force-pushed the inline-private-pkcs12 branch from ce943f4 to 01eb0b8 Compare June 23, 2025 16:49
@TinCanTech TinCanTech added this to the v3.2.4 (or v3.3.0) milestone Jun 23, 2025
@TinCanTech TinCanTech modified the milestone: v3.2.4 Jun 23, 2025
Replace $p12_cipher_opts with p12_keypbe p12_certpbe p12_macalg

Signed-off-by: Richard T Bonhomme <[email protected]>
@TinCanTech TinCanTech merged commit ee6f0c4 into OpenVPN:master Jun 24, 2025
3 checks passed
@TinCanTech TinCanTech linked an issue Jun 24, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Split $p12_cipher_opts into respective parts Inline PKCS files with private keys should be written to inline/private folder
1 participant