| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
CfgPath: Add support for ${PROGRAM_DIR}.
Closes #586
See merge request tpo/core/arti!760
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`${PROGRAM_DIR}` expands to the equivalent of
`std::env::current_exe().parent()`, with appropriate unwrapping and
conversions.
It is expected to be useful for finding the locations of pluggable
transports in some kinds of bundles.
Closes #586.
|
| |\ \
| | |
| | |
| | |
| | | |
Make cargo-sort stop complaining
See merge request tpo/core/arti!763
|
| |/ / |
|
| |\ \
| |/
|/|
| |
| | |
Fixed grammar mistake
See merge request tpo/core/arti!762
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
tor-linkspec: Refactor HasAddrs, HasChanMethods, and Owned* objects
See merge request tpo/core/arti!758
|
| | | |
|
| | |
| |
| |
| | |
All the other users of HasAddrs are correct.
|
| | |
| |
| |
| | |
These are now builders.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This will become the preferred way to make one of these objects, and
insulate us against future API changes.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HasAddr used to mean "Here are addresses that I have, at which I can
be contacted." But "Where (and how) can I be contacted?" is now a
question for HasChannelMethod to answer.
(We still need to have "HasAddr", though, so we can answer things
like "what country is this relay in" and "are these relays in the
same /8?")
So this commit introduces:
* A new trait for adding an implementation of HasChannelMethod in
terms of HasAddr.
* A requirement on ChanTarget that it needs to implement
HasChannelMethod.
There is some temporary breakage here, marked with "TODO pt-client",
that I'll fix later in this branch.
|
| |\
| |
| |
| |
| | |
Start implementing more data structures to hold Bridge descriptors.
See merge request tpo/core/arti!755
|
| | | |
|
| | |
| |
| |
| | |
See comment for an explanation of the next issue here.
|
| | |
| |
| |
| |
| |
| | |
Also add a BridgeRelayWithDesc type (name tbd) to guarantee that
a bridge relay really does have a known descriptor before you
try to build a circuit with it.
|
| | |
| |
| |
| |
| | |
These are needed to actually be able to build circuits through
a bridge.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This is the one we'll actually use to connect to bridges. It
has a `Bridge` line, and an optional `BridgeDesc`.
Maybe this will turn into a `BridgeRelay<'a>` by analogy to `Relay`
some time; I'm not sure.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
BridgeDesc is a separate type to make sure that we do not confuse
bridges' descriptors with the descriptors from other routers down
the road. (Bridges' descriptors need to be used differently, and
treated as more private.)
With this code, BridgerDescList is now just an alias for
`ByRelayIds<BridgeDesc>`, which is pretty keen.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
To implement a reasonable RsaIdentity accessor, we have to
store the RsaIdentity in the RouterDesc, or else we'd have to
recalculate it using SHA1 and DER every time.
The Ed25519 identity is hidden inside the identity cert, but it's
safe to get a reference to it.
|
| |\ \
| | |
| | |
| | |
| | | |
Temporarily suppress a false positive from nightly.
See merge request tpo/core/arti!754
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Nightly rust gives a warning about this "pub use", but the warning
is a false positive. Since it doesn't seem to be going away in a
hurry, let's suppress it for now.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Shadow ci
Closes #174
See merge request tpo/core/arti!634
|
| |/ / /
| | |
| | |
| | | |
Fixes https://gitlab.torproject.org/tpo/core/arti/-/issues/174
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
remove manual limitation of coredump size
Closes #598
See merge request tpo/core/arti!757
|
| |/ / /
| | |
| | |
| | | |
it's already disabled by secmem_proc
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
feature-gate some functions requiring PreferredRuntime in arti_client
Closes #597
See merge request tpo/core/arti!756
|
| |/ / |
|
| |\ \
| |/
|/|
| |
| | |
Implement ByRelayIds<H : HasRelayIds>
See merge request tpo/core/arti!753
|
| | |
| |
| |
| |
| | |
For whatever reason, rustdoc didn't like these multiline strings
in `doc` attributes.
|
| | |
| |
| |
| |
| | |
This is based on the type generated with n_key_set, with a
couple of extra methods to take advantage of RelayId and RelayIdRef.
|
| | |
| |
| |
| | |
Otherwise, there is a parsing ambiguity. :(
|
| | |
| |
| |
| |
| | |
Previously we used `<T>` in a bunch of places. But that fails
if you try to declare `T` as a parameter on the structure itself.
|
| | |
| |
| |
| | |
I am finding as I use this that I want a variant that can't panic.
|
| |/ |
|
| |\
| |
| |
| |
| | |
Parse (and format) bridge lines
See merge request tpo/core/arti!745
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Include the offending word in all the applicable errors.
Always print it with {word:?}.
As a consequence, there are no From impls any more and error
generation/conversion is by hand in all cases.
Clarify InvalidPtOrAddr vs InvalidIAddrorPt, and don't make the
attempted parse be a source error for those.
Where we still have source errors, don't print them in Display.
|
| | | |
|
| | |
| |
| |
| |
| | |
This is not perfect but it at least ensures that our own parsing and
printing code works correctly with all the values we accept.
|
| | |
| |
| |
| |
| |
| | |
It has its own error type PtTargetInvalidSetting.
In check_doc_features, adjust suppression to new code.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This is going to appear in config files etc. We don't want the user
to have to type "<none>" in a bridge line.
|