Mariano Cano

That is basically how I finally did it. It would be nice to have that in the README.md, and perhaps a command to do 2.

@cretz @FiloSottile I also have a use case in a project that I'm working on, so I went ahead and created a package with the install/uninstall functionality. Here it is...

@noglitchyo you might want to look into [smallstep/certificates](https://github.com/smallstep/certificates). You can use [smallstep/cli](https://github.com/smallstep/cli) to create a CSR and a JWT token, those will get validated by the CA and you'll get...

@noglitchyo I forgot that you can `bootstrap` your environment so you don't need to provide the root certificate or the ca url using `step ca bootstrap`

@cespare take a look to https://github.com/smallstep/truststore, it implements mkcert install logic but you can use it in your code.

> @Hardcorian certificate flexibility (#300) should drop soon and you should be able to use that to add CDP to your ACME certs. I'm not 100% certain whether templates are...

@dopey yes, this will be fixed once we switch to https://github.com/smallstep/logging

As I said before this will be addressed by replacing the logger with https://github.com/smallstep/logging, but we haven't prioritized this, I will tag this issue so it appears in our next...

Hi @lindenaar, @hslatman, There seems to be a bug in `go.step.sm/crypto` in how those extra subject fields are parsed, we should get them from `pkix.Name` `Names` instead of `ExtraNames` as...

@hslatman with https://github.com/smallstep/crypto/pull/42 @lindenaar should be able to extract non-default subject attributes from ExtraNames, and populate them directly to the subject using templates.