COROSYNC-QNETD-CERTUTIL(8)
π COROSYNC-QNETD-CERTUTIL π
okay bestie, welcome to corosync-qnetd-certutil, straight out of the System Manager's Manual (section 8, the big-girl system administration section, we love her). She's the tool that makes your QNetd TLS certificates happen, and honestly? she's carrying the whole 'net' model on her back. π
β¨ NAME β¨
corosync-qnetd-certutil β the tool that generates qnetd TLS certificates π
π¦ SYNOPSIS π¦
corosync-qnetd-certutil [-i|-s] [-c certificate] [-n cluster_name]
πΈ DESCRIPTION πΈ
So corosync-qnetd-certutil is basically a frontend for the NSS certutil β like, she's the cute face, certutil is the muscle behind the curtain. π«Ά
She's here to generate the QNetd CA (that's Certificate Authority, iykyk), the server certificate, and to sign the cluster certificate that corosync-qdevice uses when it's running the model 'net'. No cap, that's her whole job and she does it flawlessly. β¨
π OPTIONS π
-iβ Initialize the QNetd NSS certificate database and generate the QNetd CA and server certificates. The default directory for the database is/etc/corosync/qnetd, and heads up: this directory must be writeable by the current user. The QNetd CA certificate also gets exported into the file/etc/corosync/qnetd/nssdb/qnetd-cacert.crt. π-sβ Sign the cluster certificate. You absolutely need to pass the cluster name (as configured incorosync.conf) and the certificate request file β see the options below, bestie, don't skip them. The signed certificate gets written to the file/etc/corosync/qnetd/nssdb/cluster-$ClusterName.crt. π-cβ Certificate request file to sign. That's it, that's the vibe. π-Gβ Do not set the group write bit for new files. This one only does anything when you use it together with the-ioption, periodt. It's useful when you need that extended security and it's actually viable to prohibit the daemon from changing its own configuration. Expected usage is: first set the owner of the/etc/corosync/qnetddirectory toroot:$COROQNETDwith permissions0750, and then create the database (as root):
# corosync-qnetd-certutil -i -G
-nβ Name of the cluster. π·οΈ
π NOTES π
If qnetd is executed by a non root user, /etc/corosync/qnetd and all its subdirectories must be owned by (or have group access for) that given user. π
And if corosync-qnetd-certutil is executed as root, she tries to copy the owner and group of /etc/corosync/qnetd onto all of the files she creates. Such a considerate icon. π
π SEE ALSO π
β AUTHOR β
Jan Friesse β thank you for your service, legend π«‘π
and that's the whole page, babe β¨ this beauty is from 2016-06-28, and she lives in the COROSYNC-QNETD-CERTUTIL(8) era of the System Manager's Manual. go forth and generate those certificates, main character π¦π
π¦ where this page comes from
- debian bookworm: corosync-qnetd 3.0.3-1 Β· BSD-3-Clause
- debian trixie: corosync-qnetd 3.0.3-2 Β· BSD-3-Clause
- fedora 43: corosync-qnetd 3.0.3-10.fc43 Β· BSD-3-Clause
- fedora 43: corosync-qnetd 3.0.4-1.fc43 Β· BSD-3-Clause
- fedora 44: corosync-qnetd 3.0.4-3.fc44 Β· BSD-3-Clause
- nixos 26.05: corosync-qdevice 3.0.4
- nixpkgs unstable: corosync-qdevice 3.0.4
- opensuse-leap 16.0: corosync-qnetd 3.0.3-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: corosync-qnetd 3.0.3-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: corosync-qnetd 3.0.3-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: corosync-qnetd 3.0.3-160000.2.2 Β· BSD-3-Clause
- ubuntu jammy: corosync-qnetd 3.0.1-1 Β· BSD-3-Clause
- ubuntu noble: corosync-qnetd 3.0.3-1 Β· BSD-3-Clause
- ubuntu questing: corosync-qnetd 3.0.3-2
- ubuntu resolute: corosync-qnetd 3.0.4-1 Β· BSD-3-Clause
- ubuntu stonking: corosync-qnetd 3.0.4-1 Β· BSD-3-Clause
- Copyright (C) 2016 Red Hat, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms