`dotnet dev-certs` should have the ability to import the generated cert into the machine store

[jackmtpt]

Is your feature request related to a problem? Please describe.

We have several applications that run as windows services which we'd like to be able to use dev-certs with. Typically we'd be debugging a separate application that needs to talk to these services over HTTPS, and we'd like to use the same cert everywhere.

At the monent we can work around this by exporting the cert to a pfx file and importing it into the machine store, but it'd be better if this could be built-in.

Describe the solution you'd like

dotnet dev-certs https --trust --add-to-machine-store or something like that

[MackinnonBuck]

cc @adityamandaleeka

[MackinnonBuck]

@jackmtpt, it sounds like you want to add the certificate into the machine store instead of the user store - is that correct?

[jackmtpt]

Into both would be ideal. Right now we're importing the cert+key into the LocalMachine My store so that services can use it to listen for TLS connections, and we're importing just the cert into the LocalMachine Root store so that everything on the machine trusts it.

We basically have a mix of applications, some of which run as windows services, some are web apps under IIS, some run as console apps or desktop apps and we want everything to Just Work when a developer sets it all up on their machine. Ideally we would just turn off TLS entirely since it's totally pointless for local dev anyway, but we're dependent on some third-party libraries that don't have any ability to do plaintext sockets; they only work over TLS.