There’s a command-line tool called certutil one can use to add (among other things) certificates to the certificate store in windows.
REM Add pfx-file to Personal
certutil -ent -p pfxpassword -importpfx my some.pfx
REM Add pfx-file to Trusted Root Certification Authorities
certutil -ent -p pfxpassword -importpfx root some.pfx
REM Add cer-file to Trusted Root Certification Authorities
certutil -ent -addstore root some.cer
- Win + r
Logged into a windows share via explorer and hit the Remember Password option. Even though the login was accepted (and saved) it turned out I had used the wrong ad domain name…
Couldn’t find where to reset/change/”logout” again, but eventually found there’s a built-in command-line tool one can use for managing these saved passwords. Think I’ve seen a control panel type thing to do this too in the past, but just couldn’t find it today… Anyways, command-line is nice, so, using imaginary share \\foobar.int, here’s some stuff one can do:
> cmdkey /list
> cmdkey /list:foobar.int
> cmdkey /delete:foobar.int
> cmdkey /add:foobar.int /user:domain\username /pass
Trying to set up Apache on a server, something is hogging port 80, but very “helpfully” the Resource Monitor just reports “System” with PID 4…
However, some commands found in a StackOverflow answer and its comments were helpful:
netsh http show urlacl
netsh http show servicestate
net stop http
Note: Do not just run these commands blindly and turn off services (in particular you should probably answer N when the last one asks…), but use them to identify what service(s) might be to blame. Then do an intelligent decision on whether the service is needed or not, before you potentially stop it and disable it…
Couldn’t get this to work, but now it does, so… time for another “note to self”. 🙂
- Git, obviously…
- PuTTY, with puttygen, plink and pageant, to be exact…
Either Load an existing private key, or Generate a new one.
Copy the public key (“Public key for pasting …”) and add it to the git provider settings:
Load your private key.
Check that the key authentication works with plink:
plink -v firstname.lastname@example.org
plink -v email@example.com
plink -v firstname.lastname@example.org
Set the GIT_SSH environment variable to C:\Program Files\PuTTY\plink.exe.
^^ This is the detail that so many StackOverflow answers and blog/forum posts didn’t mention. Without this, plink worked fine, but git commands still failed with authentication errors.
(optional) Add a shortcut to the private key file to your startup folder. This way pageant will be automatically started, with your key, ready to go, whenever Windows boots up.
Now, as long as pageant is running with your private key loaded, it should work to clone, pull, push, etc., both to and from, both private and public git repositories. E.g. like this:
git clone email@example.com:example/some-private-repo.git
Note: If you’re asked to accept/store/cache a key, but pressing y doesn’t work, connect using putty first, which should give you a dialog with the same question which does work. Putty will complain/crash because there’s not actually an ssh shell to connect to, but that’s fine. After the key has been saved by putty, git should work fine. E.g. like this:
putty -ssh firstname.lastname@example.org
Sources: makandracards.com, vladmihalcea.com