| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-keymgr: Remove dead code
See merge request tpo/core/arti!2638
|
| | | | |
| | | |
| | | |
| | | | |
This doesn't seem to be needed anymore.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Otherwise, we get a dead code warning when the `ctor-keystore` feature
is disabled.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The fields are never read but need to be present in order for the
dummy `KeyMgrBuilder` to have the same interface as the real one.
(We could of course manually implement the builder, or let the dummy
`KeyMgrBuilder` impl diverge from the real one, but for now let's leave
this as-is and simply mark the fields as unused).
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
We no longer have any dummy keymgr operations that return an error,
so this error type is unused.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This is not used anywhere (or exported publicly).
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Begin implementation work on RPC connect points
See merge request tpo/core/arti!2629
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
("Server support" here means binding to a socket and reading a
cookie file.)
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
("Client support" here means connecting to a socket and reading a
cookie file.)
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
In particular, we only allow binding/connecting to localhost,
and we only support None auth for Unix connections.
|
| | | | |
| | | |
| | | |
| | | | |
The cookie authentication protocol will need these.
|
| | | | |
| | | |
| | | |
| | | | |
(Cookie authentication is described in rpc-cookie-sketch.md)
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
While doing so, tidy up the errors that we detect when parsing
a connect point, so that we can differentiate ones that indicate an
unsupported connect-point type.
This means that fewer types now implement Deserialize;
that's probably a good thing.
|
| | | | |
| | | |
| | | |
| | | | |
See doc/dev/rpc-book/src/rpc-connect-sketch.md for details.
|
| | | | |
| | | |
| | | |
| | | | |
We'll need this for implementing the connect point logic.
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-config-path: refactor to support a `CfgPathResolver`
See merge request tpo/core/arti!2615
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rather than using `arti_client::config::path_resolver()`, third-party
code can get the path resolver using `TorClientConfig`s
`AsRef<CfgPathResolver>` impl instead.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Also updated to use the `PATH_RESOLVER` resolver.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a big change across multiple crates since there isn't a good way
to break it up.
This changes the signature of `CfgPath::path` to:
```
pub fn path(&self, path_resolver: &CfgPathResolver) -> Result<PathBuf, CfgPathError> {
```
Making this change means that our global `CfgPathResolver` needs to be
stored in the 'arti-client' library instead of `tor-config-path`, and
must be passed through to anything that calls `path` to expand the
variables.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | | |
These tests were in the 'test_serde' module, which wasn't the right
place for them.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
tor-keymgr: Explain why the dummy keymgr is missing some functions.
Closes #1732
See merge request tpo/core/arti!2631
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This commit applies Diziet's suggestion from
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2631#note_3130234
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These are not actually needed anywhere.
In fact, it's a bad idea to have them in the first place (see the
comment from the dummy `KeyMgr` impl block).
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is based on a recent discussion with @Diziet on IRC.
For the full context, see the chat log attached to the ticket.
Closes #1732
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
arti-relay: remove runtime-related features
Closes #1744
See merge request tpo/core/arti!2634
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
In arti this option is just a convenience function to override the
configuration option, so we'll probably want to do the same thing.
|
| | | | | |
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
doc/dev/notes: keymgr-certificates: Add note about certificate management.
See merge request tpo/core/arti!2565
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is not necessarily set in stone, but it seems like a plausible way
of going about this.
|
