summaryrefslogtreecommitdiff
path: root/crates/arti
Commit message (Collapse)AuthorAgeFilesLines
...
* | arti: Use warn_report on anyhow::Error in onion_proxyNick Mathewson2023-12-121-4/+1
|/ | | | This was made possible by !1818.
* Merge branch 'todo_hsrproxy' into 'main'Nick Mathewson2023-12-111-1/+4
|\ | | | | | | | | Resolve several TODO HSS items in hsrproxy See merge request tpo/core/arti!1809
| * hsrproxy: Take nickname as an argument and pass it to forwarding functionNick Mathewson2023-12-071-1/+4
| | | | | | | | We'll use this for logging.
* | Merge branch 'onion-reconfigure' into 'main'Nick Mathewson2023-12-113-52/+210
|\ \ | |/ |/| | | | | | | | | arti: Reconfigure onion services as needed Closes #1089 See merge request tpo/core/arti!1798
| * Add a TODO HSS comment about Reconfigure.Ian Jackson2023-12-111-0/+1
| |
| * Reconfigure onion services when their configuration changes.Nick Mathewson2023-12-052-28/+20
| | | | | | | | Closes #1089.
| * arti: Make reconfiguration slightly more abstractNick Mathewson2023-12-052-24/+94
| | | | | | | | | | | | | | | | | | | | Now instead of having a hardwired list of of things to reconfigure, the watch_cfg module now has a vector of ReconfigurableModule. As noted in the documentation, I don't intend that this should be our final API here: It is deliberately not exposed. When we revisit the structure of `arti` more, we should probably do this differently.
| * arti: Backend support for reconfiguring onion proxies.Nick Mathewson2023-12-051-6/+101
| |
* | upgrade to toml 0.8.8Nick Mathewson2023-12-051-1/+1
|/
* Merge branch 'msrv-followup' into 'main'Nick Mathewson2023-12-041-16/+4
|\ | | | | | | | | Followups from MSRV 1.70 upgrade See merge request tpo/core/arti!1785
| * arti: rewrite ilog10_roundup using checked_ilog10.Nick Mathewson2023-11-301-16/+4
| |
* | Merge branch 'dirs' into 'main'gabi-2502023-12-041-2/+0
|\ \ | | | | | | | | | | | | Cleanup and clarification re cache_dir and state_dir (rename in tor_dirmgr) See merge request tpo/core/arti!1789
| * | arti-example-config: Do not claim that state_dir is unusedIan Jackson2023-12-041-2/+0
| | | | | | | | | | | | tor-ptmgr uses it, and the key manager too.
* | | Two more patchlevel bumpsNick Mathewson2023-12-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | These crates both depend on tor-error. Since tor-error got a patchlevel bump, they now depend on the new version, which means by our rules that _they_ get a patchlevel bump themselves. tor-geoip tor-rpcbase
* | | Bump minor versions in preparation for releaseNick Mathewson2023-12-041-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This crate is new, and gets a bump to 0.1.0. tor-log-ratelim This crate had a breaking change: tor-persist tor-llcrypto had a breaking change. These crates _are_ tor-llcrypto, or (transitively) depend on it. I am assuming that they all re-expose something from it in a way that matters: tor-llcrypto tor-bytes tor-hscrypto tor-socksproto tor-checkable tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-consdiff tor-netdir tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr tor-keymgr tor-hsclient tor-hsservice tor-hsrproxy arti-client arti-rpcserver arti-hyper
* | | Bump patchlevel versions in preparation for releaseNick Mathewson2023-12-041-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These crates had backward-compatible changes, and get a patchlevel bump only: fs-mistrust tor-error tor-config tor-rtcompat tor-rtmock This crate exposes no non-CLI APIs, and gets a patchlevel bump only: arti
* | | arti cfg: suppress a warningIan Jackson2023-12-041-0/+1
|/ / | | | | | | | | | | | | | | | | | | | | | | | | There is a TODO HSS for this. Fixes cargo check --workspace --all-targets producing warning: unused variable: `result` --> crates/arti/src/cfg.rs:1060:13 | 1060 | let result = file.resolve::<(TorClientConfig, ArtiConfig)>(); | ^^^^^^ help: if this is intentional, prefix it with an underscore: `_result` | = note: `#[warn(unused_variables)]` on by default
* / Move from `trust-dns` to `hickory`Andrew2023-11-302-8/+8
|/ | | | | | This is not a change of ownership but just rebranding. Signed-off-by: Andrew <[email protected]>
* Merge branch 'msrv-bump-1.70' into 'main'Ian Jackson2023-11-301-1/+1
|\ | | | | | | | | Increase our MSRV to 1.70 See merge request tpo/core/arti!1773
| * In every crate, change rust-version to 1.70.Nick Mathewson2023-11-281-1/+1
| |
* | Revert "hsrproxy: Temporarily change the format of ProxyRule."Nick Mathewson2023-11-292-9/+6
| | | | | | | | | | | | | | | | | | | | | | This reverts commit 21605d2c9e601c3a5099bfd8d8c887cbb3b36c0a. We're doing this because we wanted the configuration of proxy rules to be a 2-tuple, as in `[ "22", "127.0.0.1:22" ]`. But `config` couldn't handle that before, so we temporarily changed it to a string, as in "22 => 127.0.0.1:22". Closes #1058.
* | Require config ≥ 0.13.4Nick Mathewson2023-11-291-1/+1
| | | | | | | | | | | | | | This version of the config crate includes a fix for the issue (https://github.com/mehcode/config-rs/issues/464) that had prevented us from using the format we had wanted for our rproxy configuration.
* | make feature arti/experimental-api enable arti-client/experimental-apiJim Newsome2023-11-281-1/+1
|/
* Merge branch 'upgrades-20231115' into 'main'gabi-2502023-11-151-2/+2
|\ | | | | | | | | Upgrade a couple of dependencies See merge request tpo/core/arti!1736
| * Upgrade to itertools 0.12.0Nick Mathewson2023-11-151-2/+2
| |
* | Use "wrap_help" feature for clap.Nick Mathewson2023-11-151-1/+1
| |
* | Bump to clap 4 and resolve compiler errors.Nick Mathewson2023-11-152-4/+6
|/
* Patch version bumps in crates without breaking changesNick Mathewson2023-10-311-3/+3
| | | | | | | | | | | | | | | | | | ``` These crates have new APIs: tor-async-utils ADDED tor-config ADDED tor-hscrypto ADDED tor-netdoc ADDED, plus BREAKING-experimental. These crates have patch-level changes only: tor-netdir (bugfix only). (re-exposes netdoc) arti-rpcserver (tweaks only, uses nothing that broke.) arti 1.1.10, no stable public APIs. ```
* Minor version bumps in crates with breaking changes.Nick Mathewson2023-10-311-3/+3
| | | | | | | | | | | | | | | | | | | | | | ``` tor-basic-utils BREAKING tor-rtmock BREAKING. tor-cert BREAKING tor-cell BREAKING tor-proto BREAKING: re-exposes cell. (Also BREAKING-experimental) tor-chanmgr BREAKING: Re-exposes proto. tor-ptmgr BREAKING: re-exposes tor-chanmgr tor-guardmgr BREAKING: re-exposes proto. (Only for ClockSkew I think?) tor-circmgr BREAKING: re-exposes proto tor-dirclient BREAKING tor-hsclient BREAKING, re-exposes proto. tor-hsservice BREAKING, re-exposes proto. tor-hsrproxy BREAKING arti-client BREAKING: re-exposes proto. arti-hyper: BREAKING, re-exposes arti-client. tor-dirmgr Let's assume BREAKING, very high-level. tor-keymgr BREAKING, but experimental. ```
* Run "fixup-features" in preparation for release this week.Nick Mathewson2023-10-291-1/+1
|
* handle_socks_conn: update parameter name in doc commentJim Newsome2023-10-251-1/+1
|
* HSS: Do not drop ProxySet immediately - let HS services continue to run (fmt)Ian Jackson2023-10-191-2/+4
|
* HSS: Do not drop ProxySet immediately - let HS services continue to runIan Jackson2023-10-191-4/+19
| | | | Dropping the ProxySet causes all the services to terminate.
* HSS: Add many must_use annotationsIan Jackson2023-10-191-0/+2
|
* Merge branch 'generic-listen' into 'main'Nick Mathewson2023-10-163-55/+70
|\ | | | | | | | | arti, tor-config: Allow listening on generic addresses for SOCKS and DNS. See merge request tpo/core/arti!1613
| * Treat only EAFNOSUPPORT as a warningJani Monoses2023-09-262-8/+12
| |
| * Do not writelns in Display, undo localhost_port_legacy changes.Jani Monoses2023-09-251-1/+1
| |
| * Handle address already in useJani Monoses2023-09-222-2/+6
| |
| * arti, tor-config: Allow listening on generic addresses for SOCKS and DNS.Jani Monoses2023-09-223-56/+63
| |
* | Merge branch 'configure_onion_service_part2' into 'main'Nick Mathewson2023-10-112-29/+103
|\ \ | | | | | | | | | | | | Non-working attempt to test onion service configuration. See merge request tpo/core/arti!1640
| * | Use a less obtrustive sign to end the onion services config sectionNick Mathewson2023-10-112-7/+5
| | |
| * | 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
| |