| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
| |
These are not "must fix before releasing onion services".
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Resolve Arti crate todos, redux
See merge request tpo/core/arti!1833
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
(We can't use `visibility::make(pub)` or `visible` here.
Try it yourself if you don't believe me!)
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
The TODO HSS in question is about our inability to serialize every
possible builder. The right answer here might be to use something
else instead of a ListBuilder.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The most logical way to do this was to change the "List" type
to a HashMap, and add a build function to the ListBuilder.
This change additionally renames:
OnionServiceProxyConfig{List=>Map}
NamedProxyMap => ProxyBuilderMap
(We now have two kinds of map, and this name change will clarify the
distinction.)
|
| | |
| |
| |
| |
| |
| |
| | |
IIUC, there will never be a Some(InNew) entry here, since we will
never have an onion service be configured by default. Instead we
test this kind of configuration by having commented-out options that
we uncomment as needed.
|
| | |
| |
| |
| |
| |
| | |
It's correct that we'd like someday for the `arti` crate APIs to
allow all the different modes supported by `Reconfigure` enum;
this is #1156, and it does not block an HSS release.
|
| | | |
|
| | |
| |
| |
| | |
(This was solved with !1798)
|
| | | |
|
| | |
| |
| |
| | |
Part of #1071
|
| |/
|
|
| |
This was made possible by !1818.
|
| |\
| |
| |
| |
| | |
Resolve several TODO HSS items in hsrproxy
See merge request tpo/core/arti!1809
|
| | |
| |
| |
| | |
We'll use this for logging.
|
| | | |
|
| | |
| |
| |
| | |
Closes #1089.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |/ |
|
| |\
| |
| |
| |
| | |
Followups from MSRV 1.70 upgrade
See merge request tpo/core/arti!1785
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Cleanup and clarification re cache_dir and state_dir (rename in tor_dirmgr)
See merge request tpo/core/arti!1789
|
| | | |
| | |
| | |
| | | |
tor-ptmgr uses it, and the key manager too.
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |/
|
|
|
|
| |
This is not a change of ownership but just rebranding.
Signed-off-by: Andrew <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Dropping the ProxySet causes all the services to terminate.
|
| | |
|
| |\
| |
| |
| |
| | |
arti, tor-config: Allow listening on generic addresses for SOCKS and DNS.
See merge request tpo/core/arti!1613
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Non-working attempt to test onion service configuration.
See merge request tpo/core/arti!1640
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|