Skip to content

Changes to manifest for CIPHER corrected #1

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.

Sign up for GitHub

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

Open
shubhaat wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Changes to manifest for CIPHER corrected #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,9 +24,9 @@ Before running `cf push`
- Include a `ca.crt` file in this directory (CA that signed the expected client certs)

## Specifying Cipher suites while TLS or MTLS is enabled
- When no cipher suite is provided, the [golang default](https://golang.org/pkg/crypto/tls/#pkg-constants) ciphers are loaded.
- When the set of ciphers are specified and shared with the gorouter, the most preferred cipher (first one in the list) is used.
- In `manifest.yml`
```yaml
CIPHER: "ECDHE-RSA-AES128-GCM-SHA256:TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384"
- When `CIPHER` key is not provided in `manifest.yml` the [golang default](https://golang.org/pkg/crypto/tls/#pkg-constants) ciphers are loaded.
- To specify a cipher suite for the app, use `CIPHER` in `manifest.yml`; Gorouter must be configured to support the same cipher suite. Note: only one cipher suite is supported by `CIPHER`. For e.g. in `manifest.yml`
```yaml
CIPHER: "ECDHE-RSA-AES128-GCM-SHA256"
```