mirrors/arti.git/crates/arti/src/dns.rs, branch arti-v1.8.0

Add a notion of isolation strong enough to enable long-lived circuits.

2025-11-12T15:00:55Z

Part of prop368.

all: replace all uses of `futures::task::SpawnExt` with `tor_rtcompat::SpawnExt`

2025-11-05T03:39:55Z

*: suppress cognitive_complexity warnings from nightly

2025-05-29T14:21:17Z

Apparently clippy nightly is better (or worse?) about detecting complex functions than before, so I'm suppressing these warnings where they occur. I have mixed feelings about these warnings: On the plus side, they really do help to detect functions that are twistier than they need to be. On the minus side, they get confused by tracing macros, and the "allows" do pile up. But on the plus side, those "allows" do provide a way to find functions that need to be refactored, and they are never uglier than the functions they decorate.

arti: Warn when listening on non-loopback addresses.

2024-09-25T16:28:47Z

Move from `trust-dns` to `hickory`

2023-11-30T17:05:13Z

This is not a change of ownership but just rebranding. Signed-off-by: Andrew

Treat only EAFNOSUPPORT as a warning

2023-09-26T08:16:39Z

Handle address already in use

2023-09-22T16:26:45Z

arti, tor-config: Allow listening on generic addresses for SOCKS and DNS.

2023-09-22T16:19:40Z

Bump to trust-dns-proto 0.23.0

2023-09-05T12:05:45Z

Throughout: Use *_report!() macros for reporting Errors.

2023-07-07T17:00:21Z

I identified the cases to replace by searching for the string `.report()`. There are a few that I didn't change: * A couple of cases that used anyhow::Error, * One case that reported two Errors. * Two cases in `tor_hsclient::err` that just did `error!("Bug: {}")`. I have also not audited the cases in `tor-hsclient` where we're using `tor_error::Report` manually. Nonetheless, closes #949.