From 18db69be2d2bbacc6b9f4de2e9e8f8db2df4febe Mon Sep 17 00:00:00 2001 From: Gian Demarmels Date: Mon, 3 Jan 2022 14:38:59 +0100 Subject: initial cs_secmod implementation --- src/util/taler-exchange-secmod-cs.conf | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 src/util/taler-exchange-secmod-cs.conf (limited to 'src/util/taler-exchange-secmod-cs.conf') diff --git a/src/util/taler-exchange-secmod-cs.conf b/src/util/taler-exchange-secmod-cs.conf new file mode 100644 index 000000000..5085eab79 --- /dev/null +++ b/src/util/taler-exchange-secmod-cs.conf @@ -0,0 +1,23 @@ +[taler-exchange-secmod-cs] + +# How long should generated coins overlap in their validity +# periods. Should be long enough to avoid problems with +# wallets picking one key and then due to network latency +# another key being valid. The DURATION_WITHDRAW period +# must be longer than this value. +OVERLAP_DURATION = 5 m + +# Where do we store the generated private keys. +KEY_DIR = ${TALER_DATA_HOME}/exchange-secmod-cs/keys + +# Where does the helper listen for requests? +UNIXPATH = $TALER_RUNTIME_DIR/exchange-secmod-cs/server.sock + +# Directory for clients. +CLIENT_DIR = $TALER_RUNTIME_DIR/exchange-secmod-cs/clients + +# Where should the security module store its own private key? +SM_PRIV_KEY = ${TALER_DATA_HOME}/exchange-secmod-cs/secmod-private-key + +# For how long into the future do we pre-generate keys? +LOOKAHEAD_SIGN = 1 year -- cgit v1.2.3