| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As suggested in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4222#note_3437129
|
| | | | |
| | | |
| | | |
| | | | |
Applies @opara's suggested rephrasing.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This makes the `DirMirror` return a dummy 500 response.
This enables us to (manually) verify that the new relay BEGIN_DIR stream
handler works as expected. We will of course need some automated e2e
tests too, but for the time being a manual test should do.
This will all be replaced by the real implementation, once that's ready
(TODO DIRMIRROR).
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Directory streams are accepted and turned into `DataStreams` by an
`arti-relay` task. The `DataStream`s are then passed to the `DirMirror`
for handling.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will be used shortly, as we need to spawn a `DirMirror::serve()`
task from `TorRelay::run()` for handling the incoming directory stream
requests.
The `DirMirror` is currently built from dummy data because there is no
config for it yet.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is just the skeleton of the task. The implementation will follow
later.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We need to return the "futures::Stream of Tor streams" from the CREATE
handler, because these need to be handled from `arti-relay`,
as per `doc/dev/notes/relay-streams.md`
This commit is intentionally (slightly) misformatted to make reviewing a
bit easier (the next commit will rustfmt everything).
Part of #2612
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The inner type is an eyesore, and doesn't really need to be exposed
outside of tor-proto (we might even replace it at some point).
|
| |/ / /
| | |
| | |
| | |
| | | |
This applies to relays too, not just onion services (we need to to
handle BEGIN/BEGIN_DIR/RESOLVE).
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Added #[cfg(...)] to remove the unnecessary #[allow(dead_code)]
See merge request tpo/core/arti!4152
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
tor-dirauth: Implement approximate IPv4 port summaries
See merge request tpo/core/arti!4212
|
| | | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4212#note_3436989
|
| | | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4212#note_3436987
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
In some sense this is a convenience wrapper around `push_ordered`,
but, really, it's the only nontrivial constructor that doesn't take an
iterator of individual port numbers.
|
| | | |
| | |
| | |
| | |
| | | |
This takes a PortRanges. We're going to introduce another function to
construct from an iterator.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The macro-generated code for `#[deftly(netdoc(flatten))]` relies on
this. The Default impl is genereated by the derive, but a generic
or handwritten `NetdocParseableFields` wouldn't work.
|
| |/ /
| |
| |
| |
| | |
Otherwise our MSRV compiler prints a warning, that this was an
unhandled Result.
|
| |\ \
| | |
| | |
| | |
| | | |
arti-relay: Remove `Arc` from around `KeyMgr`
See merge request tpo/core/arti!4221
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Fixes a TODO.
|
| | | |
| | |
| | |
| | | |
Now it can be used with `KeyMgr` and `&KeyMgr`, not only `Arc<KeyMgr>`.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
ci: replace image:docker:platform key with tag
See merge request tpo/core/arti!4216
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the recent update to gitlab-runner 19.2.0 has introduced
incompatibilities which make using this key with our podman backend
produce runner failures, see tpo/tpa/team#42731
this key was originally added as an attempt to coerce the container
runtime to always pull an amd64 image after it was observed that
sometimes, an i386 image was pulled instead
however, since switching registries from dockerhub to registry.tpo, this
can almost certainly never happen again since the base-images project
doesn't even build i386 containers
instead, just tag all jobs by default with the amd64 to ensure only such
runners can ever pick up those jobs
|
| |\ \
| | |
| | |
| | |
| | | |
ci: correct osxcross unattended build
See merge request tpo/core/arti!4219
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
tor-checkable: Rename Timebound to TimeBound and TimerangeBound to TimeRangeBound
See merge request tpo/core/arti!4215
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
For consistency with the TimeBound trait.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
For consistency with TimeRangeBounds (currently TimerangeBounds).
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-basic-utils: Improve docs for iter_join
See merge request tpo/core/arti!4213
|
| | | | | |
|
| | |/ / |
|