mirrors/arti.git/crates/fs-mistrust, branch arti-v1.4.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.22025-03-31T17:59:48ZBump the versions of the non-{arti-,tor-} crates.2025-03-31T17:59:48ZGabriela Moldovangabi@torproject.org2025-03-31T17:33:52Zurn:sha1:a0919b507bb2a5855e36b85a2e10e3eac5fa4e15
The non-{arti-,tor-} crates are:
```
./maint/list_crates | rg -v '^(tor|arti)'
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
```
We split them in the following categories:
* crates with no changes (no version bumps):
```
maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
oneshot-fused-workaround: No change.
slotmap-careful: No change.
fslock-guard: No change.
caret: No change.
retry-error: No change.
```
* crates that only have non-functional changes (bump the patch version):
- test-temp-dir
- equix
- fs-mistrust
- safelog
* crates where APIs were broken (bump minor):
- hashx (`RngCore` impl for `SipRand`)
The bumps from this commit were created using this script:
```
PATCH="
test-temp-dir
equix
fs-mistrust
safelog
"
for crate in $PATCH; do
cargo set-version --bump patch -p $crate;
done
MINOR="
hashx
"
for crate in $MINOR; do
cargo set-version --bump minor -p $crate;
done
```
fix compiling fs-misstrust on tvOS2025-03-26T15:27:09Zyaucpthomas.yau@kape.com2025-03-26T15:27:09Zurn:sha1:0a4c1e155a926da2c568c92ef9338fc8eefed6c4Bump minor version of fs-mistrust2025-02-07T10:47:05ZIan Jacksonijackson@chiark.greenend.org.uk2025-02-06T18:24:38Zurn:sha1:d69fe98f10d469028e1cbbd3dff4eabd3ba3d816
Fixes #1841.
fs-mistrust: bump minor version, and in-tree deps2025-02-06T18:17:34ZIan Jacksonijackson@chiark.greenend.org.uk2025-02-06T18:07:00Zurn:sha1:760400b3de12c5de121b6a7027a29ec78297c863
There are new features.
cargo set-version --offline --bump minor -p fs-mistrust
Actually, I have discovered by diffing that some methods now take
`&self` where previously they took `self`. This will need a further
bump to the fs-mistrust version and a fix to the changelog.
I will do that. Filed blocker ticket #1841 for it.
Upgrade to dirs 62025-02-05T16:43:18ZIan Jacksonijackson@chiark.greenend.org.uk2025-02-05T16:43:18Zurn:sha1:57c439c312b379a512c9b014ec3337df43759ef6
No code changes needed.
fix: fix typos2025-01-30T08:39:30ZDimitris Apostoloudimitris.apostolou@icloud.com2025-01-30T08:39:30Zurn:sha1:6371829c976f6a5b77d46bf977f369a915f2ced3fs-mistrust: document that follow_final_links is not insecure2025-01-28T15:55:13ZNick Mathewsonnickm@torproject.org2025-01-28T15:55:13Zurn:sha1:ba3b957961bd4dfb93bb471b3f1f99367c9b47e3
Since it makes an exception, we need to be clear about the
exceptions that it _doesn't_ make.
fs-mistrust: link to documentation about "obeying constraints"2025-01-28T15:32:02ZNick Mathewsonnickm@torproject.org2025-01-28T15:32:02Zurn:sha1:b0e2280a402c38f2c2af612c7c8d766be0293a6f
Since "obeying the constraints of a FileAccess" is a term of art,
this commit introduces links from the places where it is used
to the place where it is defined.
fs-mistrust: Fix test compilation on windows.2025-01-16T13:49:30ZNick Mathewsonnickm@torproject.org2025-01-16T13:42:19Zurn:sha1:c0c96ee76cf701335813dffbcd5b3dbe5b853890
`std::os::unix::fs::MetadataExt` was indeed the right trait to
import, but it doesn't exist on non-unix platforms.
This is another bugfix on !2707. It should retain the fix of !2717.
I've confirmed that it builds on Windows and passes tests on Linux
and Mac.
Fix: Tests fails to run on macos2025-01-16T10:37:15Zhhamudself@hamzahamud.com2025-01-16T10:37:15Zurn:sha1:00489651b88f88960a07e4234ceb5869b36f81c9