Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-02-04 | implement feedback | Lucien Heuzeveldt | |
2022-02-04 | -scope needed | Christian Grothoff | |
2022-02-04 | change TEH_keys_denomination_sign message parameter | Lucien Heuzeveldt | |
2022-02-04 | refactoring | Gian Demarmels | |
2022-02-04 | implement spend | Lucien Heuzeveldt | |
2022-02-04 | removed varargs | Gian Demarmels | |
2022-02-04 | implement withdraw (nonce reuse check missing) | Lucien Heuzeveldt | |
2022-02-04 | cleanup | Gian Demarmels | |
2022-02-04 | secmod CS sign implementation | Gian Demarmels | |
2022-02-04 | implement CS key handling and csr endpoint | Lucien Heuzeveldt | |
2022-02-04 | set planchet detail cipher, add cipher checks | Lucien Heuzeveldt | |
2022-02-04 | implement TALER_CRYPTO_helper_cs_r_derive and related tests | Lucien Heuzeveldt | |
2022-02-04 | implement secmod cs derive R | Lucien Heuzeveldt | |
2022-02-04 | revocation | Gian Demarmels | |
2022-02-04 | setup_key for cs secmod helper | Gian Demarmels | |
2022-02-04 | initial cs_secmod implementation | Gian Demarmels | |
2022-02-04 | secmod cs signatures implementation | Gian Demarmels | |
2022-02-04 | fix const due to changes in TALER_planchet_prepare | Lucien Heuzeveldt | |
2022-02-04 | clean up cs implementation | Lucien Heuzeveldt | |
2022-02-04 | remove varargs in cs crypto implementation | Lucien Heuzeveldt | |
2022-02-04 | utility functions | Gian Demarmels | |
2022-02-04 | fixed CS signatures and cleanup/refactoring | Gian Demarmels | |
2022-02-04 | implement exchange_api_csr | Lucien Heuzeveldt | |
2022-02-04 | add sign and verify implementation | Gian Demarmels | |
2022-02-04 | sign_blinded implementation | Gian Demarmels | |
2022-02-04 | implemented planchet_prepare for CS | Gian Demarmels | |
2022-02-04 | added CS get R functionality and planchet setup | Gian Demarmels | |
2022-02-04 | CS planchet create and withdraw create | Gian Demarmels | |
2022-02-04 | added CS data structures, implemented CS keypair | Gian Demarmels | |
2022-02-03 | fix hyphenation | Christian Grothoff | |
2022-02-03 | -more edits from Dora | Christian Grothoff | |
2022-02-03 | -fix amp | Christian Grothoff | |
2022-02-02 | -corrections at cbdc-it + FIXMEs | ms | |
2022-02-01 | -more fixes from Dora | Christian Grothoff | |
2022-02-01 | diagramma | Christian Grothoff | |
2022-02-01 | luca | Christian Grothoff | |
2022-02-01 | -corrections from Dora | Christian Grothoff | |
2022-02-01 | corrections from Dora | Christian Grothoff | |
2022-01-31 | cbdc-it | Christian Grothoff | |
2022-01-31 | cbdc - Italian edition | Christian Grothoff | |
2022-01-27 | test and hopefully fix JSON canonicalization | Florian Dold | |
2022-01-27 | fix RFC 8785 JSON normalization | Florian 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-22 | improvements 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-18 | fix 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-18 | use 'pipe' instead of 'eventfd' on non-Linux systems | Jonathan Buchanan | |
2022-01-11 | fix #7143 | Christian Grothoff | |
2022-01-11 | The 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-10 | fix amount denormalization issue | Christian Grothoff | |