You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think in some cases it could be useful if mkcert had a flag that would create the Certificate Authority files without trying add it to the system store.
My use case
I have a makefile that creates a CA, generates certificates based on this freshly created CA and then proceeds to build and deploy a microservices application through docker-compose.
I'm calling mkcert -install from a Makefile in a machine where I do not have root privileges.
When mkcert -install is called, the system prompts for sudo password. If one presses CTRL + C to send a SIGINT, make captures the signal and does not build the application. Instead, the user has to fail the password check three times so that the build process can continue.
It would be better is, provided user passes a convenient flag to mkcert, it creates the CA in the usual user directory but does not try to install this CA to the system store.
Below, a sample of the makefile that it illustrates the point.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I think in some cases it could be useful if mkcert had a flag that would create the Certificate Authority files without trying add it to the system store.
My use case
I have a makefile that creates a CA, generates certificates based on this freshly created CA and then proceeds to build and deploy a microservices application through docker-compose.
I'm calling
mkcert -install
from a Makefile in a machine where I do not have root privileges.When
mkcert -install
is called, the system prompts for sudo password. If one pressesCTRL + C
to send aSIGINT
,make
captures the signal and does not build the application. Instead, the user has to fail the password check three times so that the build process can continue.It would be better is, provided user passes a convenient flag to mkcert, it creates the CA in the usual user directory but does not try to install this CA to the system store.
Below, a sample of the makefile that it illustrates the point.
Beta Was this translation helpful? Give feedback.
All reactions