| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Deferred formatting changes which would have obscured the commits they
were prompted by.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Provide an accessor for the HSDIR flag
* Provide a function for testing a relay for hsdir inclusion
* Provide an iterator on NetDir that returns the hsdirs
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Implement Netdir::compute_rings in terms of a new
HsDirRing::compute, that currently does nothing.
* Actually call Netdir::compute_rings (since now it doesn't panic).
* Make Netdir::compute_rings not be pub. We do this unconditionally,
rather than exposing the distinction between a netdir-without-hsdir
and a netdir-with-hsdir.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This already allows us to get rid of some duplication, and will be
useful more widely in a moment.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This will allow us to tell if we can reuse parts of a ring.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The file which contains this type is called hsdir_params.rs. We have
a general problem with slight confusion about when to includen "dir"
and when to include "ring".
Resolve this in favour of the rule now added to the module-level doc
comment.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These variables are going to be struct fields, which will sort of
enforce consistent naming. The struct fields are going to appear in a
moment. We'll call the fields "current" and "secondary" after the
naming in the test cases.
And import hsdir_params::HsRingParams, which we're going to make more
references to.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will enable us to pass these around more conveniently.
And make empty_from_params take an owned params, which it would like.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
We'll need this shortly.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Remove the return value, which was not used anywhere.
Also remove the code to calculate the return value.
* Take an Arc<NetDir> rather than a reference. We are going to want
this for HS support. This has no overall effect on the lifetime of
the4 Arc, which was owned at the one call site and then imediately
dropped.
* Change the documentation to explain what the function's role is in
the netdir API, rather than the fiddly details of what it actually
does internally. Relegate the latter to a code comment.
(When we have HS, this will do more, or, at least, make further
arrangements.)
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This was omitted in !1004. (Because this code isn't actually wired up
yet, it typechecked anyway. But we need to fix it.)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Locally, the only functional effect is that now we refuse to handle
non-whole-number-of-minutes lengths - but since the consensus
parameter can't represent those, there's no overall functional change.
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Rename DescEncNonce => HsDescEncNonce
See merge request tpo/core/arti!1014
|
| |/ / / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Rename hs-related identifiers to mirror those in the spec
Closes #746
See merge request tpo/core/arti!1011
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
As far as we can tell, this never existed.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
(I think it's okay to omit the Hs here, since this type is not
visible outside the hsdesc parsing code. I'll rename if others
disagree.)
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Generated with perl:
s/K([PS])_hs_intro_tid/K$1_hs_ipt_sid/g;
s/K([PS])_onion_ntor/K$1_ntor/g;
s/K([PS])_hs_intro_ntor/K$1_hss_ntor/g;
s/K([PS])_hs_desc_ephem/K$1_hss_desc_enc/g;
|
| |\ \
| | |
| | |
| | |
| | | |
Fix typo
See merge request tpo/core/arti!1010
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Create a macro to generate restricted variations on RelayMsg, ChanMsg.
Closes #525
See merge request tpo/core/arti!1008
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
We need to make sure any `#[cfg(feature=...)]` attributes are
applied not only to our variant declarations, but also to the
branches in the match statements that deal with them.
|
| | | |
| | |
| | |
| | | |
Thanks to rust-analyzer for making this simple.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This is the main implementation part of #525.
|
| | | |
| | |
| | |
| | |
| | | |
Previously, there were some unit variants, but that makes things
quite awkward for #525.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Doing this will make it much easier to implement a macro that
generates restricted instances of the Msg types (for #525).
The Body change is a breaking change. I don't think anybody else
implements Body, but in theory they could.
|
| |/ /
| |
| |
| |
| |
| |
| | |
These are generalizations of RelayCell and ChanCell respectively,
that allow using an arbitrary message type in place of the fully
general RelayMsg and ChanMsg types. Doing this is a prerequisite
for usefully implementing arti#525.
|
| |\ \
| | |
| | |
| | |
| | | |
Bump openssl-src to 1.1.1t, and make main CI pass.
See merge request tpo/core/arti!1009
|
| | | | |
|