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…
- Open puttygen.
- Load your private key, or generate a new one and save it.
- Copy your public key (“Public key for pasting …”) to BitBucket/GitHub/etc.
- Open pageant
- Load your private key.
- Check that the key authentication works by running e.g.
plink -v firstname.lastname@example.org
plink -v email@example.com
- Point the GIT_SSH environment variable to plink.exe.
Now, as long as pageant is running with your private key loaded, it should work to clone, pull, push, etc. to/from both private and public repos. E.g.
git clone firstname.lastname@example.org:example/some-private-repo.git.
Key here, for me, was the GIT_SSH variable that so many blogs, StackOverflow answers and forum posts failed to mention… Without that set, the plink check did still work, but git clone did not. It just failed with an authentication error. With that variable set it now works perfectly. 🙄🙂👍
Sources: makandracards.com, vladmihalcea.com