mirrors/arti.git/crates/arti-client/src/client.rs, branch arti-v0.5.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.5.0 2022-06-21T18:19:22Z channel padding: Plumb settings from chanmgr 2022-06-21T18:19:22Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-06-14T14:42:23Z urn:sha1:7f3f42673816be8924395c9db26e55bee5c9c412 Merge branch 'dormant_directory' into 'main' 2022-06-13T13:59:26Z Nick Mathewson nickm@torproject.org 2022-06-13T13:59:26Z urn:sha1:d44dd6f44fb6a1831affd6757132b189b4109323 Use TaskSchedule to sleep in directory bootstrapping Closes #497 See merge request tpo/core/arti!571 New API to expose and use TaskHandle from DirMgr. 2022-06-13T12:28:41Z Nick Mathewson nickm@torproject.org 2022-06-10T17:23:20Z urn:sha1:430f4ffb8612a01cb99775e6a0b4a4c3c4de8e0f This change also means that we need to create the handle and scheduler earlier in the process of creating the DirMgr. If we don't, we won't have a way to manage the task before bootstrap() returns. Move responsibility for GuardMgr NetDir updates to GuardMgr. 2022-06-07T15:44:51Z Nick Mathewson nickm@torproject.org 2022-06-02T21:35:01Z urn:sha1:dc0a4e3c3d20bb6708a1e20df1c07a78041b6111 Previously it was the job of a task in CircMgr to do this; but we're going to want to give GuardMgr full access to the latest NetDir for this, and for other code-simplification reasons. With this change I'm deprecating a couple of functions in tor-circmgr. It's no longer necessary for us to have an artificial external way for you to feed new NetDirs to a circmgr. (I could just remove them, but I want practice deprecating.) Remove now-redundant Send+Sync constraints alongside NetDirProvider 2022-06-07T15:44:51Z Nick Mathewson nickm@torproject.org 2022-06-02T21:11:59Z urn:sha1:957eb929a0a70ba1d77504d3618f9e8f3386fd70 Make fs-mistrust configurable from the top level. 2022-05-24T14:54:02Z Nick Mathewson nickm@torproject.org 2022-05-23T15:31:47Z urn:sha1:b1fc4bd03bb4024cd5a467ccb682e88adf30bac7 This change requires a little refactoring of TorClientBuilder: now, instead of enabling or disabling mistrust, it enables or disables the decision to _override_ the mistrust in the config. add unit tests for arti_client::StreamPrefs 2022-05-23T14:55:17Z michael mccune msm@opbstudios.com 2022-05-22T17:45:05Z urn:sha1:0d8f520faf84ba7b9e53dc8eead0b97ffd287ba0 this change adds unit tests for the public methods of StreamPrefs. although these are mostly "setter" style functions, the tests confirm the basic expectations and operation. Merge branch 'use-fs-mistrust' 2022-05-09T19:27:25Z Nick Mathewson nickm@torproject.org 2022-05-09T19:27:25Z urn:sha1:4262e9d0ecca5f77f6ee2e0b00fb8c35d65f01e3 arti-client: Configure and use fs-mistrust. 2022-05-09T18:40:29Z Nick Mathewson nickm@torproject.org 2022-05-03T18:58:03Z urn:sha1:2938268f34d0f9a110b06b86d92ac460247d01b8 This is derived from the environment, not the configuration file: We might not want to trust the configuration file until we've decided whether we like its permissions. Apply `sensitive` in some info-level log messages. 2022-05-06T11:36:50Z Nick Mathewson nickm@torproject.org 2022-05-02T23:44:12Z urn:sha1:4679023c39bc8658b6f1d44bc6bda8074c485520 This specifically applies the `sensitive` wrapper in the places where we're logging target addresses at level "info" or higher.