| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Put a last_descriptor_expiry_including_slop into the IptSet.
Define who is responsible for which data.
The code at the sites that interacts with this needs to be bodged, to
make it still compile. That code is wrong, and the new API for
sharing the state doesn't exist yet.
|
| | | | | |
|
| | |/ /
|/| |
| | |
| | |
| | | |
This is going to be complicated enough we probably want it split out
of the publisher.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The descriptor publisher reactor was (incorrectly) only keeping track of
the "current" and "previous" time periods.
The reactor now maintains a list of all relevant time periods (obtained
from `Netdir::hs_all_time_periods`).
|
| | | |
| | |
| | |
| | |
| | | |
We don't need to build the `Descriptor` for each time period (it
contains TP-agnostic information).
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was based on the incorrect assumption there would be an external
source notifying the reactor of time period changes.
Time period changes will be handled in the consensus change handler of
the reactor.
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1545#note_2935668
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Version bumps in preparation for today's release
See merge request tpo/core/arti!1570
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This includes:
```
tor-basic-utils
caret
fs-mistrust
safelog
retry-error
tor-events
tor-units
tor-geoip
tor-rtcompat
tor-rpcbase
tor-protover
tor-socksproto
tor-checkable
tor-congestion
tor-persist
tor-circmgr
arti-rpcserver
arti-config
arti-hyper
arti-bench
arti-testing
tor-consdiff
```
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These are:
```
hashx
equix
tor-async-utils
tor-error
tor-config
tor-rtmock
tor-llcrypto
tor-bytes
tor-hscrypto
tor-hspow
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-chanmgr
tor-guardmgr
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
arti-client
arti
```
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These are:
```
tor-dirclient
tor-ptmgr
```
|
| | | |
| | |
| | |
| | |
| | | |
There's a complaint (seen in a CI build log) about over-eager iterator
item cloning. This is a perf complaint and not very relevant in tests.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Weirdly, rustdoc says
189 | /// TODO HSS surely this should be [`tor_proto::crypto::handshake::ntor::NtorSecretKey`] ?
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no item named `crypto` in module `tor_proto`
when it should probably complain the item is private.
Anyway, we can't link to it, so don't.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Run "fixup-features" in preparation for release.
See merge request tpo/core/arti!1569
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Upgrade a couple of dependencies for today's release.
See merge request tpo/core/arti!1566
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-hsservice: Fix broken doc links.
See merge request tpo/core/arti!1565
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
HS: Calculate descriptor sets to publish
See merge request tpo/core/arti!1559
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Apropos
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1559#note_2937979
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Apropos
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1559#note_2937978
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1559#note_2937976
If we're publishing with Durations, then we can use Instant at least
while everything remains in-core.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1559#note_2937976
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Apropos
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1559#note_2937975
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Apropos
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1559#note_2937973
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Apropos
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1559#note_2937971
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Apropos
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1559#note_2937970
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Apropos
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1559#note_2937969
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously there was no way to construct one of these during
descriptor generation, other than parsing.
A fairly simple builder seems right.
I felt the builder's setter functions for setting keys should be
named precisely after official key names. But the fields weren't,
so for now I have done some builder-level renaming.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
I'm going to want to reuse this, and it makes the code clearer at the
one call site already.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add the key material to `struct Ipt`, and add some code to generate
it.
However, this is all rather unsatisfactory. I got a bit lost in the
maze of 25519 key types, and neded up making a provisional dummy
`NtorKeyPair` type, which will need to be deleted again.
And, I wasn't able to generate K_hs_ipt_sid because of a mismatch in
Rng traits, which seems to be caused by us not properly wrapping up
the underlying crypto key types ?
At least the warts seem to be fairly localised.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Replace the publish_set closure (whose body is just TODOs right now)
with a proper function.
Change the type of the publication set to be Option<publish::IptSet>,
like the publisher now wants.
The value of the enum IptSetStatus is now no longer reified; instead,
these situations are the three branches of an if, and described in
comments.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previous code review comments suggested this variable would be better
with a name that more clearly distinguished it from (say) something
containing `Relay`s.
|