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

FIPS compliant version of docker image in docker repository #8107

Closed
sp13-hub opened this issue Aug 30, 2019 · 6 comments
Closed

FIPS compliant version of docker image in docker repository #8107

sp13-hub opened this issue Aug 30, 2019 · 6 comments
Labels
question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently

Comments

@sp13-hub
Copy link

sp13-hub commented Aug 30, 2019

Title: FIPS compliant version of docker image in docker repository

Description:

It looks like images available in envoyproxy repo is boringSSL without fips compliance. Right now if we need it we have to build on our own. Is it possible to provide a fips compliant version of image ?

[optional Relevant Links:]

https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl.html?highlight=fips#fips-140-2

@mattklein123 mattklein123 added the question Questions that are neither investigations, bugs, nor enhancements label Sep 1, 2019
@mattklein123
Copy link
Member

This is a reasonable request but realistically I doubt this will happen any time soon. It might be better to reach out to https://www.getenvoy.io/ and see if they will do it? cc @lizan @dio

@sp13-hub
Copy link
Author

sp13-hub commented Sep 1, 2019

@mattklein123 Thank you. I just checked the issues there, and looks like there has been already one in their queue.
tetratelabs-attic/getenvoy-package#20

@lizan
Copy link
Member

lizan commented Sep 3, 2019

Yeah that's in getenvoy roadmap but I don't have an ETA right now

@sp13-hub
Copy link
Author

sp13-hub commented Sep 4, 2019

@lizan Thank you. Glad it is in your road map. I will follow the other issue.

@stale
Copy link

stale bot commented Oct 4, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Oct 4, 2019
@stale
Copy link

stale bot commented Oct 11, 2019

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

3 participants