taler-exchange-secmod-rsa.conf (1569B)
1 [taler-exchange-secmod-rsa] 2 3 # How long should generated coins overlap in their validity 4 # periods. Should be long enough to avoid problems with 5 # wallets picking one key and then due to network latency 6 # another key being valid. The DURATION_WITHDRAW period 7 # must be longer than this value. 8 OVERLAP_DURATION = 0 m 9 10 # Where do we store the generated private keys. 11 # Denomination subdirectories use lowercase section names. Existing mixed-case 12 # directories are renamed on startup; conflicting names must be resolved first. 13 # Denomination section names must not contain '/'. 14 # Entries in KEY_DIR must not be symbolic links. 15 KEY_DIR = ${TALER_DATA_HOME}secmod-rsa/keys 16 17 # Where does the helper listen for requests? 18 UNIXPATH = ${TALER_RUNTIME_DIR}secmod-rsa/server.sock 19 20 # Directory for clients. 21 CLIENT_DIR = ${TALER_RUNTIME_DIR}secmod-rsa/clients 22 23 # Where should the security module store its own private key? 24 SM_PRIV_KEY = ${TALER_DATA_HOME}secmod-rsa/secmod-private-key 25 26 # For how long into the future do we pre-generate keys? 27 LOOKAHEAD_SIGN = 1 year 28 29 # Align the validity period of the keys to (UTC) calendar intervals: the start 30 # date is rounded down and the end date rounded up to this interval. Only 0 (no 31 # rounding, the default) and exactly "1 s", "1 minute", "1 hour", "1 day", 32 # "1 week", "1 month", "3 months" and "1 year" are supported. Can also be set 33 # per denomination, which takes precedence over the value given here. 34 # The exchange does not need this; Donau uses "1 year" to have its keys be 35 # valid for exactly one calendar year. 36 ANCHOR_ROUND = 0