mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 13:36:02 +03:00
[GH-ISSUE #178] What is the "Password:" for which I'm prompted when I run mkcert -install on a Mac? #114
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#114
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kenny-evitt on GitHub (Jul 19, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/178
From a Terminal window:
I'm pretty sure this is my Keychain password (the 'login' password for my user) but it's certainly not clear that that's what's being requested. Could this (or should) this be documented in the README? (I'd be willing to make a stab at doing so if it's considered helpful.)
@hauleth commented on GitHub (Jul 29, 2019):
Current account password. The same you use when you do
sudo true@rfay commented on GitHub (Jul 29, 2019):
This is a confusing thing that mkcert silently runs sudo. Maybe necessary, but a little more output would be useful, knowing that sudo may go ahead and prompt for password.
@hauleth commented on GitHub (Jul 29, 2019):
Actually, at least in macOS Sierra, it is not needed to use
sudoforsecuritycommand line tool, as this will automatically ask user whether they allow changes and would even allow using TouchID to confirm such changes.@adamdecaf commented on GitHub (Jul 30, 2019):
I created https://github.com/FiloSottile/mkcert/pull/183 which removes
sudowhere we can, but since we add the mkcert root to the System Keychainsudoappears to be required still.@FiloSottile commented on GitHub (Jul 30, 2019):
We should probably always pass
--prompt="Sudo password:"tosudo.@kenny-evitt commented on GitHub (Jul 31, 2019):
@FiloSottile That's a good idea too but a brief mention in the README would nicely set expectations too:
sudorequirement by kenny-evitt · Pull Request #185 · FiloSottile/mkcert@adamdecaf commented on GitHub (Jul 31, 2019):
I like the idea of passing
--promtptosudo.