| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will be used for the `vanguard.mode` config option. The
`VanguardMode` corresponding to the `"auto"` variant will depend
on whether the `vanguards` feature is enabled: if the feature is
enabled, it is mapped to `VanguardMode::Lite`, and
`VanguardMode::Disabled` otherwise.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We want to export the `VanguardConfig` even if the `vanguards` feature
is disabled (we will need to unconditionally include it in the arti
config).
Note that if `vanguards` are disabled, the `VanguardMode` from the
`VanguardConfig` can only be `Dsiabled`.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is already exported via the `pub mod vanguards` module, so there is
no need to export it from the top-level too. This *is* a breaking change,
but the downstream fix is trivial (and the type should never have been
exported directly from `arti_client::config` in the first place).
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-keymgr: Add script for generating test key files.
See merge request tpo/core/arti!2121
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The keys generated in this commit are reproducible using the
`maint/keygen-openssh-test/generate` script.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The README now applies to the generate.sh script too, so it had to be
updated.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit contains a new set of `tor-keymgr/testdata` keys,
generated using ./maint/keygen-openssh-test/generate.sh`.
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2121#note_3025369
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
`tor-keymgr/testdata` contains a bunch of OpenSSH keys used for testing.
I meant to share the script I generated them with, but somehow never got
around to it.
Note: the OpenSSH keys generated by this script are going to look
slightly different than the ones that are checked into the repo. This is
because some of those original key files were generated ad-hoc (I
manually modified them a while ago, but I forgot exactly how
|
| |\ \ \ \
| | |/ /
| |/| |
| | | |
| | | | |
Add ticket links to relay-sketch.md
See merge request tpo/core/arti!2176
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
dirauth: Add new faravahar authority
See merge request tpo/core/arti!2175
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Related to C-tor MR:
https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/819
Signed-off-by: David Goulet <[email protected]>
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Update the location of the code of conduct.
See merge request tpo/core/arti!2173
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
relay-sketch: Incorporate notes from Lisbon meeting.
See merge request tpo/core/arti!2174
|
| |/ / / |
|
| |\ \ \
| | |/
| |/|
| | |
| | | |
Tidy up the ChannelSender::poll_ready inherent method
See merge request tpo/core/arti!2171
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This is where it belongs.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This makes this available for any Sink + Unpin. Which we want because
we're about to wrap our ChannelSender in a Sink wrapper.
It's in the wrong place now; we'll move it in a moment.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This would otherwise shadow the poll_ready method, which is
confusing.
Also this paves the way for making it available for any
Sink + Unpin.
Improve the docs somewhat to explain what this thing actually is.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I think this error was in fact always Error::CircuitClosed because it
came from ChannelClosed.into(). Anyway, we shouldn't squash it.
Now this function has semantics identical to Sink::poll_ready, just a
slightly different signature.
|
| | | |
| | |
| | |
| | | |
Make it clear we're discarding `()`, not an actual value.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We're going to change this function, but first we are going to make
its behaviour identical to Sink::poll_ready.
This avoids open-coding the call to poll_read on cell_tx.
The error handling is still strange. We'll fix that in a moment.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
proto: Make DataWriter::close actually do something.
Closes #1368
See merge request tpo/core/arti!2170
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This test verifies that when we invoke the code to close a stream,
an END message is actually sent.
The test comes in two versions:
* `drop_stream` closes the stream by dropping it. It currently
passes on main.
* `close_stream` closes the stream by running `AsyncWriteExt::close`
on the writer. It is a regression test for #1368. It currently
fails on main.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In particular, clarify that dropping the DataWriter on its own does
nothing unless the DataReader is also dropped.
Related to #1368.
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously we had a bug where `<DataWriter as AsyncWrite>::close`
(or `shutdown` in tokio-land) would not actually have any effect.
It _would_ drop the `StreamTarget` held by the `DataWriter`, but
since the `DataReader` also held a `StreamTarget`, the
MPSC channel would not get closed, and the circuit reactor would
not realize that the stream wanted to shut down.
Now we use `mpsc::Sender::close_channel` to make our closes
effectual.
Closes #1368.
Additionally, we fix a bug where `poll_close()` never actually did
anything if the buffer had nothing in it when it was called.
Previously, `poll_flush_impl()` would exit immediately if it had no
data to flush. That isn't what we want when we are closing!
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
mypy: Enable strict mode
See merge request tpo/core/arti!2169
|
| | | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2169#note_3033481
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Consultation with a nearby Python expert, on another topic, revealed
that without --strict, mypy turns most of its stuff off by default.
Sadly (?) this bureaucracy didn't find any bugs.
|
| | | | |
|