monzero-core.git/tests/data, branch v0.18.4.4Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.18.4.42024-12-13T19:37:39Zp2p: allow comments in banlist files2024-12-13T19:37:39Zjeffro256jeffro256@tutanota.com2024-11-07T06:34:59Zurn:sha1:a1b545a2f7b2ac48d66e7fd846ca5093286525c7
In-line comments explicitly explaining banned hosts/subnets might help assuage fears of some good banlists' arbitaryiness.
wallet2: fix `store_to()` and `change_password()`2023-08-23T16:52:31Zjeffro256jeffro256@tutanota.com2023-07-07T17:55:02Zurn:sha1:ba98269ca507766aa76f0ebbcaebe6f6eef93192
Resolves #8932 and:
2. Not storing cache when new path is different from old in `store_to()` and
3. Detecting same path when new path contains entire string of old path in `store_to()` and
4. Changing your password / decrypting your keys (in this method or others) and providing a bad original password and getting no error and
5. Changing your password and storing to a new file
verRctNonSemanticsSimpleCached: fix fragility2023-03-17T23:46:34ZJeffrey Ryanjeffro256@tutanota.com2023-01-14T02:53:25Zurn:sha1:c59e0096b671528036563c1c30f31763a615aa75allow exporting outputs in chunks2022-09-07T06:22:07Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2022-08-16T20:20:38Zurn:sha1:0cbf5571d3ccd07c81d33b05dd23b2ac9c777c3b
this will make it easier huge wallets to do so without hitting
random limits (eg, max string size in node).
unit_tests: add more sha256sum test cases2022-05-17T23:34:20ZJeffrey Ryanjeffreyryan@tutanota.com2022-05-17T20:41:22Zurn:sha1:08080df2d9de877ae79028f20960b6b2417d4f20fuzz_tests: add a test for utf8canonical2020-12-14T19:40:24Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2020-12-14T14:25:44Zurn:sha1:0660db3e7a0f561ecd70c0cecc3bbf267534021breplace most boost serialization with existing monero serialization2020-08-17T16:23:58Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2020-06-24T23:26:58Zurn:sha1:7175dcb1078abbdaa130a8c5f5fd2b93fa7b3086
This reduces the attack surface for data that can come from
malicious sources (exported output and key images, multisig
transactions...) since the monero serialization is already
exposed to the outside, and the boost lib we were using had
a few known crashers.
For interoperability, a new load-deprecated-formats wallet
setting is added (off by default). This allows loading boost
format data if there is no alternative. It will likely go
at some point, along with the ability to load those.
Notably, the peer lists file still uses the boost serialization
code, as the data it stores is define in epee, while the new
serialization code is in monero, and migrating it was fairly
hairy. Since this file is local and not obtained from anyone
else, the marginal risk is minimal, but it could be migrated
later if needed.
Some tests and tools also do, this will stay as is for now.
fuzz_tests: add a tx extra fuzz test2020-06-14T12:54:10Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2020-05-16T11:43:45Zurn:sha1:38ca1bb389e1548fabd80dc314d805605248fb69wallet2: only export necessary outputs and key images2018-11-04T22:27:01Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-10-24T18:24:11Zurn:sha1:8d71b2b1b3714a13d46247ed7342a1ad292c488d
and disable annoying test that requires ridiculous amounts
of skullduggery every time some format changes
tests: update test wallet keys file for encrypted keys2018-09-15T09:34:11Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-09-15T09:25:17Zurn:sha1:27af46c9308b98b5f282ec50ae1d953cff025766