-
Notifications
You must be signed in to change notification settings - Fork 40
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
Ability to specify file path for saving the root certificate files #9
Comments
Yes, writing to program folder is definetly not a best practice on Windows. And in most cases this behaviour is just fine.
It is certainly possible (and even easy), May be we could first try to save to the folder inside Will it suit you? |
Thanks for the quick response. Yes I like the fact that the tool is simple to use as all you need is “require” it. Putting them in a fall back location would definitely works for me. |
Well, try npm i win-ca@beta |
I think I can get it working for my case - it took longer then expected but I am on top of it. Thanks for the change! |
I just tested on my machine and on the client machines and both work like a charm! |
Great! I plan to release new version tomorrow. |
|
My user case:
My NodeJS scripts and node_modules folder is deployed to "Program Files\MyApp" folder and ran as a window service. When the tool tries to write the root certificate to the node_modules it fails as it has no write permission to do so.
According to the windows guidelines, applications shall not require write permissions to their folder. It will be better if the application writing data to a user profile folder (C:\Users\username\AppData) or to a common data folder (C:\ProgramData).
I wonder if it is OK to add the ability for specifying the path for the root certificates so we can put them somewhere else.
Thanks for making this amazing tool!
The text was updated successfully, but these errors were encountered: