This is really just a tutorial on importing a client certificate into chromium via the shared nss database. The real magic is knowing chromium reads a sqlite database under ~/.pki/nssdb for it’s key and certificate storage. pk12util can be installed via the nss-tools package on Fedora or the libnss3-tools package on Debian/*buntu.
$ pk12util -d sql:$HOME/.pki/nssdb -i ~/STARTCOM.p12 Enter password for PKCS12 file: pk12util: PKCS12 IMPORT SUCCESSFUL
Could someone who has a windows installation clue me in via a comment on the best way to do this? Also, could anyone test this on google chrome?
After installing that certificate, startssl login works
Brought to you by the “I’d rather google and see how someone else did it rather than figure it out department”
Wrench Menu -> Preferences -> Under the Hood -> HTTPS/SSL -> Manage Certificates -> Import?
To be fair, it used to just open a page with nssdb instructions.
On Windows, Chrome uses the Windows
'My'certificate store, so just double-click a .p12 file, or use certmgr.exe (with/s myas destination).Thanks for the heads up on both.
@Peter: *facepalm*, the startcom website said that chrome didn’t support it. I’ll have to let them know that is woefully inaccurate.