-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add option to generate a shared certificate + auto install it #14
Comments
After thinking about it, I don't think there's any usecase where you might prefer a project scoped certificate compared to a shared certificate 🤔... I mean, the only downside I see is that the certificate may remain somewhere in your system even after you delete all your js projects. So I think it might be better to just create a shared certificate anyway. |
sometimes you want to create a local certificate for a custom test domain, not localhost (some features in some browsers only work with the "green ssl lock" and you can't always get that for localhost) Either way you should ensure that The goal of all this is that it is impossible to use this devtool to compromise the developer by getting access to a trusted ca and presenting them with a fake site that looks legit. |
For a single shared cert on the system, you would have to find a good location, os wide application cache dir for example. |
So after talking a bit with @userquin, I suggest adding two features:
The first time the plugin is launched in a project, as the user where he wants to generate the certificate:
If the user chooses the shared certificate, ask him if he wants to install it
I can work on this feature.
The text was updated successfully, but these errors were encountered: