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

Security: PEPS is vulnerable to a POODLE attack, as it has SSL v3 enabled #77

Open
tiangolo opened this issue Feb 16, 2017 · 1 comment

Comments

@tiangolo
Copy link
Contributor

Security: PEPS is vulnerable to a POODLE attack, as it has enabled SSL v3

Opening: https://www.ssllabs.com/ssltest/analyze.html?d= + <domain with PEPS> scans the server for security risks.

A simple way to fix this would be to enable simple direct HTTP access and then letting users put a termination TLS proxy (as a HAProxy) instead of implementing TPS in PEPS' code.

It would also be simpler to configure encryption with Let's Encrypt using an additional proxy than trying to update the certificates used by PEPS in its implementation of TLS.

ssllabs-peps

@hbbio
Copy link
Contributor

hbbio commented Mar 10, 2017

Thanks. This is done in the forthcoming version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants