openssl / openssl/openssl

openssl pkcs12 - can someone the "passout" options

Open
#32,307 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted triaged: documentation
Dominant language
C
Stars
30.8k
Forks
11.5k
Avg merge
10m
Merged PRs (30d)
1

Description

For build issues:
Using OpenSSL v3.5.5

$  openssl pkcs12 -export -inkey server/End_Entity_Private_Key.pem -in ./server/End_Entity_Private_Cert.pem -out ./server/Server_Chain.p12 -chain -untrusted ./issuingca/IssuingCA_Cert_G1.pem -CAfile ./rootca/RootCA-G1.pem -passin file:./server/passphrase.txt -passout pass:$(cat ./server/passphrase.txt )

Can I ask someone to confirm an issue I just noticed, essentially I just notice "-passout file:./server/passphrase.txt" does appear to work, as a work around I've used "-passout pass:$(cat ./server/passphrase.txt)".

Note, I haven't tried the many permutation of the above command.

Regards
Nigel

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the supplied openssl pkcs12 -export command, comparing -passout file:./server/passphrase.txt with the working pass:$(cat ...) form. Done means determining whether file-based input is expected to work and recording a minimal reproducible case for the relevant CLI behavior.

Written by the indexing model from the issue text.

Assessment

Domain
cli, cryptography, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.