-
Notifications
You must be signed in to change notification settings - Fork 615
[BUG]: TLS profile doesn't support passphrase-protected certificates #2679
Copy link
Copy link
Labels
MUSTP1: Non-negotiable, critical requirements without which the product is non-functional or unsafeP1: Non-negotiable, critical requirements without which the product is non-functional or unsafebugSomething isn't workingSomething isn't workingpythonPython / backend development (FastAPI)Python / backend development (FastAPI)securityImproves securityImproves security
Milestone
Description
Description
When using make compose-tls with a passphrase-protected private key, nginx fails to start because it cannot read encrypted keys natively.
Steps to Reproduce
- Generate a passphrase-protected certificate:
make certs-passphrase
- Run the TLS profile:
make compose-tls
- nginx fails with SSL error - unable to read private key
Expected Behavior
Users should be able to use passphrase-protected certificates by providing the passphrase via environment variable.
Actual Behavior
nginx cannot start because it doesn't support passphrase-protected keys without additional configuration.
Environment
- Docker Compose with TLS profile
- Any passphrase-protected PEM key
Proposed Solution
Enhance cert_init service to:
- Detect
key-encrypted.pemfile - Read passphrase from
KEY_FILE_PASSWORDenv var - Decrypt key to
key.pembefore nginx starts
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
MUSTP1: Non-negotiable, critical requirements without which the product is non-functional or unsafeP1: Non-negotiable, critical requirements without which the product is non-functional or unsafebugSomething isn't workingSomething isn't workingpythonPython / backend development (FastAPI)Python / backend development (FastAPI)securityImproves securityImproves security