| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | epee: allow copying a rolling_median_t object | moneromooo-monero | 2022-04-10 | 1 | -0/+18 |
| | | |||||
| * | Copyright: Update to 2022 | mj-xmr | 2022-03-04 | 1 | -1/+1 |
| | | |||||
| * | Fix overflow issue in epee:misc_utils::rolling_median_t and median(), with ↵ | koe | 2020-07-23 | 1 | -0/+11 |
| | | | | | unit test | ||||
| * | Update copyright year to 2020 | SomaticFanatic | 2020-05-06 | 1 | -1/+1 |
| | | | | | Update copyright year to 2020 | ||||
| * | Replace std::random_shuffle with std::shuffle | Tom Smeding | 2019-08-15 | 1 | -1/+1 |
| | | | | | | | | | | | | | | According to [1], std::random_shuffle is deprecated in C++14 and removed in C++17. Since std::shuffle is available since C++11 as a replacement and monero already requires C++11, this is a good replacement. A cryptographically secure random number generator is used in all cases to prevent people from perhaps copying an insecure std::shuffle call over to a place where a secure one would be warranted. A form of defense-in-depth. [1]: https://en.cppreference.com/w/cpp/algorithm/random_shuffle | ||||
| * | use crypto::rand instead of libc rand in a few tests | moneromooo-monero | 2019-05-10 | 1 | -4/+4 |
| | | | | | We don't need secure randomness here, but it should shut coverity up | ||||
| * | blockchain: keep a rolling long term block weight median | moneromooo-monero | 2019-05-02 | 1 | -0/+202 |
 |
index : monzero-core.git | |
| Monzero core node, command-line wallet, consensus code, and release tooling. | www-data |
| aboutsummaryrefslogtreecommitdiff |