mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #84] installJava fails on Windows #48
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#48
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 @philippbeckmann on GitHub (Oct 26, 2018).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/84
mkcert.exe -installwith set JAVA_HOME fails with following error:ERROR: failed to execute "keytool -importcert": exec: "sudo": executable file not found in %PATH%@adamdecaf commented on GitHub (Oct 27, 2018):
Are you running
mkcert.exeinside Windows Subsystem for Linux (WSL)?@philippbeckmann commented on GitHub (Oct 27, 2018):
@adamdecaf No, i'm using the more common
cmd.exeor Powershell on Windows.@adamdecaf commented on GitHub (Oct 27, 2018):
Are you running the windows binary from the releases page? The windows binary doesn't have code using
sudo.@philippbeckmann commented on GitHub (Oct 27, 2018):
I am using this one: mkcert-v1.1.2-windows-amd64.exe
The
sudois in truststore_java.go@L113@adamdecaf commented on GitHub (Oct 27, 2018):
Oh you're totally right. My bad. Can you try out this PR? https://github.com/FiloSottile/mkcert/pull/85
@philippbeckmann commented on GitHub (Oct 30, 2018):
The
sudois gone, but the destination file<JDK>\lib\security\cacertsis not writeable by a normal user.I had a brief look at this issue and it seems the only way to run a command elevated is by using
ShellExecutewith the verbrunas.Alternativly, a manifest file can be added to require elevation on invoking
mkcert(certainly not desirable, as there are many functions usable without elevation)Option 3 would be to just fail and instruct the user to run
mkcertelevated.@adamdecaf commented on GitHub (Nov 3, 2018):
I recall it being a common pattern to "Run as Administrator" on Windows. If that's still around then that sounds fine.