2015-05-18 11:41:41 +00:00
|
|
|
NATIVE_PKCS11
|
2014-04-10 16:01:27 +00:00
|
|
|
When using the NATIVE_PKCS11 option, BIND will use the PKCS#11
|
|
|
|
engine specified by the named_pkcss11_engine variable in
|
|
|
|
/etc/rc.conf for *all* crypto operations.
|
|
|
|
|
|
|
|
This is primarily intended to be used in an authoritative
|
|
|
|
case.
|
|
|
|
|
2015-05-18 11:41:41 +00:00
|
|
|
If BIND is also operating as a validating resolver,
|
2014-04-10 16:01:27 +00:00
|
|
|
NATIVE_PKCS11 should not be used, because the HSM will be
|
2015-05-18 11:41:41 +00:00
|
|
|
used for all crypto, including DNSSEC validations, and the
|
|
|
|
HSM is likely to be slower than the CPU for this purpose.
|
|
|
|
Additionally, the HSM might not support all of the PKCS#11
|
|
|
|
API functions needed for signature verification.
|
2014-05-17 21:30:24 +00:00
|
|
|
|
|
|
|
|
2015-06-01 10:13:58 +00:00
|
|
|
START_LATE
|
|
|
|
Most of the time, BIND needs to start early in the boot
|
|
|
|
process. Enable this if BIND starts too early for you and
|
|
|
|
you need it to start later.
|