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

Please make certificate password changable, this is a sequrity threat. #164

Open
OlegJakushkin opened this issue Nov 19, 2020 · 5 comments

Comments

@OlegJakushkin
Copy link

Issue:
Stuff like X509Certificate2(data, nameof(FluffySpoon)); with constant passwords makes the system quite vulnerable.

Solution:
A. Keep nameof(FluffySpoon) as sane default, yet allow the user to set his own password
B. Make it random\GUID based so that it would change on each automatic update.

@ffMathy
Copy link
Owner

ffMathy commented Nov 19, 2020

Vulnerable to what exactly? Can you elaborate?

@OlegJakushkin
Copy link
Author

OlegJakushkin commented Nov 19, 2020 via email

@ffMathy
Copy link
Owner

ffMathy commented Nov 20, 2020

The only vulnerability would be to intercept HTTPS traffic and decrypt it, right? That's all I want to know, or if you see other attack vectors too.

That defeats the prime purpose of a certificate indeed, unless you don't really care about the privacy element of HTTPS and just want it for HTTP/2 performance or SEO/usability purposes.

Either way, I agree it should be specified clearly in the documentation, and there should be a way to get around it.

I'll probably also make it throw a warning.

Right now I don't have a lot of time though, but PRs are welcome 😊🙏

@OlegJakushkin
Copy link
Author

OlegJakushkin commented Nov 20, 2020

Yep - main attack vector would be to intercept HTTPS traffic and decrypt it on provider or router side (free wifi access points). That is important when: you transfer money, use OpenID to login, furthermore OpenID and banking systems require you to use SSL exactly for "safe" traffic encryption.

@ffMathy
Copy link
Owner

ffMathy commented May 29, 2021

@OlegJakushkin very good point. Unfortunately, I do not have time to fix it at the moment. PRs are very welcome!

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