> 0:/var/opendnssec/kasp.db
> 1:/var/opendnssec/slot1.db
> or
> 0:/home/test/slot0
> 1:/var/opendnssec/slot1.db
> I confused which is the right one, maybe the problem is that I fetched the
> data in a wrong .db file .
You can use whatever you want. As long as SoftHSM has R/W privilege on
that path
On 04/07/12 11:00, Rickard Bellgrim wrote:
When the Enforcer list the keys, it only look into its own database of
DNSSEC keys. There is no search performed in the HSM. The Enforcer
only has the CKA_ID of the objects in the HSM.
Unless you include the "--verbose" flag when it needs access to th
> That really puzzled me why there was a sudden error with softhsm.
> $ softhsm --show-slot
> Available slots:
> Slot 0
>Token present: yes
>Token initialized: no
>User PIN initialized: no
> initialized:no? I'm sure I use this slot to create keys before this disa
Hi all,
After I signed a zone and I noticed there were something wrong in the log:
Jul 4 10:21:34 CST-BJ-104 ods-signerd: *** glibc detected ***
/usr/local/sbin/ods-signerd: double free or corruption (!prev):
0x7f006132f020 ***
I knew the ods-signerd process was down, because I met this kind
