| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This option affects all socks listeners, because:
- We don't have a convenient way to associate an option with each
port.
- The main purpose of having this option is as a switch in case we
discover a major problem with this code.
|
| |/
|
|
|
| |
(With no-default-features there is no runtime, and that still causes
a compiler error.)
|
| |
|
|
| |
Typos found with codespell
|
| | |
|
| |\
| |
| |
| |
| | |
Fix various typos
See merge request tpo/core/arti!3781
|
| | | |
|
| | |
| |
| |
| |
| | |
This is not exactly the most _urgent_ superuser functionality,
but it is probably the easiest to implement.
|
| | |
| |
| |
| |
| | |
When connection point provides superuser support, provide a
(currently inert) RpcSuperuser object to the RPC session.
|
| |/
|
|
|
| |
The Connection will know the options that the listener was created
with, as opposed to RpcMgr, which is the same for every listener.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Instead of doing this when we construct the listeners, we can do it
in a separate method, to simplify the return type.
|
| |
|
|
| |
Part of #2301.
|
| |
|
|
| |
Part of #2301.
|
| |\
| |
| |
| |
| |
| |
| | |
Mr 3616 rebased
Closes #1800
See merge request tpo/core/arti!3681
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
`clippy::collapsible_if` started triggering after bumping the MSRV to
1.88.
Since this triggers from a lot of places, and since there even are a
couple of instances where we explicitly allow `clippy::collapsible_ifs`,
I've opened #2342 for deciding what to do about it.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Uses the standard clap error messages, for example:
```text
$ cargo run -p arti -- proxy -p 123a
error: invalid value '123a' for '-p <PORT>': invalid digit found in string
For more information, try '--help'.
```
|
| | |
|
| |
|
|
|
|
| |
I'm undecided whether we want to keep `resolve_alternative_specs`
around, but it seems possible/likely that we'll want it in the future,
so I think we can keep it.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This is in preparation for removing the `listen_port` and `dns_port`
config options.
|
| | |
|
| |
|
|
| |
Use anyhow::Context to wrap error in useful message.
|
| |
|
|
| |
This resolves a newly-triggered lint.
|
| | |
|
| |
|
|
| |
This adds the lint to all our crates.
|
| |
|
|
|
|
|
| |
This isn't the long-term solution to error reporting and proxies,
but it is a start that we can work from.
Closes #2304.
|
| | |
|
| | |
|
| |
|
|
|
| |
This commit adds more documentation/examples for the prop330 syntax for
specifying directory authorities.
|
| |\
| |
| |
| |
| |
| |
| | |
Make all non-main APIs in arti experimental.
Closes #2284, #2299, and #419
See merge request tpo/core/arti!3586
|
| | | |
|
| | |
| |
| |
| |
| | |
Or rather, un-rename it. It's no longer a stable thing, so it
doesn't need to have this particular name.
|
| | |
| |
| |
| |
| |
| | |
Only fn main() is now pub when experimental-api is disabled.
Closes #2284.
|
| |/ |
|
| | |
|
| |
|
|
|
|
| |
Fixes bug introduced in 0cc367b9fef37c0f7d7f04d54c4687b27ef251d0.
Without this fix, RPC's get_proxy_info command wouldn't work.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This will make it easier to see the correspondence between CTorPaths
and the HS client/service key specifiers.
Initially, I was hoping this would make it easier to write a d-d macro
that automatically derives a `CTorPath` variant (e.g.
`HsClientDescEncKeypair`) from the KeySpecifier type name
(`HsClientDescEncKeypairSpecifier`), but alas, I don't think d-d can
"chop off" name suffixes ("Specifier", in this case).
`from_ctor_path()`/`ctor_path()` implementations for converting
`CTorPath`s to and from key specifiers.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Out of all the variants in `KeyPathError`, `Unrecognized` is the odd one
out, because unlike the others, which are mainly just lower level
parsing errors, `Unrecognized` is a higher level error constructed in
`KeyMgr::describe()`.
`KeyMgr::describe()` now returns an `Option`, because
* the failure to describe a user provided `KeyPath` may or may not be
an error
* previously, `describe()` would only ever return `Ok` or
`Err(KeyPathError::Unrecognized)`, which essentially a binary
result. Also, `describe()` would never return any of the other
`KeyPathError` kinds, which further suggests `Unrecognized`
doesn't belong there
The `Unrecognized` variant still exists, but is now part of
`KeystoreCorruptionError`, (returned from
`KeyMgr::validate_entry_integrity()`).
|
| |
|
|
| |
This folds `display_arti_entry()` into `display_entry()`.
|
| | |
|