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

docs: add FAQ on why BoringSSL #7331

Closed
mattklein123 opened this issue Jun 20, 2019 · 1 comment · Fixed by #8678
Closed

docs: add FAQ on why BoringSSL #7331

mattklein123 opened this issue Jun 20, 2019 · 1 comment · Fixed by #8678
Assignees
Labels
Milestone

Comments

@mattklein123
Copy link
Member

Let's have an explicit FAQ on why we are using BoringSSL, the support we get from the BoringSSL team, etc.

@mattklein123
Copy link
Member Author

@lizan @PiotrSikora are either of you willing to take a stab at this?

cc @davidben @agl

@mattklein123 mattklein123 added this to the 1.12.0 milestone Jul 3, 2019
@mattklein123 mattklein123 self-assigned this Oct 10, 2019
mattklein123 added a commit that referenced this issue Oct 19, 2019
Fixes #8190
Fixes #7420
Fixes #7331
Fixes #7312
Fixes #7284

Signed-off-by: Matt Klein <mklein@lyft.com>
mattklein123 added a commit that referenced this issue Oct 21, 2019
Fixes #8190
Fixes #7420
Fixes #7331
Fixes #7312
Fixes #7284

Signed-off-by: Matt Klein <mklein@lyft.com>
mattklein123 pushed a commit to envoyproxy/data-plane-api that referenced this issue Oct 21, 2019
Fixes envoyproxy/envoy#8190
Fixes envoyproxy/envoy#7420
Fixes envoyproxy/envoy#7331
Fixes envoyproxy/envoy#7312
Fixes envoyproxy/envoy#7284

Signed-off-by: Matt Klein <mklein@lyft.com>

Mirrored from https://github.com/envoyproxy/envoy @ 8e0b240b0e0abcda07b7b259178bdad60a699019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants