| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the combination of a number of separate commits, many of which
were generated by seddery, and then rebased and squashed.
Cargo.toml
perl -i~ -pe 's{^derive-adhoc}{derive-deftly = "0.10"}' crates/*/Cargo.toml
(not regenerated during rebase)
update Cargo.lock
`cargo fetch` without --locked
(regenerated during rebase)
seddery
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{^use derive_adhoc}{use derive_deftly}'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bdefine_derive_adhoc\b}{define_derive_deftly}g'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bAdhoc\b}{Deftly}g if m{derive}'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\#\[derive_adhoc\b}{#[derive_deftly}g'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{use derive_adhoc}{use derive_deftly}'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bderive_adhoc\b}{derive_deftly_adhoc} if m{use.*deftly}'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bderive_adhoc!}{derive_deftly_adhoc!}'
(not regenerated during rebase)
Manually add `#[derive_deftly_adhoc]` where needed.
seddery
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\#\[adhoc\b}{#[deftly}g'
git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bderive_adhoc_template}{derive_deftly_template}'
(not regenerated during rebase)
Manually fix up an import
Manually update some builder attrs
Manually fix up tor_rtmock::time_core
This was missed in my seddery, due to me rebasing the branch and not
redoing the seddery.
|
| |
|
|
| |
Closes #1124.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We have Display/FromStr for AuthorizedClientConfig. We can't have
Display if it can containa PathBuf because a PathBuf may not have a
string representation.
If we want to support non-unicode in the future, we'll need an
escaping scheme and messing around with OsStr.
The config scheme here may not be the best, but right now I'm just
fixing uses of Path::display.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Remove a wanted blank line.
|
| |
|
|
|
| |
This is not implemented. It is better to have it commented out than
providing a knob that isn't connected to anything.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Part of #1210.
These values are not necessarily the cleverest possible, but they
match the C implementation. We can tune them if we need to.
|
| |
|
|
|
| |
This makes us more spec-conformant. See discussion at #1210
"question 3".
|
| | |
|
| |
|
|
|
| |
(These are about parameters and configuration for the introduction
point manager.)
|
| |
|
|
| |
We don't necessarily need to build this option at all.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This will mean if we refer to it in more places, we'll still only have
one place to change it.
|
| |
|
|
|
|
| |
It does not help that C tor has a set of parameters and a set of
configuration options with exactly the same names which configure
the same thing in two slightly different ways.
|
| |
|
|
| |
Closes #723.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This lets us write `[onion_services.allium_cepa]`.
|
| | |
|
| |
|
|
|
| |
We plan to ship without them at first, so we may as well remove
them.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
See thread at
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1599#note_2944510
for information about why `flatten` doesn't work here.
|
| |
|
|
| |
This matches our design.
|
| |
|
|
|
| |
Temporarily disable descriptor encryption configuration while we
figure out how it should work (see #1028)
|
| |
|
|
|
|
|
|
|
|
|
| |
This will enable the descriptor publisher to tell whether it needs to
update the descriptor.
When the publisher is notified of an `OnionServiceConfig` change, it
checks whether the `anonimity` or `encrypt_descriptor` fields have
changed. If they have, it rebuilds and republishes the descriptor
using the new values (note: the publisher changes will be implemented in
a future commit).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Note a few issues encountered while doing so.
|
| |
|
|
|
|
|
|
|
| |
For rate-limiting, we make it optional. If it isn't set, we don't
tell the intro to rate-limit.
We condense our two max-streams options into one. We had two
options here because we were looking for feature parity with C, but
I think I had misunderstood what C provides.
|
| | |
|
| | |
|
| |
|
|
| |
There are many TODOs and no tests, but it does compile.
|
|
|
Also, removed some older structures that don't make sense in the
current design.
Closes #970
|
