| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| |
| | |
Update versions for today's releases.
See merge request tpo/core/arti!1716
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
```
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.
```
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
```
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.
```
|
| |/
|
|
|
|
| |
I think retaining this lint even in tests is probably reasonable.
IptsPublisherView has interior mutability, so with this function
taking one, it won't ever need mut.
|
| |\
| |
| |
| |
| | |
timeout_track improvements
See merge request tpo/core/arti!1711
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
We have a profusion of similar methods with similar names and similar
documentation. Centralising the documentation in a trait is helpful.
This also means that callers can just naturally call `.update` rather
than needing to spell out `.update_abs` vs `.update_rel` etc.
|
| | |
| |
| |
| |
| | |
Clarify this in the update functions, and in the general discussion.
We don't want zero timeouts.
|
| |/
|
|
|
|
|
|
|
|
|
| |
Representing the supported HTYPEs as `HandshakeType`s instead of `u32`s
makes it more difficult to pass in wrong/invalid values to
`HsDescBuilder::create2_formats`.
This also fixes a descriptor publisher bug spotted by @jnewsome, where
the advertised CREATE2 HTYPEs included HTYPE `1`, which is actually
supposed to be a reserved value. The publisher now only advertises the
`NTOR` HTYPE (just like C Tor).
|
| |
|
|
|
|
| |
`Bug` wasn't necessarily the right error type here. Plus, with the new
error type adding new errors (i.e. `CertEncodeError` variants), is not a
breaking change.
|
| |
|
|
| |
blinded_id.
|
| |
|
|
|
|
|
|
|
|
| |
argument.
This will enable us to (eventually) the load the descriptor signing key
cert from the keystore (as opposed to always recomputing it when
building the `HsDesc`).
Part of #1048
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Enough of them have turned out to need to be async so far that I
don't think it's a great idea to commit to making any of them
not-async forever. Additionally, we've written the code that uses
these, and having them be async didn't seem to cause any major
trouble.
By the same "we may want to make these more complicated underneath"
argument, we should IMO leave them as fallible.
|
| | |
|
| | |
|
| |
|
|
|
| |
This particular public key is not stored in the keystore (though maybe
it should be).
|
| |
|
|
|
|
| |
The pattern was only supposed to match the 3 components of the time
period, separated by `_`, but not the leading `_`, which separates the
key name from its denotators.
|
| |
|
|
|
|
| |
We don't need to be logging the entire descriptor for each upload
attempt (logging descriptors immediately after they are generated should
be sufficient).
|
| |
|
|
|
|
| |
The message is supposed to print how many HSDirs the descriptor was
uploaded to (previously it was showing the
`<success_count>/<failure_count>` which is pretty unintuitive).
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Fix rustdoc link warnings/errors.
See merge request tpo/core/arti!1690
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
tor-keymgr: Auto-generate missing keys in descriptor publisher
See merge request tpo/core/arti!1688
|
| | | |
| | |
| | |
| | |
| | | |
This is not an error, it just means we need to wait until some IPTs are
established.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We don't need this helper anymore (we no longer map `None` to
`Err(MissingKey)`, because the new get-or-create functions don't return
an `Option`).
Also, the key lookups are going to look less uniform from now on
(because some will be auto-generated with `get_or_generate`, and others
with `get_or_generate_with_derived`).
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
necessary.
This auto-generates the blinded identity key and the descriptor signing
key (if they are missing).
|
| | |/
| |
| |
| | |
We're already fetching the descriptor signing key from the keystore.
|
| | |
| |
| |
| |
| |
| | |
The condition for logging the "generated a new identity.." message was
wrong (`generate_with_derive()` returns `Some(())` if it generated a new
key, and `None` if the key was already present).
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
| |
Downcasting is tricksy. We need to try the downcast on a
type-erased &IptEstablisher, not &Box<dyn Any>, and if we don't
dereference nothing tells us it's wrong since &Box<dyn Any>
also implements and we end up with &Box<dyn Any> as &dyn Any.
|
| | |
|
| |
|
|
|
|
| |
If it's due to lack of useable netdir, that's normal during startup,
so don't log it. Hopefully something else somewhere will log if a
consensus can't be obtained.
|
| | |
|
| |
|
|
| |
We want to pass one of these to info_report!, which demands HasKind.
|
| |
|
|
| |
If we don't do this then the manager won't ever select a replacement.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
tor-hsservice: ipt_mgr: Track notional estab started for faulty IPTs
See merge request tpo/core/arti!1686
|
| | | |
|
| | |
| |
| |
| | |
An IPT can go from Faulty to Good.
|
| | | |
|