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.

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

Does Contour support FIPS-allowed encryption? #2878

Closed
javsalgar opened this issue Sep 3, 2020 · 10 comments · Fixed by #3446
Closed

Does Contour support FIPS-allowed encryption? #2878

javsalgar opened this issue Sep 3, 2020 · 10 comments · Fixed by #3446
Assignees
Labels
kind/question Categorizes an issue as a user question.
Milestone

Comments

@javsalgar
Copy link

Please describe the problem you have

Some applications like Elasticsearch have a FIPS mode that forces the application to use FIPS-compliant encryption mechanisms (https://www.elastic.co/guide/en/elasticsearch/reference/current/fips-140-compliance.html). I didn't see here (https://projectcontour.io/guides/tls/) if it is possible to allow something similar to Contour. Looking a bit further it seems that Envoy does allow it (https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fips-140-2), could you confirm if that would be enough or it is necessary to enable anything else on the Contour side.

@jpeach jpeach added the kind/question Categorizes an issue as a user question. label Sep 3, 2020
@jpeach
Copy link
Contributor

jpeach commented Sep 3, 2020

If you bring a FIPS-compliant Envoy image to your deployment, then everything should work fine. The only potential issue that I can think of is whether the cipher suite that Contour configures is allowed in FIPS (I suspect that it should be OK).

@sunjayBhatia
Copy link
Member

See #3347

@youngnick
Copy link
Member

I'm not sure (I'm no FIPS expert), but it looks like in order to be able to have a FIPS-compliant Contour install, you need three things:

To wrap this up, we will probably need a guide in the website guides section for what to do to end up with a FIPS-compliant Contour, and possibly have something in the Operator eventually.

@youngnick youngnick self-assigned this Feb 11, 2021
@sunjayBhatia
Copy link
Member

I can write up a guide to start with, depending on how that works we can assess if we want to provide more resources (scripts, docker images, etc.)

@sunjayBhatia
Copy link
Member

Or @youngnick if you want go for it since you self assigned!

@youngnick youngnick removed their assignment Feb 11, 2021
@youngnick
Copy link
Member

No, I'm happy for you to take this one @sunjayBhatia!

@sunjayBhatia sunjayBhatia self-assigned this Feb 11, 2021
@sunjayBhatia sunjayBhatia added this to the 1.14.0 milestone Feb 23, 2021
@sunjayBhatia
Copy link
Member

Started work on this but will not be done for 1.13 so moving to 1.14

sunjayBhatia added a commit to sunjayBhatia/contour that referenced this issue Feb 24, 2021
This will enable keen users who can build Contour themselves to use a different golang image to support building with FIPS-validated BoringCrypto library.

Updates projectcontour#2878

Signed-off-by: Sunjay Bhatia <[email protected]>
@sunjayBhatia
Copy link
Member

One step: #3406

skriss pushed a commit that referenced this issue Feb 27, 2021
…e images (#3406)

This will enable keen users who can build Contour themselves to use a different golang image to support building with FIPS-validated BoringCrypto library.

Updates #2878

Signed-off-by: Sunjay Bhatia <[email protected]>
@sunjayBhatia
Copy link
Member

See #3446 for a guide on Contour and FIPS, please give feedback if you have it!

@sunjayBhatia
Copy link
Member

See https://projectcontour.io/guides/fips/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Categorizes an issue as a user question.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants