mirrors/arti.git/crates/fs-mistrust/src/imp.rs, branch arti-v2.1.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.1.02025-08-07T15:28:36ZSwitch Cargo.toml files to edition 2024.2025-08-07T15:28:36ZNick Mathewsonnickm@torproject.org2025-08-06T01:19:58Zurn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
Update code for Edition 20242025-08-07T15:28:31ZNick Mathewsonnickm@torproject.org2025-08-07T12:44:47Zurn:sha1:0453fb4be8cf618b94230812957ce1db1afe74bd
1. Run cargo fix --edition
2. Selectively revert the "if let"->"match" changes.
These changes are meant to protect us from the lifetime changes
for "if let" bindings in Rust 2024.
But we're not actually relying on the old lifetime rules
anywhere, and the match syntax here is quite ugly.
3. Automatically revert `$pat:expr_2021` to `$pat:expr`.
(We don't actually want to restrict the expression syntax
that our macros accept).
Done with
`git grep -l expr_2021 | xargs perl -i -pe 's/expr_2021/expr/g;'`
4. Run cargo fmt.
fix compiling fs-misstrust on tvOS2025-03-26T15:27:09Zyaucpthomas.yau@kape.com2025-03-26T15:27:09Zurn:sha1:0a4c1e155a926da2c568c92ef9338fc8eefed6c4fix fs-misstrust on android2022-08-08T20:32:07Ztrinity-1686atrinity@deuxfleurs.fr2022-08-08T20:32:07Zurn:sha1:3cb5d27fb7970b391588c17da4277a5abdb79c64
it would fail to link at runtime due to missing getgrnam_r in bionic
and then it would fail again because some directory is group writeable
fix runtime issues on ios2022-07-30T13:42:37Ztrinity-1686atrinity@deuxfleurs.fr2022-07-30T13:17:16Zurn:sha1:19a71534ec6f3f43462c197c9bb964e03356bdedremove dependancy 'users' on iOS2022-07-30T09:28:03Ztrinity-1686atrinity@deuxfleurs.fr2022-07-30T09:28:03Zurn:sha1:68ad22a9852b242e6b87e21bdb51b538fbcd81bcfs-mistrust: API to disable based on environment2022-07-19T19:21:09ZNick Mathewsonnickm@torproject.org2022-07-15T16:08:13Zurn:sha1:03b5efbd6e83d9e6c97f7b46507b1ad925566859
By default we look at `$FS_MISTRUST_DISABLE_PERMISSIONS_CHECKS`.
Optionally, the user can provide another variable as well, or
disable looking at the environment entirely.
fs-mistrust: Improve BadPermission string2022-05-31T18:23:01ZAlex Xu (Hello71)alex_y_xu@yahoo.ca2022-05-30T18:18:20Zurn:sha1:bc6b02045ee4e5515f0f057998ef257638bffaf4
To me, "Incorrect permissions on file or directory /path: g=w o=w"
implies that the current permissions on /path are 022.
Change the message to "Incorrect permissions: /path is
u=rwx,g=rwx,o=rwx; need g-w,o-w", which is closer to chmod syntax and is
more useful in non-interactive environments such as CI and support.
fs-mistrust: allow symlinks to have any permissions2022-05-25T14:27:45ZAlex Xu (Hello71)alex_y_xu@yahoo.ca2022-05-24T20:17:45Zurn:sha1:85b4b5620d294b27cdee01989d4f2a936f6f32f4fs-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.