| Tool | Object store type | Input |
|---|---|---|
softhsm2-dump-file | File-based object store | Path to a single object file |
softhsm2-dump-db | SQLite3 database object store | Path to a .db database file |
SoftHSM v2 supports two storage backends: a file-based store (one file per object) and a SQLite3 database store. Use the tool that matches the backend configured for your installation.
softhsm2-dump-file
Dumps a SoftHSM v2 object file from the file-based object store.Arguments
Path to the SoftHSM v2 object file to dump. Object files are stored in the token directory defined in
softhsm2.conf and have names like <uuid>.object.softhsm2-dump-file takes exactly one positional argument — the path — and no flags.Example
softhsm2-dump-db
Dumps a SoftHSM v2 SQLite3 database from the database-backed object store.Arguments
Path to the SoftHSM v2 SQLite3 database file to dump. The database file is named
sqlite3.db and is located inside the token’s UUID subdirectory in directories.tokendir.softhsm2-dump-db takes exactly one positional argument — the path — and no flags.Example
Debugging workflow
Identify your storage backend
Check your
softhsm2.conf to determine whether you are using the file-based or SQLite3 backend, and locate the token directory.Locate the object store
For the file backend, navigate to the token directory and identify the object files. For the database backend, find the
.db file in the token directory.See also
softhsm2-util— token management and key importsofthsm2.conf(5)— SoftHSM configuration reference