mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0 2022-05-27T13:01:20Z 2022-05-27T13:01:20Z Nick Mathewson nickm@torproject.org 2022-05-27T13:01:20Z urn:sha1:b232365a75249d6f767127feb2a47286f9ece762 I followed the following procedure to make these changes: * I used maint/changed_crates to find out which crates had changed since 0.3.0. * I used grep and maint/list_crates to sort those crates in topological (dependency) order. * I looked through semver_status to find which crates were listed as having semver-relevant changes (new APIs and breaking changes). * I scanned through the git logs of the crates with no semver-relevant changes listed to confirm that, indeed, they had no changes. For those crates, I incremented their patch-level version _without_ changing the version that other crates depend on. * I scanned through the git logs of the crates with no semver-relevant changes listed to confirm that, indeed, they had no obvious breaking changes. * I treated all crates that depend on `arti` and/or `arti-client` as having breaking changes. * I identified crates that depend on crates that have changed, even if they have not changed themselves, and identified them as having a non-breaking change. * For all of the crates, I used `cargo set-version -p $CRATE --bump $STATUS` (where `STATUS` is `patch` or `minor`) to update the versions, and the depended-upon versions. 2022-05-26T12:53:14Z Nick Mathewson nickm@torproject.org 2022-05-26T12:53:14Z urn:sha1:68b04197528896bf84774c738cf6439e73977c5e Standardise shell Closes #425 See merge request tpo/core/arti!533 2022-05-25T20:25:58Z trinity-1686a trinity@deuxfleurs.fr 2022-05-25T15:37:19Z urn:sha1:b380c25e6637b2cf48239eea8c4a3707eb3aa67e 2022-05-25T14:27:45Z Alex Xu (Hello71) alex_y_xu@yahoo.ca 2022-05-24T20:17:45Z urn:sha1:85b4b5620d294b27cdee01989d4f2a936f6f32f4 2022-05-24T14:54:02Z Nick Mathewson nickm@torproject.org 2022-05-24T14:15:56Z urn:sha1:924cc380d478e2b4a6b2b7bacbbe780e3b8fee7c 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. 2022-05-24T14:54:02Z Nick Mathewson nickm@torproject.org 2022-05-20T19:15:56Z urn:sha1:12f2a47fcb42ea3ccf3456a034dbdec82a8f0953 We support all of the following (in TOML notation): ``` user = "rose" # by name user = 413 # by ID user = false # no user user = ":current" # A 'special' user. user = { name: "rose" } user = { id: 413 } user = { special: ":none" } user = { special: ":current" } ``` 2022-05-24T14:54:02Z Nick Mathewson nickm@torproject.org 2022-05-18T20:29:23Z urn:sha1:9dd7b99de1b8bf8625cf6de93770dda25fe2823b The Group and User (de)serialization is pretty ugly, and I can't vouch for the correcness of MistrustBuilder. I will seek feedback before I proceed. 2022-05-24T14:54:02Z Nick Mathewson nickm@torproject.org 2022-05-18T18:36:24Z urn:sha1:330582a142e30a80fe5f62af043955ca7373b7e7 This will help make the actual configuration more serializable, I hope. 2022-05-24T14:54:02Z Nick Mathewson nickm@torproject.org 2022-05-18T17:26:01Z urn:sha1:95200383b52d1644d4de357c2a8a50d91fdc1021 This is an approximately minimal revision to get Builder in place; subsequent commits will clean up the API.