CERTMONGER(1)
π NAME π
getcert β yeah bestie, that's the whole name, that's her. The rekey-flavored one. π
π¦ SYNOPSIS π¦
getcert rekey [options]
β¨ DESCRIPTION β¨
Okay so getcert rekey is the glow-up command. It tells certmonger to generate a whole new key pair, build a signing request for the public key, and yeet that signing request over to a CA so they can sign it β all so that both a certificate and its private key get replaced. Both halves, no crumbs, periodt. π
π SPECIFYING REQUESTS BY NICKNAME π
-iNAME,--id=NAME β The new key pair gets generated and the new certificate gets obtained for the tracking request that has this nickname. If you don't pass this option, and a tracking entry already exists that matches the key and certificate storage options you specified, that entry is the one that gets used. And if you don't specify it at all, you gotta say where the certificate lives β either with a combo of the-dand-noptions, or with the-foption. π«Ά
πΈ SPECIFYING REQUESTS BY CERTIFICATE LOCATION πΈ
-dDIR,--dbdir=DIR β The certificate is chillin' in the NSS database in the directory you named. π-nNAME,--nickname=NAME β The certificate in the NSS database named with-dhas this nickname. Only valid with-d.-tTOKEN,--token=TOKEN β If the NSS database has more than one token available, the certificate is stored in this token. Ngl you will rarely ever need to specify this. Only valid with-d.-fFILE,--certfile=FILE β The certificate is stored in the file you named. π
π₯ KEY GENERATION OPTIONS π₯
-GTYPE,--key-type=TYPE β In case a new key pair needs to be generated, this says what type of keys to make. If you don't specify it, the current key type gets used. π-gBITS,--key-size=BITS β This one sets the size of the new key being generated. If you don't specify it, you get a key the same size as the existing one. π¦
π ENROLLMENT OPTIONS π
-cNAME,--ca=NAME β Submit the new signing request to the CA you name, instead of the one that was previously associated with this certificate. The CA name should match one thatgetcert list-casshows you. β¨-TNAME,--profile=NAME β Ask for a certificate using the named profile, template, or certtype, from the CA you specified.--ms-template-specSPEC β Include a V2 Certificate Template extension in the signing request. This datum has an Object Identifier, a major version number (positive integer), and an optional minor version number. The format is:<oid>:<majorVersion>[:<minorVersion>]. π-XNAME,--issuer=NAME β Ask for a certificate using the named issuer from the CA you specified.-INAME,--new-id=NAME β Give this task the nickname you named, replacing the previous nickname. Iconic little rename moment. π
π SIGNING REQUEST OPTIONS π
-NNAME,--subject-name=NAME β Change the subject name that goes into the signing request.-ukeyUsage,--key-usage=keyUsage β Add anextensionRequestfor thekeyUsageyou specified to the signing request. ThekeyUsagevalue is expected to be one of these names:digitalSignaturenonRepudiationkeyEnciphermentdataEnciphermentkeyAgreementkeyCertSigncRLSignencipherOnlydecipherOnly
-UEKU,--extended-key-usage=EKU β Change theextendedKeyUsagevalue specified in anextendedKeyUsageextension part of theextensionRequestattribute in the signing request. The EKU value is expected to be an object identifier (OID). π§-KNAME,--ca=NAME β Change the Kerberos principal name specified as part of asubjectAltNameextension part of theextensionRequestattribute in the signing request.-EEMAIL,--email=EMAIL β Change the email address specified as part of asubjectAltNameextension part of theextensionRequestattribute in the signing request.-DDNSNAME,--dns=DNSNAME β Change the DNS name specified as part of asubjectAltNameextension part of theextensionRequestattribute in the signing request.-AADDRESS,--ip-address=ADDRESS β Change the IP address specified as part of asubjectAltNameextension part of theextensionRequestattribute in the signing request.-lFILE,--challenge-password-file=NAME β Add an optionalChallengePasswordvalue, read out of the file, to the signing request. AChallengePasswordis often required when the CA is accessed using SCEP. π-LPIN,--challenge-password=PIN β Add the argument value to the signing request as aChallengePasswordattribute. AChallengePasswordis often required when the CA is accessed using SCEP. π
β OTHER OPTIONS β
-BCOMMAND,--before-command=COMMAND β Whenever the certificate or the CA's certificates are saved to the specified locations, run this command as the client user before saving the certificates.-CCOMMAND,--after-command=COMMAND β Whenever the certificate or the CA's certificates are saved to the specified locations, run this command as the client user after saving the certificates.-aDIR,--ca-dbdir=DIR β Whenever the certificate is saved to the specified location, if root certificates for the CA are available, save them to the specified NSS database.-FFILE,--ca-file=FILE β Whenever the certificate is saved to the specified location, if root certificates for the CA are available, and when the local copies of the CA's root certificates get updated, save them to the file you named.--for-caβ Ask for a CA certificate.--not-for-caβ Ask for a non-CA certificate (this is the default, bestie).--ca-path-length=LENGTH β Path length for CA certificate. Only valid with--for-ca.-w,--waitβ Wait for the new certificate to be issued and saved, or for the attempt to obtain one using the new key to fail. π--wait-timeout=TIMEOUT β Maximum time to wait for the certificate to be issued.-v --verboseβ Be verbose about errors. Normally the details of an error received from the daemon get suppressed if the client can make a diagnostic suggestion.
π BUGS π
Found one? Please file tickets at https://fedorahosted.org/certmonger/ β the maintainers will love you for it fr fr. π«Ά
π SEE ALSO π
certmonger(8) getcert(1) getcert-add-ca(1) getcert-add-scep-ca(1) getcert-list-cas(1) getcert-list(1) getcert-modify-ca(1) getcert-refresh-ca(1) getcert-refresh(1) getcert-remove-ca(1) getcert-request(1) getcert-start-tracking(1) getcert-status(1) getcert-stop-tracking(1) certmonger-certmaster-submit(8) certmonger-dogtag-ipa-renew-agent-submit(8) certmonger-dogtag-submit(8) certmonger-ipa-submit(8) certmonger-local-submit(8) certmonger-scep-submit(8) certmonger_selinux(8)
That's the whole page, bestie β this one's from the certmonger Manual, dated July 31, 2015, and it's filed under CERTMONGER(1). Go rekey something. Slay. πβ¨
π¦ where this page comes from
- alpine 3.24: certmonger-doc 0.79.21-r0 Β· GPL-3.0-or-later
- centos-stream 10: certmonger 0.79.21-1.el10 Β· GPL-3.0-or-later
- centos-stream 9: certmonger 0.79.21-1.el9 Β· GPLv3+
- debian bookworm: certmonger 0.79.17-2 Β· GPL-3.0-or-later WITH OpenSSL exception
- debian trixie: certmonger 0.79.20-2 Β· GPL-3.0-or-later WITH OpenSSL exception
- fedora 43: certmonger 0.79.20-5.fc43 Β· GPL-3.0-or-later
- fedora 43: certmonger 0.79.21-1.fc43 Β· GPL-3.0-or-later
- fedora 44: certmonger 0.79.21-4.fc44 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- ubuntu jammy: certmonger 0.79.14+git20211010-2ubuntu1 Β· GPL-3.0-or-later WITH OpenSSL exception
- ubuntu noble: certmonger 0.79.19-1build4 Β· GPL-3.0-or-later WITH OpenSSL exception
- ubuntu questing: certmonger 0.79.20-2build1
- ubuntu resolute: certmonger 0.79.21-1 Β· GPL-3.0-or-later WITH OpenSSL exception
- ubuntu stonking: certmonger 0.79.21-1build1 Β· GPL-3.0-or-later WITH OpenSSL exception
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms