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

Prompts for password in windows and what to type there? #40

Open
SanjivG10 opened this issue Oct 11, 2019 · 5 comments
Open

Prompts for password in windows and what to type there? #40

SanjivG10 opened this issue Oct 11, 2019 · 5 comments

Comments

@SanjivG10
Copy link

every time I started the devcert, it is always asking me to enter the password, and I don't know.. ANything you type there, it asks again. There is no real docs on what to type on or anything. Any help? If any previous password is stored, which I must have forgot, any way to reset it?

@Js-Brecht
Copy link
Contributor

@SanjivG10 The password that it is asking for is the one used when the CA was originally configured. It is used to encrypt/decrypt the CA key so that it can't be used by anybody/anything to sign certificates (which would be a security risk, considering that the CA is trusted by your computer). It should only ask you for it when the CA is installed, and when it needs to make a certificate for a domain that hasn't had one created yet.

If you need to reset it, you should first remove the trust for the certificate from your computer. You can remove it from your Windows trust store using powershell:

# Say yes to the prompt when it asks you if you want to delete
Get-ChildItem cert:\CurrentUser\Root |?{ $_.Subject -like '*devcert*' } |Remove-Item

If you have Firefox installed, you will need to remove it from there manually. Go to the menu in the top right -> options -> Privacy & Security. All the way at the bottom is "View Certificates...". Open that, go to the Authorities tab, and find "devcert" in the list. Click "Delete or Distrust".

Another way to remove it from the Firefox list is to delete its nssdb, but that will also delete any other custom certificate trusts you've added.

Then, the final step (fairly broad stroke method, but it works) is to delete the devcert AppData directory. Again, probably easiest in Powershell:

Remove-Item -Force -Recurse "$ENV:LOCALAPPDATA\devcert"

Then you should be able to run devcert again, and put in whatever password you want. It will create the certificate authority again, install the trust for the new CA, then create the domain certificate you requested.

@Js-Brecht
Copy link
Contributor

Js-Brecht commented Oct 16, 2019

Just remember that new password is the one you need to use from then on.

Also good to remember is that any domain certificates created with the old CA will no longer be trusted, if you happened to move any of them out of the "$ENV:LOCALAPPDATA\devcert" directory. Just delete them and have devcert recreate them.

@LucasZNK
Copy link

Thanks @Js-Brecht !! Working again!

@talha-itsol-2020
Copy link

It worked for me too.

@dmwyatt
Copy link

dmwyatt commented Jan 17, 2023

# Say yes to the prompt when it asks you if you want to delete
Get-ChildItem cert:\CurrentUser\Root |?{ $_.Subject -like '*devcert*' } |Remove-Item

This wouldn't work for me, I'd always get this error:

Remove-Item: The operation is on user root store and UI is not allowed.

I ended up using the steps I googled up here but instead of selecting Computer account I selected My user account.

alias-mac pushed a commit to alias-mac/devcert that referenced this issue Feb 8, 2024
Bumps [@types/debug](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/debug) from 0.0.30 to 4.1.5.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/debug)

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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

5 participants