monzero-core.git/src, branch v0.15.0.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.15.0.12019-11-19T09:20:04Zmake d2h et al. constant-time2019-11-19T09:20:04ZJethro Grassiejtg@xtrabass.com2019-11-08T06:26:17Zurn:sha1:443b1e9fee964873ede0fde61dc34d834473b47bMerge pull request #61522019-11-18T20:59:10Zluigi1111luigi1111w@gmail.com2019-11-18T20:59:10Zurn:sha1:cb3aad4b4603b4d40207a5ceaf0964cb5298014e
74b0ca4 v0.15.0.1 version bump (moneromooo-monero)
v0.15.0.1 version bump2019-11-18T19:23:30Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-11-18T19:23:30Zurn:sha1:74b0ca4bed68e562a7616085a8a20900af16fd10Fix #6147 DB corruption from child process overwrite2019-11-17T14:05:16ZHoward Chuhyc@symas.com2019-11-17T11:41:09Zurn:sha1:4dc4e1f1505523b0f0c7085f8cbb486f1a9d424c
Don't leave stdout/stderr dangling on a fork.
wallet: set non-empty error string on connection failure2019-11-15T13:09:02Zxiphonxiphon@protonmail.com2019-11-14T19:49:57Zurn:sha1:2a8953c0192792ac51fdcbfb78978a4ccc594811wallet2: fix pool txes not being flushed when mined2019-11-04T19:33:22Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-11-04T19:32:48Zurn:sha1:cbec8eb10bd0f0d82b6524df2b4af714b1b3599aMerge pull request #60752019-11-03T22:51:11ZRiccardo Spagniric@spagni.net2019-11-03T22:51:10Zurn:sha1:e046c02ec318cf52e8c913c1bf847bd489d5c1f3
912ff6abe simplewallet: plug a timing leak (moneromooo-monero)
cc2fc0bc3 epee: allow a random component in once_a_time timeouts (moneromooo-monero)
c0f504787 wallet: reuse cached height when set after refresh (moneromooo-monero)
f98d9673e wallet2: fix is_synced checking target height, not height (moneromooo-monero)
98cdc8492 wallet: fix another facet of "did I get some monero" information leak (moneromooo-monero)
69b8aa5a2 wallet2: do not send an unnecessary last getblocks.bin call on refresh (moneromooo-monero)
2ca057402 wallet2: do not repeatedly ask for pool txes sent to us (moneromooo-monero)
Merge pull request #60792019-11-02T15:32:39ZRiccardo Spagniric@spagni.net2019-11-02T15:31:22Zurn:sha1:4ad0f003859f26851c35299c26a451f4f319410e
e4d1674e8 0.15.0.0 release engineering (Riccardo Spagni)
simplewallet: plug a timing leak2019-11-02T11:41:30Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-10-15T10:30:50Zurn:sha1:912ff6abebe43caf16b3b384c7fde684a3dcb142
As reported by Tramèr et al, timing of refresh requests can be used
to see whether a password was requested (and thus at least one output
received) since this will induce a delay in subsequent calls.
To avoid this, we schedule calls at a given time instead of sleeping
for a set time (which would make delays additive).
To further avoid a scheduled call being during the time in which a
password is prompted, the actual scheduled time is now randomized.
wallet: reuse cached height when set after refresh2019-11-01T19:00:20Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-10-15T19:16:13Zurn:sha1:c0f50478785a67e854228bf392129cdefb55900d
Refreshing sets cached height, which is otherwise got by calling
get_info. Since get_info is called upon needing to display a prompt
after a command has finished, it can be used to determine how much
time a given command took to run if the cache timeout lapses while
the command runs. Refreshing caches the height as a side effect, so
get_info will never be called as a result of displaying a prompt
after refreshing (and potentially leaking how much time it took to
process a set of transactions, therefore leaking whether we got
some monero in them).