envoyproxy / envoyproxy/envoy-openssl
Roadmap
- Vorherrschende Sprache
- C++
- Sterne
- 57
- Forks
- 46
- Ø Merge
- 16 Std. 56 Min.
- Gemergte PRs (30 T.)
- 14
Beschreibung
Here's a high-level roadmap for the project.
- [x] Make boringssl-based TLS extensions fully unpluggable
* https://github.com/envoyproxy/envoy/pull/7377
- [x] Move TLS extensions into envoy-openssl
* https://github.com/Maistra/envoy-openssl/tree/maistra-0.12
* https://github.com/rojkov/envoy-openssl/tree/openssl-as-3d-party-extension
- [x] Convert the crypto library, etc. to an extension and implement one based on OpenSSL
* envoyproxy/envoy#7344
- [ ] Implement OpenSSL patches for jwt-verify, quiche, etc.
* https://github.com/bdecoste/jwt_verify_lib
* https://github.com/rojkov/envoy-openssl/blob/openssl-as-3d-party-extension/jwt_verify-make-compatible-with-openssl.patch (preferred pattern)
- [ ] Implement a build and test pipeline which is triggered on commits into the main envoy project
* Pull latest Envoy before building
- [ ] Implement tests in the main envoy project to prevent spillage of SSL related code into classes which don't have proper SSL abstractions/extension mechanisms
/cc @envoyproxy/openssl-dev
Feel free to add/edit.
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.