[GH-ISSUE #501] mkcert -version does not output actual version number #305

Open
opened 2026-02-25 22:33:04 +03:00 by kerem · 1 comment
Owner

Originally created by @venteto on GitHub (Feb 2, 2023).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/501

Environment

  • Operating system (including version): Manjaro Linux 22.0.1 Sikaris
  • mkcert version (from mkcert -version): devel

What went wrong

When I view the info about the mkcert package in Manjaro's GUI package manager, it displays the version, but the command line flag only outputs "devel" (see screenshots):

Screenshot from 2023-02-02 10-16-15

Screenshot from 2023-02-02 10-15-31

Originally created by @venteto on GitHub (Feb 2, 2023). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/501 ## Environment * Operating system (including version): Manjaro Linux 22.0.1 Sikaris * mkcert version (from `mkcert -version`): devel ## What went wrong When I view the info about the mkcert package in Manjaro's GUI package manager, it displays the version, but the command line flag only outputs "devel" (see screenshots): ![Screenshot from 2023-02-02 10-16-15](https://user-images.githubusercontent.com/7062385/216364340-2112a51d-fb83-42e7-be91-f6a330e50134.png) ![Screenshot from 2023-02-02 10-15-31](https://user-images.githubusercontent.com/7062385/216364343-79f7ae2b-099b-4eed-b8ac-f3974f26d1b0.png)
Author
Owner

@gitressa commented on GitHub (May 16, 2023):

Also, perhaps -version could get added to the list of options?

$ mkcert -help
Usage of mkcert:

	$ mkcert -install
	Install the local CA in the system trust store.

	$ mkcert example.org
	Generate "example.org.pem" and "example.org-key.pem".

	$ mkcert example.com myapp.dev localhost 127.0.0.1 ::1
	Generate "example.com+4.pem" and "example.com+4-key.pem".

	$ mkcert "*.example.it"
	Generate "_wildcard.example.it.pem" and "_wildcard.example.it-key.pem".

	$ mkcert -uninstall
	Uninstall the local CA (but do not delete it).

Advanced options:

	-cert-file FILE, -key-file FILE, -p12-file FILE
	    Customize the output paths.

	-client
	    Generate a certificate for client authentication.

	-ecdsa
	    Generate a certificate with an ECDSA key.

	-pkcs12
	    Generate a ".p12" PKCS #12 file, also know as a ".pfx" file,
	    containing certificate and key for legacy applications.

	-csr CSR
	    Generate a certificate based on the supplied CSR. Conflicts with
	    all other flags and arguments except -install and -cert-file.

	-CAROOT
	    Print the CA certificate and key storage location.

	$CAROOT (environment variable)
	    Set the CA certificate and key storage location. (This allows
	    maintaining multiple local CAs in parallel.)

	$TRUST_STORES (environment variable)
	    A comma-separated list of trust stores to install the local
	    root CA into. Options are: "system", "java" and "nss" (includes
	    Firefox). Autodetected by default.
<!-- gh-comment-id:1550175509 --> @gitressa commented on GitHub (May 16, 2023): Also, perhaps `-version` could get added to the list of options? ``` $ mkcert -help Usage of mkcert: $ mkcert -install Install the local CA in the system trust store. $ mkcert example.org Generate "example.org.pem" and "example.org-key.pem". $ mkcert example.com myapp.dev localhost 127.0.0.1 ::1 Generate "example.com+4.pem" and "example.com+4-key.pem". $ mkcert "*.example.it" Generate "_wildcard.example.it.pem" and "_wildcard.example.it-key.pem". $ mkcert -uninstall Uninstall the local CA (but do not delete it). Advanced options: -cert-file FILE, -key-file FILE, -p12-file FILE Customize the output paths. -client Generate a certificate for client authentication. -ecdsa Generate a certificate with an ECDSA key. -pkcs12 Generate a ".p12" PKCS #12 file, also know as a ".pfx" file, containing certificate and key for legacy applications. -csr CSR Generate a certificate based on the supplied CSR. Conflicts with all other flags and arguments except -install and -cert-file. -CAROOT Print the CA certificate and key storage location. $CAROOT (environment variable) Set the CA certificate and key storage location. (This allows maintaining multiple local CAs in parallel.) $TRUST_STORES (environment variable) A comma-separated list of trust stores to install the local root CA into. Options are: "system", "java" and "nss" (includes Firefox). Autodetected by default. ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mkcert#305
No description provided.