| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| |
| |
| | |
Split OTLP exporter into separate crate.
Closes #2611
See merge request tpo/core/arti!4297
|
| | |
| |
| |
| | |
Mostly relating to typos and dependencies.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This contains configuration types that are shared between arti and
arti-rely.
|
| | |
| |
| |
| |
| |
| | |
This will allow this code to be shared between arti and arti-relay.
See: #2470
|
| | |
| |
| |
| |
| | |
This will allow this code to be shared between arti and arti-relay,
and will also likely be useful for others in the ecosystem.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Older versions of `h2` have a bug that causes empty HTTP/2 DATA frames
to be queued without limit if the streams are not read from quickly
enough.
According to the [hyper advisory]:
> To determine if vulnerable, all these things must be true:
>
> * You are using HTTP/2, either as a server or a client.
> * Your application does not fully drain incoming request
> or response bodies (for example, a proxy applying backpressure,
> or a client that delays reading the body).
> * The direct remote peer is malicious and intentionally
> sends large numbers of empty DATA frames.
To my knowledge, the only non-example crates that use `hyper` are `arti`
and `tor-dirserver`. Both of them run HTTP/1.1 servers, so I don't
believe we're affected by the `h2` bug.
[hyper advisory]: https://github.com/hyperium/hyper/security/advisories/GHSA-q83h-524g-xf6h
|
| |\ \
| | |
| | |
| | |
| | | |
Implement kludge to allow use of DirMgr as a backend for DirServer.
See merge request tpo/core/arti!4298
|
| | | |
| | |
| | |
| | | |
Part of #2657
|
| | |/
| |
| |
| |
| |
| |
| | |
This is part of #2657. The goal here is to use DirMgr as a
temporary backend for tor-dirserver, so that we can have a
sort-of-working directory cache that can be used for testing guards
before tor-dirserver is complete.
|
| |/
|
|
|
|
|
|
|
|
| |
This commit removes the getters in database.rs. If the overall
tor-netdoc refactoring has taught us something, then that the use of
getters can be quite annoying.
Therefore, this commit removes the getters and marks the respective
fields as pub. Given that these data types are pub(crate) only right
now, it does not matter a lot anyways.
|
| |\
| |
| |
| |
| | |
tor-proto: Upgrade statrs dev-dependency and remove default features
See merge request tpo/core/arti!4283
|
| | |
| |
| |
| |
| | |
This doesn't appear to be needed, and removes an nalgebra dev-dependency
which should help build times.
|
| | |
| |
| |
| |
| |
| | |
```bash
cargo upgrade --incompatible allow -p statrs
```
|
| |/
|
| |
This reverts merge request !4264
|
| |\
| |
| |
| |
| | |
Upgrade to weak-table 0.4.0
See merge request tpo/core/arti!4278
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Weak-table 0.4.0 replaces the backend with hashbrown for improved
performance and correctness. It adds a bunch of APIs for parity
with std::collections, and deprecates the risky `ahash` feature.
(I'm the maintainer at this point.)
|
| | | |
|
| | |
| |
| |
| | |
This is actually quite simple now.
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
```bash
cargo set-version --bump patch -p hashx
```
|
| |
|
|
|
|
| |
```bash
cargo set-version --bump patch -p arti
```
|
| |
|
|
|
|
|
| |
```bash
readarray -t bump < <(maint/list-crates | grep -P '^tor-|^arti-')
for crate in "${bump[@]}"; do cargo set-version --bump minor -p "${crate}"; done
```
|
| |
|
|
| |
Version 3.0.3 was yanked.
|
| |
|
|
|
|
| |
Fixes unsoundness for RUSTSEC-2026-0221.
https://rustsec.org/advisories/RUSTSEC-2026-0221.html
|
| |
|
|
|
|
|
|
|
| |
Give a tx to the descriptor task so it can request the keys when
building a new descriptor.
Implement the crypto task handling of that command channel.
Signed-off-by: David Goulet <[email protected]>
|
| |
|
|
| |
Signed-off-by: David Goulet <[email protected]>
|
| |
|
|
|
|
|
|
|
| |
This is the basics, with many TODO(relay), for a relay descriptor upload
task which uses tor-dirpublish::Publisher.
Future commits will implement the several todo!().
Signed-off-by: David Goulet <[email protected]>
|
| |
|
|
| |
We don't need to open-code this any more.
|
| |\
| |
| |
| |
| | |
arti-dirauth: Build an arti consensus method plugin binary, and implement list-methods
See merge request tpo/core/arti!4225
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
hashx: Update dynasmrt to 5.1.0
Closes #2637
See merge request tpo/core/arti!4232
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes a rust future-incompatibilities warning, which was caused by
the proc-macro-error2 crate.
The dynasmrt crate switched to a fork proc-macro-error3 to fix this.
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
To pick up this fix:
* BETA: Allow user-defined expansions whose definition is just
a string literal `"..." within `${concat }` and `$"..."`.
which I have just released.
|
| |/
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
