Skip to content
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

Jump to bottom

Helm Deployment: Default nginx ciphers are too restrictive #4503

Closed
nwmac opened this issue Aug 12, 2020 · 0 comments · Fixed by #4507
Closed

Helm Deployment: Default nginx ciphers are too restrictive #4503

nwmac opened this issue Aug 12, 2020 · 0 comments · Fixed by #4507
Assignees
@nwmac
Labels
bug P1 Priority 1
Milestone
4.0.1

Comments

@nwmac
Copy link
Contributor

nwmac commented Aug 12, 2020

Insecure ciphers were removed, need to check if there are use cases where these are needed.
@nwmac nwmac added the P1 Priority 1 label Aug 12, 2020
@nwmac nwmac self-assigned this Aug 12, 2020
@nwmac nwmac changed the title Revisit ciphers supported by nginx Helm Deployment: Default nginx ciphers are too restrictive Aug 18, 2020
@nwmac nwmac added this to the 4.0.1 milestone Aug 18, 2020
@nwmac nwmac added the bug label Aug 18, 2020
@nwmac nwmac mentioned this issue Aug 18, 2020
Merged
@nwmac nwmac closed this as completed Aug 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nwmac nwmac

Labels
bug P1 Priority 1
Projects
None yet
Milestone
4.0.1
Development

Successfully merging a pull request may close this issue.

Change nginx ciphers and make configurable via helm chart values cloudfoundry/stratos
1 participant
@nwmac