exchange

Base system with REST service to issue digital coins, run by the payment service provider
Log | Files | Refs | Submodules | README | LICENSE

commit a467ba6a541048d53f77d7e74fd439fac6c5ed31
parent c8480d97a17e1ab8f358dadc48e6e9b3ea17f6da
Author: Özgür Kesim <oec-taler@kesim.org>
Date:   Mon, 29 Nov 2021 10:12:08 +0100

typo and pointer comparison fixed

Diffstat:
Msrc/util/crypto_helper_rsa.c | 2+-
Msrc/util/taler-exchange-secmod-rsa.c | 2+-
2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/util/crypto_helper_rsa.c b/src/util/crypto_helper_rsa.c @@ -240,7 +240,7 @@ handle_mt_avail (struct TALER_CRYPTO_RsaDenominationHelper *dh, &denom_pub, &kan->secm_pub, &kan->secm_sig, - (&kan->age_restricted > 0)); + (kan->age_restricted > 0)); TALER_denom_pub_free (&denom_pub); } return GNUNET_OK; diff --git a/src/util/taler-exchange-secmod-rsa.c b/src/util/taler-exchange-secmod-rsa.c @@ -20,7 +20,7 @@ * * Key design points: * - EVERY thread of the exchange will have its own pair of connections to the - * crypto helpers. This way, every threat will also have its own /keys state + * crypto helpers. This way, every thread will also have its own /keys state * and avoid the need to synchronize on those. * - auditor signatures and master signatures are to be kept in the exchange DB, * and merged with the public keys of the helper by the exchange HTTPD!