| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for p in `cat ../u`; do cargo set-version --locked --offline -p $p; done
where u contains
tor-basic-utils
tor-async-utils
tor-error
tor-config
tor-units
tor-geoip
tor-rtcompat
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-memquota
tor-llcrypto
tor-protover
tor-bytes
tor-hscrypto
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-relay-selection
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-hyper
|
| |
|
|
|
|
|
|
|
|
| |
for p in `cat ../u`; do maint/bump_nodep $p; git commit -a -m X; done
where u contains
hashx
equix
fs-mistrust
|
| |
|
|
| |
cargo set-version --locked --offline --bump patch -p arti
|
| |
|
|
| |
From fixup-features
|
| |
|
|
| |
Followup to !2109.
|
| |\
| |
| |
| |
| | |
arti-client: Make vanguards non-experimental.
See merge request tpo/core/arti!2109
|
| | |
| |
| |
| | |
For symmetry with remove_expired.
|
| | |
| |
| |
| | |
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2109#note_3024672
|
| | |
| |
| |
| |
| | |
`rotate_expired()` now only logs that it is rotating the vanguards if
some existing vanguards have actually expired.
|
| | |
| |
| |
| | |
Otherwise we end up logging that we're launching 0 circuits.
|
| | |
| |
| |
| |
| | |
We flush every time the vanguards may have changed, but we don't know
for sure if they did.
|
| | | |
|
| | |
| |
| |
| | |
This makes the vanguards feature non-experimental.
|
| |\ \
| |/
|/|
| |
| | |
Rename tor-memtrack to tor-memquota
See merge request tpo/core/arti!2105
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
properly report bootstrap readiness without cache
See merge request tpo/core/arti!2107
|
| | |/ |
|
| | |
| |
| |
| | |
The wanted_kind _does_ matter.
|
| | | |
|
| | |
| |
| |
| | |
Closes #1385
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
tor-circmgr: Make a fraction of preemptive HS circuits be STUB+.
Closes #1353
See merge request tpo/core/arti!2102
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2102#note_3024366
|
| | | |
| | |
| | |
| | | |
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2102#note_3024370
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Closes #1353
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
tor-rpcbase: simplify invoker_ent invocation (and infer the fn type)
Closes #1380
See merge request tpo/core/arti!2103
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2103#note_3024372
I overlooked this.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Previously, one of the macros was documented to accept
`(function_expr)`, but in fact it would only accept an identifier.
Now we *do* accept any expression.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
IMO if we want flags again in the future, we should probably pick a
syntax that doesn't involve such awkward patterns.
Perhaps `$expr $( , $( $flag )* )?`.
But I think we probably won't need that feature.
|
| | | |
| | |
| | |
| | |
| | | |
This renders the Update flag redundant.
Indeed, in this commit we mow ignore the flags.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This arm puts parens around its argument. But the other arm insists
on $func:ident, and also would capture any reasonable input.
This was probably something to do with the (func_expr) syntax. We
don't need to *fix* this macrology, because in a moment the whole
macro can be made to take $func:expr.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
The tests need to be updated now that the `VanguardMode` is read from
the config rather than the consensus.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As discussed on #tor-dev, I'm reintroducing `VanguardConfig` for now.
The `VanguardConfig` specifies what mode (full/lite/disabled) the
`VanguardMgr` should run in. We currently don't have a separate modes
for HS clients and HS services.
We shouldn't actually *need* a `VanguardConfig` at all, so this is just
a (hopefully!) short- or medium-term fix until we sort out #1382 (which
might involve making breaking changes to our `reconfigure()` APIs).
Closes #1272
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`VanguardParams` already contains the `vanguards_enabled` and
`vanguards_hs_service` `VanguardMode` params.
We still intend to abolish `VanguardConfig` in favour of deriving the
`VanguardMode` from the consensus params (#1382), but this is not the
right place for such a TODO.
|
| | | |
| | |
| | |
| | | |
None of these should be unused anymore.
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
Add LGPL-3.0 file
Closes #1375
See merge request tpo/core/arti!2094
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
This is the simplest way to get this included during "cargo publish",
which is necessary.
Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2094#note_3021187
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
tor_memtrack: Soup up DropBomb. make into its own module, and add more tests
Closes #1381
See merge request tpo/core/arti!2100
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
In addition to the in-module, switchable, tests, I have done an ad-hoc
test, removing the bulk of the accounting from
Participation::release_qty, it crashes in a test as expected.
|
| | | |
| | |
| | |
| | | |
We're going to want this in other places.
|
