Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-08-26 | Add support for setting a custom monotonic time function in mono_time | zugz (tox) | |
2018-08-21 | consistently use 'mono_time' rather than 'monotime' | zugz (tox) | |
2018-08-19 | make Mono_Time an argument to current_time_monotonic | zugz (tox) | |
2018-08-16 | Use per-instance `Mono_Time` for Messenger and onion. | iphydf | |
2018-08-10 | Use the crypto random functions instead of `rand()`. | iphydf | |
Presumably the uses of `rand()` were fine because they were not used in security-sensitive places, but having to think about whether a crappy RNG is acceptable in each situation requires effort that could better be spent elsewhere. Also, this means that once we have a custom deterministic RNG for testing, that RNG is used everywhere, so all the code is deterministic. It also allowed us to delete a system-specific function that wasn't used anywhere except in a call to `srand()`. | |||
2018-07-09 | Factor out time keeping code into its own module: mono_time.c. | iphydf | |
It turns out, `unix_time` is also monotonic, and is used as such, so I've renamed the new functions to `mono_time_*`. 2018-07-08: ``` 00:01 <@irungentoo> the idea used to be that the unix_time() function could go backward in time but I think I might have started using it like if it could not after I changed it so that it would never go back in time ``` |