exchange

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

commit f965adcf106e78c5ee6e93830143fff463d5c9e9
parent ebd836271b7810660db7c2b12926d140cc6276f1
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sun,  4 May 2025 20:41:04 +0200

FIXME for future

Diffstat:
Msrc/kyclogic/taler-exchange-helper-measure-clear-continue | 6++++++
1 file changed, 6 insertions(+), 0 deletions(-)

diff --git a/src/kyclogic/taler-exchange-helper-measure-clear-continue b/src/kyclogic/taler-exchange-helper-measure-clear-continue @@ -103,6 +103,12 @@ NEW_RULES=$(echo "$CURRENT_RULES" | jq '(.rules[] |= if (.measures[0]=="'"${CLEA echo "Passing new rules ${NEW_RULES} to ${EXEC_NAME}." 1>&2 +# FIXME: we might want to restrict EXEC_NAME to binaries +# with a certain prefix and/or even validate that it is +# an AML program in some 'approved' list. Right now, an +# AML officer (reasonably trusted...) could basically +# run any binary on the server here... + # Finally, pass the new rules as input to the AML program '$EXEC_NAME'. jq -n \ --argjson nc "$NEXT_CONTEXT" \