summaryrefslogtreecommitdiff
path: root/crates/arti
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Improve test fn documentation even more.Ian Jackson2023-10-101-2/+2
| | |
| * | arti::cfg: tweak narrow() test fn to be more useful.Nick Mathewson2023-10-102-13/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | It still matches the start pattern in the same way, but it takes the _next_ match of the end pattern after the start pattern, and it allows the end pattern to be absent. This will make the bridge tests a little more robust, and let the onion service tests stop saying BEGIN and END.
| * | hsrproxy: Temporarily change the format of ProxyRule.Nick Mathewson2023-10-101-5/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | Since config-rs has a bug breaking its support for nested arrays (see discussion at !1640), we're temporarily changing the format to a single string with a "=>" in the middle. I've opened #1058 to put things back as they were once config-rs is fixed.
| * | Non-working attempt to test onion service configuration.Nick Mathewson2023-10-032-22/+76
| | | | | | | | | | | | | | | | | | | | | The problem here is that, for some reason, the proxy_rule configuration doesn't actually work. I suspect a bug in Flatten, since the same configuration works fine if you pass it to the hsrproxy config directly.
| * | arti: Try to document some test helpers.Nick Mathewson2023-10-031-1/+18
| | |
* | | arti: Lower some over-broad #allows in onion_proxy.rsNick Mathewson2023-10-051-4/+2
| | |
* | | arti: Actually launch the onion service code.Nick Mathewson2023-10-051-0/+9
| | |
* | | arti: functions to configure and launch actual onion service proxies.Nick Mathewson2023-10-051-3/+82
|/ /
* | Add/clarify comments about name duplication.Nick Mathewson2023-10-031-1/+1
| |
* | arti: make sure nicknames in builders match (or are absent)Nick Mathewson2023-10-031-7/+16
| |
* | arti: Fix up the example config to use the new onion_services format.Nick Mathewson2023-10-031-6/+5
| |
* | arti: in onion service builder, rename "transports" to "services"Nick Mathewson2023-10-031-4/+3
| | | | | | | | The old name was a copy-paste error.
* | arti: Make onion_services serialize as a map.Nick Mathewson2023-10-032-1/+42
| | | | | | | | This lets us write `[onion_services.allium_cepa]`.
* | arti: Make onion_service configuration option pluralNick Mathewson2023-10-032-5/+5
| |
* | hss: Rename the "name" config field to "nickname".Nick Mathewson2023-10-031-1/+1
| |
* | Note that we *do* need to actually test the onion service config.Ian Jackson2023-10-031-1/+1
| |
* | arti: Add a list of [[onion_service]]s to the config.Nick Mathewson2023-10-033-2/+91
| | | | | | | | There are no tests for parsing it yet.
* | arti: add a set of OnionServiceProxyConfig types.Nick Mathewson2023-10-033-1/+63
| | | | | | | | | | These don't yet attach to the rest of the ArtiConfig, or actually launch any onion services, but they're a start.
* | Patchlevel bumps to crates whose dependencies just changed.Nick Mathewson2023-10-021-2/+2
| | | | | | | | (The only change in these crates is that their dependencies changed.)
* | Patchlevel bumps, with dependents affected.Nick Mathewson2023-10-021-4/+4
|/
* Add cognitive-complexity exceptions for clippy.Nick Mathewson2023-09-051-0/+2
| | | | I have no idea why these became necessary.
* Merge branch 'bumps' into 'main'arti-v1.1.8Ian Jackson2023-09-051-4/+4
|\ | | | | | | | | Version bumps in preparation for today's release See merge request tpo/core/arti!1570
| * Update patchlevel for crates with nontrivial changes.Nick Mathewson2023-09-051-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These are: ``` hashx equix tor-async-utils tor-error tor-config tor-rtmock tor-llcrypto tor-bytes tor-hscrypto tor-hspow tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-netdir tor-chanmgr tor-guardmgr tor-dirmgr tor-keymgr tor-hsclient tor-hsservice arti-client arti ```
* | arti tests: Suppress a lint locallyIan Jackson2023-09-051-1/+2
|/ | | | | There's a complaint (seen in a CI build log) about over-eager iterator item cloning. This is a perf complaint and not very relevant in tests.
* Bump to trust-dns-proto 0.23.0Nick Mathewson2023-09-052-5/+5
|
* Upgrade to visibility 0.1.0Nick Mathewson2023-09-051-1/+1
|
* Run maint/add_warning to add lint block everywhereIan Jackson2023-08-232-0/+2
|
* arti::cfg tests: Use fold to make nightly clippy happierNick Mathewson2023-08-221-4/+5
|
* tor-error, arti: Bump backtrace to 0.3.68.Gabriela Moldovan2023-08-151-1/+1
| | | | | | | | Previously we were using backtrace 0.3.39, which has a [bug] that causes it to segault in some circumstances. I experienced this bug while trying to fix the minimal-versions build in !1508. [bug]: https://github.com/rust-lang/backtrace-rs/issues/267
* arti: Use ConfigurationSources::try_from_cmdlineIan Jackson2023-08-071-3/+3
| | | | | | | | | | This will allow us to proceed if * the default config file locations can't be established (eg due to failure of the `directories` crate), but * configuration files are explicitly specified, so the defaults wouldn't be used
* arti: Add context to default config files error messageIan Jackson2023-08-071-1/+1
| | | | | | | | | | | | Improves the error mesage in #989 somewhat. Before: target/debug/arti: error: Can't construct project directories to resolve a path element After: target/debug/arti: error: identify default config file locations: Can't construct project directories to resolve a path element
* Run add_warnings on all files.Nick Mathewson2023-08-042-4/+4
|
* Increment patchlevel versions of crates with minor changesNick Mathewson2023-08-011-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These crates are at version 0.x.y, so we don't need to distinguish new-feature changes from other changes: ``` tor-basic-utils fs-mistrust tor-error tor-geoip tor-checkable tor-linkspec tor-netdoc tor-netdir tor-persist tor-ptmgr tor-hsservice ``` This crate has a breaking change, but only when the semver-breaking feature `experimental-api` is enabled: ``` tor-config ``` This crate is at version 1.x.y, but has no new public APIs, and therefore does not need a minor version bump: ``` arti ```
* Update minor versions on crates that have had breaking changesNick Mathewson2023-08-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API.
* Fix typosDimitris Apostolou2023-07-222-10/+10
|
* Bump requirement to rlimit 0.10.1Nick Mathewson2023-07-201-1/+1
| | | | | | There was a bug in 0.10.0 that broke MacOS. Part of #963.
* Upgrade to latest rlimit.Nick Mathewson2023-07-171-1/+1
|
* arti cfg tests: Add keystore to example config.Gabriela Moldovan2023-07-132-14/+22
| | | | Closes #939
* arti config: Remove extraneous whitespace.Gabriela Moldovan2023-07-131-5/+5
|
* arti-client: Use the config struct from tor-keymgr.Gabriela Moldovan2023-07-131-1/+1
|
* Run maint/add_warning to actually apply new lint allowsIan Jackson2023-07-104-0/+4
|
* Update documentation regarding the `onion-service-client` featureKunal Mehta2023-07-071-2/+3
| | | | | It is no longer experimental, but still not rated for security-sensitive usage per <https://blog.torproject.org/arti_116_released/>.
* Merge branch 'feat' into 'main'Nick Mathewson2023-07-071-1/+10
|\ | | | | | | | | | | | | arti: Build with HS client support by default Closes #948 See merge request tpo/core/arti!1382
| * arti: Build with HS client support by defaultIan Jackson2023-07-071-0/+1
| | | | | | | | Fixes #948
| * arti Cargo.tomL: wrap default features listIan Jackson2023-07-071-1/+9
| |
* | Throughout: Use *_report!() macros for reporting Errors.Nick Mathewson2023-07-076-17/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Run add_warning to remove `missing_panics_doc` deny.Nick Mathewson2023-07-062-2/+0
|/ | | | Closes #950.
* Merge branch 'log_precision' into 'main'Nick Mathewson2023-07-065-4/+381
|\ | | | | | | | | | | | | arti: Add a `logging.time_granularity` option with 1s default. Closes #551 See merge request tpo/core/arti!1376
| * arti: comments about catch_unwindNick Mathewson2023-07-061-0/+9
| |
| * time_granularity: Make sure formatter can't panicNick Mathewson2023-07-061-17/+49
| | | | | | | | | | | | I was unable to assure myself that tracing_subscriber could withstand a panicking Timer, so instead I'm trying to make sure our own LogTimer can't panic.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-28 22:21:42 +0000