temporalio / temporalio/temporal
GRPC_SSL_CIPHER_SUITES not respected
Open
Nobody has claimed this yet.
P1
potential-bug
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Expected Behavior
When GRPC_SSL_CIPHER_SUITES environment variable is set, those are the only ciphers the server will use.
Actual Behavior
The default ciphers are still used
Steps to Reproduce the Problem
- Set
GRPC_SSL_CIPHER_SUITES=TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-CHACHA20-POLY1305 - Run
sslscanagainst the gRPC endpoint - Observe results
Specifications
- Version: 1.18.4
- Platform:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Set GRPC_SSL_CIPHER_SUITES to the listed cipher suite values and run sslscan against the gRPC endpoint to reproduce the discrepancy. Compare the advertised ciphers with the configured list; done means the server uses only the suites supplied through the environment variable rather than the defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100