Randy Fay

@FiloSottile what a day you had today, congratulations and thanks. I wanted to mention that for my job's "upstream contribution goal" I said that I'd try to take on pushing...

@FiloSottile I'd love your direction on tests, and would be pleased to contribute with a set of tests. I do think it needs your blessing and a tiny bit of...

Unfortunately, on ChromeOS the browser is not part of the linux system, so the CA created in Linux is not recognized by the Chrome browser (or even known, or even...

Thanks, I haven't found a solution yet, but poking around on the web: * The old solution (may still work) seems to be to add to git-for-windows' store: https://blogs.msdn.microsoft.com/phkelley/2014/01/20/adding-a-corporate-or-self-signed-certificate-authority-to-git-exes-store/ *...

It looks to me like ``` $ cat $(mkcert -CAROOT)/rootCA.pem >> /mingw64/ssl/certs/ca-bundle.crt ``` does the job from within git-bash context. Outside git-bash context, I believe the directory is typically `C:\Program...

@jkugler - download the windows binary from the releases page, https://github.com/FiloSottile/mkcert/releases

mkcert and Let's Encrypt are completely unrelated. Let's Encrypt provides real trusted certs. It can only be used on an internet-connected machine. mkcert creates certs for testing locally, for development...

Remember that your Virtualbox VM is a "different system" than your host. So your host's browser is not going to trust a cert that you generate inside the Virtualbox VM....

Google was broken for a bit it appears. Please try again @Brolly0204

Just for a different opinion... I'm a big fan of the version number being in the file in releases. It's very easy to script the latest release and create the...