d89385c3e1
libnpa: requires an ID card that is initialized for QES. Today, this means you need to register at sign-me. virtualsmartcard: We don't actually create a real signature, because PyCrypto can't handle ECDSA, let alone brainpoolP256r1. We only return a 64 byte buffer.
41 lines
1.4 KiB
Plaintext
41 lines
1.4 KiB
Plaintext
app default {
|
|
|
|
# What card drivers to load at start-up
|
|
#
|
|
# A special value of 'internal' will load all
|
|
# statically linked drivers. If an unknown (ie. not
|
|
# internal) driver is supplied, a separate configuration
|
|
# configuration block has to be written for the driver.
|
|
# Default: internal
|
|
# NOTE: When "internal" keyword is used, must be last entry
|
|
#
|
|
card_drivers = npa, internal;
|
|
|
|
# Card driver configuration blocks.
|
|
#
|
|
# For card drivers loaded from an external shared library/DLL,
|
|
# you need to specify the path name of the module
|
|
#
|
|
card_driver npa {
|
|
# The location of the driver library
|
|
module = @libdir@/libcardnpa.@DYN_LIB_EXT@;
|
|
|
|
# German ID card requires the CAN to be verified before QES PIN. This,
|
|
# however, is not part of the PKCS#15 profile of the card. So for
|
|
# verifying the PIN we actually need both. The CAN may be given here.
|
|
# If the CAN is not given here, it will be prompted on the command line
|
|
# or on the reader.
|
|
can = 222222;
|
|
|
|
# QES is only possible with a Comfort Reader (CAT-K), which holds a
|
|
# cryptographic key to authenticate itself as signature terminal (ST).
|
|
# We usually will use the reader's capability to sign the data.
|
|
# However, during developement you may specify soft certificates and
|
|
# keys for a ST below.
|
|
# The following example EAC PKI can be found in npa-example-data
|
|
st_dv_certificate = ZZSTDVCA00001.cvcert;
|
|
st_certificate = ZZSTTERM00001.cvcert;
|
|
st_key = ZZSTTERM00001.pkcs8;
|
|
}
|
|
}
|