| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
guardmgr needs to know how to parse Bridge lines into Bridge structs
so it needs to know about PTs specifically
|
| | |
| |
| |
| | |
I wanted this for testing. I think it's reasonable to promise this.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Make PtTargetSettings be Default.
No longer wrap it in Arc. We want to be able to update it here during
construction. If we want to save memory with copies of the same
bridge line, we should do this for the whole Bridge I think.
|
| | |
| |
| |
| | |
Spotted this in passing.
|
| |\ \
| | |
| | |
| | |
| | | |
Upgrade all fuzzers to newer libfuzzer-sys version.
See merge request tpo/core/arti!752
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Use hostname-validator crate for hostname validation
See merge request tpo/core/arti!739
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Include a HashSet variant that can be keyed on multiple keys.
See merge request tpo/core/arti!747
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Doing this lets us work with defaults and const generics.
|
| | | | |
| | | |
| | | |
| | | | |
This prevents an explosion if somebody has a key called "values".
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
It doesn't work for const generics yet, since they can't be repeated
in quite the same way.
|
| | | | |
| | | |
| | | |
| | | | |
Most of these were suggested by Ian
|
| | | | |
| | | |
| | | |
| | | | |
The `try_remove()` method, which we need, was introduced there.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The previous indentation was making it think that we had rust code
where none existed.
|
| | | | |
| | | |
| | | |
| | | | |
Also, document another invariant.
|
| | | | | |
|