ods-hsmutil(1)
π ods-hsmutil β the OpenDNSSEC HSM utility (section 1 of the manual, bestie)
okay so. gather round. this is ods-hsmutil, the OpenDNSSEC HSM utility, and she is that girl β the little tool you reach for when you need to talk directly to your Hardware Security Module. manual section 1, in case the vibe check needed numbers. π
β¨ SYNOPSIS β¨
ods-hsmutil [-c config] [-v] command [options]
π¦ DESCRIPTION π¦
so ods-hsmutil is mostly a debugging/testing bestie. that's her whole thing. she's built to interact directly with your HSM, no middleman, no filter, and you can use her to manually list, create or delete keys. she can also run a little set of basic HSM tests, like a self-care routine but for hardware. πΈ
π¨ okay listen. be careful before you create or delete keys with ods-hsmutil, because those changes are not synchronized with the KASP Enforcer. it's giving "I edited the doc and nobody else knows". no cap. π
the repositories are configured by you, the user, in the OpenDNSSEC configuration file. that config holds the name of the repository, the token label, the user PIN, and the path to its shared library. all the little identifying details. π
π COMMANDS π
loginβ if there's no PIN inconf.xml, this command will ask you for it and log in. the PINs get stored in shared memory and are accessible to the other daemons. it's giving communal notes app. πlogoutβ erases the semaphore and the shared memory holding any credentials. but heads up: authenticated processes will still be able to interact with the HSM. she logs out but the group chat stays open. πlist [repository]β lists the keys available in all repositories, or in just one repository if you name it. window shopping. ποΈgenerate repository rsa|dsa|gost|ecdsa [keysize]β generates a new key with the given keysize in the repository. note that GOST has a fixed key size, and ECDSA has two supported curves:P-256andP-384. for ECDSA, use256or384as the keysize. manifesting a key. β¨remove idβ deletes the key with the given id. bye bestie πpurge repositoryβ deletes all keys in one repository. nuclear. absolutely nuclear. π§¨dnskey id name type algoβ creates a DNSKEY RR for the given owner name, based on the key with this id. the type tells it whether it's a KSK (257) or a ZSK (256) β please use the numerical value, not the vibe. the algo, a value from the IANA repository, must match the algorithm of the key. matching energy only. πtest repositoryβ performs a number of tests on a repository. her lil checkup. π©Ίinfoβ shows detailed information about all repositories. the full tea. β
π OPTIONS π
-cconfig β path to an OpenDNSSEC configuration file.- defaults to
/etc/opendnssec/conf.xmlποΈ
- defaults to
-hβ show the help screen. she'll explain herself. π«Ά-vβ output more information by increasing the verbosity level. the more-vs, the more she yaps. π£οΈ
π₯ SEE ALSO π₯
ods-control(8), ods-enforcerd(8), ods-hsmspeed(1), ods-kaspcheck(1), ods-signer(8), ods-signerd(8), ods-enforcer(8), ods-timing(5), ods-kasp(5), opendnssec(7), http://www.opendnssec.org/
go read those too. iykyk. π
π AUTHORS π
ods-hsmutil was written by Jakob Schlyter as part of the OpenDNSSEC project. iconic behaviour, honestly. π
and that's the whole page, bestie β OpenDNSSEC, February 2010, ods-hsmutil(1). slay, stay safe with those keys, and remember: purge responsibly. periodt. π
β¨
π¦ where this page comes from
- centos-stream 10: opendnssec 2.1.14-1.el10 Β· BSD-2-Clause
- centos-stream 9: opendnssec 2.1.10-4.el9 Β· BSD
- debian bookworm: libhsm-bin 1:2.1.12-2
- fedora 43: opendnssec 2.1.14-2.fc43 Β· BSD-2-Clause
- fedora 44: opendnssec 2.1.14-3.fc44 Β· BSD-2-Clause
- ubuntu jammy: libhsm-bin 1:2.1.10-1build1
- ubuntu noble: libhsm-bin 1:2.1.13-1.1
- ubuntu noble: libhsm-bin 1:2.1.13-1.1ubuntu1.1
- ubuntu questing: libhsm-bin 1:2.1.13-1.2ubuntu3
- ubuntu questing: libhsm-bin 1:2.1.13-1.2ubuntu3.2
- ubuntu resolute: libhsm-bin 1:2.1.13-1.2ubuntu5
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms