summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2022-02-04implement feedbackLucien Heuzeveldt
2022-02-04-scope neededChristian Grothoff
2022-02-04change TEH_keys_denomination_sign message parameterLucien Heuzeveldt
2022-02-04refactoringGian Demarmels
2022-02-04implement spendLucien Heuzeveldt
2022-02-04removed varargsGian Demarmels
2022-02-04implement withdraw (nonce reuse check missing)Lucien Heuzeveldt
2022-02-04cleanupGian Demarmels
2022-02-04secmod CS sign implementationGian Demarmels
2022-02-04implement CS key handling and csr endpointLucien Heuzeveldt
2022-02-04set planchet detail cipher, add cipher checksLucien Heuzeveldt
2022-02-04implement TALER_CRYPTO_helper_cs_r_derive and related testsLucien Heuzeveldt
2022-02-04implement secmod cs derive RLucien Heuzeveldt
2022-02-04revocationGian Demarmels
2022-02-04setup_key for cs secmod helperGian Demarmels
2022-02-04initial cs_secmod implementationGian Demarmels
2022-02-04secmod cs signatures implementationGian Demarmels
2022-02-04fix const due to changes in TALER_planchet_prepareLucien Heuzeveldt
2022-02-04clean up cs implementationLucien Heuzeveldt
2022-02-04remove varargs in cs crypto implementationLucien Heuzeveldt
2022-02-04utility functionsGian Demarmels
2022-02-04fixed CS signatures and cleanup/refactoringGian Demarmels
2022-02-04implement exchange_api_csrLucien Heuzeveldt
2022-02-04add sign and verify implementationGian Demarmels
2022-02-04sign_blinded implementationGian Demarmels
2022-02-04implemented planchet_prepare for CSGian Demarmels
2022-02-04added CS get R functionality and planchet setupGian Demarmels
2022-02-04CS planchet create and withdraw createGian Demarmels
2022-02-04added CS data structures, implemented CS keypairGian Demarmels
2022-02-03fix hyphenationChristian Grothoff
2022-02-03-more edits from DoraChristian Grothoff
2022-02-03-fix ampChristian Grothoff
2022-02-02-corrections at cbdc-it + FIXMEsms
2022-02-01-more fixes from DoraChristian Grothoff
2022-02-01diagrammaChristian Grothoff
2022-02-01lucaChristian Grothoff
2022-02-01-corrections from DoraChristian Grothoff
2022-02-01corrections from DoraChristian Grothoff
2022-01-31cbdc-itChristian Grothoff
2022-01-31cbdc - Italian editionChristian Grothoff
2022-01-27test and hopefully fix JSON canonicalizationFlorian Dold
2022-01-27fix RFC 8785 JSON normalizationFlorian Dold
2022-01-23[age_restriction] progress 13/nÖzgür Kesim
- major refactoring of extensions - extensions live now in a separate library, libtalerextensions - refactored all components using age_restriction accordingly - plumbing for plugin support for extensions roughly layed down
2022-01-22improvements in extension handlingÖzgür Kesim
- extensions_sig is needed globally - keep original json with config of extension - fixed various bugs re: extension handling
2022-01-21[age restriction] progress 12/nÖzgür Kesim
- taler-offline-tool now handles extensions - command "extensions" added with subcommands "show" and "sign" - parses extensions from taler config - shows and signs of extensions and their configurations - creates signed set of configurations for upload - added test for retrieval of extension config - simplified signature verification for extensions - remove per-extension signatures, also from DB schema - adjust prepared statements accordingly - adjust DB event handler for extensions - allow NULL for config for extension in DB schema - handler for /management/extensions adjusted to new datastructures - changed test for TALER_denom_blind/TALER_denom_sign_blinded with and without TALER_AgeHash - minor updates and various fixes
2022-01-18fix FTBFS (Linux) for 2022-01-18, "use 'pipe' instead of 'eventfd' on ↵Thien-Thi Nguyen
non-Linux systems" add back #include <sys/eventfd.h>, but conditionalize on #ifdef __linux__ (This fix follows the spirit of the other changes (i.e., adding #ifdef __linux__) but might not be the best solution.)
2022-01-18use 'pipe' instead of 'eventfd' on non-Linux systemsJonathan Buchanan
2022-01-11fix #7143Christian Grothoff
2022-01-11The current recoup API is broken. I guess this is another example where ↵Christian Grothoff
"trivial" API changes turn out to have (multiple!) unexpected consequences. The current "/recoup" API does not have clear idempotency semantics, as we've discussed on the phone. This is already bad by itself, as it makes it hard to write down what the API does other than "whatever the implementation does". However, it actually breaks correctness in this (admittedly kinda contrived, but not impossible) case: Say that we have a coin A obtained via withdrawal and a coin B obtained via refreshing coin A. Now the denominations of A gets revoked.. The wallet does a recoup of A for EUR:1. Now the denomination of B also gets revoked. The wallet recoups B (incidentally also for EUR:1) and now A can be recouped again for EUR:1. But now the exchange is in a state where it will refuse a legitimate recoup request for A because the detection for an idempotent request kicks in. This is IMHO bad API design, and the exchange should simply always recoup the maximum amount. Furthermore, we usually follow the principle of "API calls that take up DB space are paid". With the current recoup API, I can do many tiny recoup requests which the exchange then has to store, right? I guess it would not be a big change to remove the "amount" value from the recoup/recoup-refresh request bodies, right? - Florian
2022-01-10fix amount denormalization issueChristian Grothoff