mirrors/arti.git/crates/fs-mistrust/src, branch arti-v0.4.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.02022-05-25T14:27:45Zfs-mistrust: allow symlinks to have any permissions2022-05-25T14:27:45ZAlex Xu (Hello71)alex_y_xu@yahoo.ca2022-05-24T20:17:45Zurn:sha1:85b4b5620d294b27cdee01989d4f2a936f6f32f4Use serde attrs instead of manual impls2022-05-24T14:54:02ZNick Mathewsonnickm@torproject.org2022-05-24T14:15:56Zurn:sha1:924cc380d478e2b4a6b2b7bacbbe780e3b8fee7cMake fs-mistrust configurable from the top level.2022-05-24T14:54:02ZNick Mathewsonnickm@torproject.org2022-05-23T15:31:47Zurn: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.
Write custom serde impls for Trusted{User,Group}2022-05-24T14:54:02ZNick Mathewsonnickm@torproject.org2022-05-20T19:15:56Zurn: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" }
```
Add serde derives for MistrustBuilder.2022-05-24T14:54:02ZNick Mathewsonnickm@torproject.org2022-05-18T20:29:23Zurn: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.
fs-mistrust: Add Group and User types.2022-05-24T14:54:02ZNick Mathewsonnickm@torproject.org2022-05-18T18:36:24Zurn:sha1:330582a142e30a80fe5f62af043955ca7373b7e7
This will help make the actual configuration more serializable,
I hope.
fs-mistrust: make Mistrust have a corresponding Builder type.2022-05-24T14:54:02ZNick Mathewsonnickm@torproject.org2022-05-18T17:26:01Zurn:sha1:95200383b52d1644d4de357c2a8a50d91fdc1021
This is an approximately minimal revision to get Builder in place;
subsequent commits will clean up the API.
fs-mistrust: rename fields2022-05-24T14:54:02ZNick Mathewsonnickm@torproject.org2022-05-18T15:52:17Zurn:sha1:baa58daace392eee68f8ff82841631e9114c9918
This renaming will make things slightly simpler for declaring a
builder.
Merge branch 'use-fs-mistrust'2022-05-09T19:27:25ZNick Mathewsonnickm@torproject.org2022-05-09T19:27:25Zurn:sha1:4262e9d0ecca5f77f6ee2e0b00fb8c35d65f01e3Loosen checking for readable files within target directories.2022-05-09T18:40:29ZNick Mathewsonnickm@torproject.org2022-05-09T16:01:08Zurn:sha1:5c33499f288c298c3db8dfc7725448db13427a36
If the target directory itself is unreadable by untrusted users,
then its contents can't be read[*] by them regardless of their
permissions. If the target directory _is_ readable, then _it_ will
be rejected if we are forbidding readable objects. (And if we
aren't we don't care if the contents are readable.)
A similar argument would apply to writable objects within an
unreadable target directory. We're not making that argument, since
such contents are likelier to be a mistake.
[*] Unless they're hard-linked; see comments in "Limitations"
section.