| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
These crates didn't have any changes until now, when I bumped
the versions of some other crates they depend on:
tor-consdiff
arti-hyper
arti-bench
arti-testing
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These crates have had small code changes, but no API additions:
tor-config
tor-socksproto
tor-cert
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
arti
tor-hsservice
tor-congestion
These crates have had API extensions:
fs-mistrust
tor-llcrypto
tor-bytes
tor-checkable
tor-linkspec
tor-netdoc
tor-persist
arti-client
|
| |
|
|
| |
This includes tor-cell, tor-proto, and tor-netdir.
|
| |
|
|
|
|
|
| |
Some code in our tests that worked fine with time 0.3.17 no
longer works with 0.3.19, despite the semver.
See https://github.com/time-rs/time/issues/552 for the upstream bug.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Remove the return value, which was not used anywhere.
Also remove the code to calculate the return value.
* Take an Arc<NetDir> rather than a reference. We are going to want
this for HS support. This has no overall effect on the lifetime of
the4 Arc, which was owned at the one call site and then imediately
dropped.
* Change the documentation to explain what the function's role is in
the netdir API, rather than the fiddly details of what it actually
does internally. Relegate the latter to a code comment.
(When we have HS, this will do more, or, at least, make further
arrangements.)
|
| |\
| |
| |
| |
| |
| |
| | |
Report causes of errors
Closes #680
See merge request tpo/core/arti!997
|
| | |
| |
| |
| | |
Split off for ease of review and possible rebase.
|
| | |
| |
| |
| | |
No functional change, just using the new idiom.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
These crates had API or behavior changes that may affect downstream
crates. Fortunately, they're all version 0.x, and don't need minor
bumps for this.
|
| |/
|
|
|
|
|
| |
These changes influence behavior, but not effect compatibility.
(If I messed up, and any crate except for `arti` has non-breaking
API changes, that's still fine, since they are all version
0.x.)
|
| |
|
|
|
| |
In both cases I think it's fine to panic; but it's best to do so
explicitly.
|
| |
|
|
|
| |
This panics on error, and we're fine with a panic on misbehavior in
tests.
|
| |
|
|
|
|
|
|
| |
This warning kind of snuck up on us! (See #748) For now, let's
disable it. (I've cleaned it up in a couple of examples, since
those are meant to be more idiomatic and user-facing.)
Closes #748.
|
| |
|
|
|
|
|
|
|
| |
This is in lieu of upgrading to the latest base64 crate, which has
a different API from the old one. Since we have to migrate either
way, we might as well use base64ct everywhere.
I don't think that most of these cases _require_ constant-time
base64, but it won't hurt.
|
| |\
| |
| |
| |
| | |
Add test lint blocks to all "mod test"
See merge request tpo/core/arti!937
|
| | |
| |
| |
| |
| | |
This is precisely the result of running the rune in
maint/adhoc-add-lint-blocks.
|
| | |
| |
| |
| |
| |
| |
| | |
This is the hunks from running the rune in maint/adhoc-add-lint-blocks
but which require some subsequent manual fixup: usually, deleting
now-superfluous outer allows, but in some cases manually putting back
lints that the adhoc script deleted.
|
| |/
|
|
|
| |
This commit introduces a consistency to the summary line of all
README.md files in each and every crate.
|
| |\
| |
| |
| |
| | |
A few spelling fixes for bridgedescmgr code
See merge request tpo/core/arti!925
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
dirauth: Remove Faravahar
See merge request tpo/core/arti!924
|
| | |/
| |
| |
| |
| |
| | |
See https://gitlab.torproject.org/tpo/core/tor/-/issues/40688
Signed-off-by: David Goulet <[email protected]>
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
We are rotating moria1's key due to a break-in few weeks ago. See
https://gitlab.torproject.org/tpo/core/tor/-/issues/40722 for more
details.
The original MR for C-tor (tor.git) done by Roger Dingledine, moria1's
operator, is here:
https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/662
Signed-off-by: David Goulet <[email protected]>
|
| | |
|
| |
|
|
|
| |
We made this job easy this time around: by incrementing our MSRV, we
have forced ourselves to do at least a minor bump everywhere.
|
| |
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/861#note_2856922
|
| | |
|
| |
|
|
| |
Fixes #630
|
| | |
|
| | |
|
| |
|
|
| |
BridgeConfig is itself an Arc now, so these are redundant.
|
| |\
| |
| |
| |
| | |
Fix warnings and breakage in nightly (2022-11-18 edition)
See merge request tpo/core/arti!872
|
| | |
| |
| |
| | |
These slipped in while nightly was broken.
|
| | |
| |
| |
| |
| | |
It looks like, despite a few false starts, they've got this warning
right; there weren't any false positives.
|
| |/ |
|
| |\
| |
| |
| |
| | |
dirmgr: Expopse DirMgrStore
See merge request tpo/core/arti!851
|
| | |
| |
| |
| |
| |
| |
| | |
Now the Store is constructed by arti_client, solving the problem
described here
https://gitlab.torproject.org/tpo/core/arti/-/issues/631#note_2853665
but in a different way.
|
| | |
| |
| |
| | |
rustfmt only, broken out to ease review.
|
| | |
| |
| |
| | |
We are going to change DirMgr's constructors to also take a DirMgrStore.
|
| | | |
|
| | |
| |
| |
| | |
This will allow us to get rid of a needless trait impl.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This seems tidier to me.
(It saved a lot of typing when I was trying to make some complicated
pub supertrait with sealed private supertrait, but apparently not
now.)
|
| |\|
| |
| |
| |
| | |
bridge descriptor dormancy: Define an enum and semantics
See merge request tpo/core/arti!845
|
| | |
| |
| |
| | |
But right now, don't do anything with it. That will come in a future MR.
|
| | | |
|
| | |
| |
| |
| | |
This is part of #630.
|
| |/ |
|
| |\
| |
| |
| |
| | |
Use ErrorKind::TorAccessFailed for misbehaving bridges
See merge request tpo/core/arti!842
|