SOFTHSM2-MIGRATE(1)
π SOFTHSM2-MIGRATE π
okay bestie, gather round, because this is the SoftHSM v1 migration tool and it's lowkey a whole legend. it lives in the General Commands Manual section of your man pages, and it's here to move your old SoftHSM v1 database into the PKCS#11 era. slay.
β¨ NAME β¨
softhsm2-migrate β the SoftHSM v1 migration tool. that's it, that's the whole vibe. it takes your dusty old v1 database and gives it a glow-up into PKCS#11. π
π¦ SYNOPSIS π¦
softhsm2-migrate --db path --token label [--pin PIN --no-public-key]
look at her. minimal. iconic. the way she needs a --db and a --token and then optionally a --pin and --no-public-key in that cute little bracket situation. periodt.
πΈ DESCRIPTION πΈ
so here's the tea, bestie: softhsm2-migrate is a tool that can migrate SoftHSM v1 databases to PKCS#11. that's literally its whole job and it does it gorgeously. π«Ά
the default HSM it targets is SoftHSM v2, but ngl you're not locked in β you can point it at other PKCS#11 libraries too by using the --module option. main character energy, honestly.
π OPTIONS π
--dbpath β the SoftHSM v1 database that's gonna get migrated. the location of the token database can be found in the configuration file for SoftHSM v1. go look, it's in there, i promise. π--help,-hβ show the help information. the classic. the "wait what were the flags again" button.--modulepath β use another PKCS#11 library than SoftHSM. go off, choose your own adventure.--no-public-keyβ do not migrate the public key. leave it behind, it's fine, it'll be okay. π--pinPIN β the PIN for the normal user. yes you need it, no you can't skip it if you want in.--serialnumber β will use the token with a matching serial number. like a little name tag but numbers. π₯--slotnumber β the database will be migrated to this slot. pick your slot, bestie.--tokenlabel β will use the token with a matching token label. this is the one you probably want.--version,-vβ show the version info. for when you need to know exactly which era of this tool you're dealing with.
π EXAMPLE π
a token database can be migrated with the following command:
softhsm2-migrate --db /home/user/token.db --token mytoken
look at her go. --db pointing at the database, --token naming the token, done. ate. π
π AUTHORS π
Written by Rickard Bellgrim, Francis Dupont, RenΓ© Post, and Roland van Rijswijk. four whole icons collaborated on this and we simply must respect it. π
π SEE ALSO π
ok that's the whole page bestie, no cap. every flag, every path, every number, all still exactly where you left them. iykyk. β¨
SoftHSM β 20 April 2016. mwah, that's the version and the date, and that's a wrap. π¦πβ¨
π¦ where this page comes from
- arch rolling: softhsm 2.7.0-1 Β· BSD-2-Clause
- centos-stream 10: softhsm 2.6.1-16.el10 Β· BSD
- centos-stream 9: softhsm 2.6.1-11.el9 Β· BSD
- debian bookworm: softhsm2 2.6.1-2.1 Β· BSD-2-Clause
- debian trixie: softhsm2 2.6.1-3 Β· BSD-2-Clause
- fedora 43: softhsm 2.6.1-13.fc43.1 Β· BSD-2-clause
- fedora 44: softhsm 2.7.0-0.1.rc1.fc44.1 Β· BSD-2-clause
- opensuse-leap 16.0: softhsm 2.6.1-bp160.1.15 Β· BSD-2-Clause
- opensuse-leap 16.0: softhsm 2.6.1-bp160.1.15 Β· BSD-2-Clause
- opensuse-leap 16.0: softhsm 2.6.1-bp160.1.15 Β· BSD-2-Clause
- opensuse-leap 16.0: softhsm 2.6.1-bp160.1.15 Β· BSD-2-Clause
- ubuntu jammy: softhsm2 2.6.1-2ubuntu1 Β· BSD-2-Clause
- ubuntu noble: softhsm2 2.6.1-2.2ubuntu3 Β· BSD-2-Clause
- ubuntu questing: softhsm2 2.6.1-2.2ubuntu3
- ubuntu resolute: softhsm2 2.6.1-3 Β· BSD-2-Clause
- ubuntu stonking: softhsm2 2.6.1-3ubuntu1 Β· BSD-2-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms