| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Switch to FixedCapacityVec from crates.io
See merge request tpo/core/arti!1563
|
| | | | | | |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
Rebased attempt to merge gsoc2023 examples
See merge request tpo/core/arti!1574
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We don't use "log" but some dependency of one of our examples does.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Chrono is unmaintained, I think, and uses a version of `time` that
cargo-audit doesn't like.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Part of a solution for cargo-audit.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We have automatic support for "OR", but we can't do anything
automated with AND, since the intersection of licenses can get
complicated. So we just have to authorize the specific combinations
that exist. This is used by matchit, which is used in the gotlou's
examples.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With permission from gotlou; see discussion at
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1556
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
I have no idea why these became necessary.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
tor-hsservice: PublishIptSet reorg and new publisher/manager intermediary API
See merge request tpo/core/arti!1575
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
tor-hsservice: Replace {current,previous}_period with a list of time periods.
See merge request tpo/core/arti!1564
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
(Only bump openssl-sys to 0.9.92; I'm having an issue with 0.9.93.)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
```
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Fix some rustdoc and clippy warnings
See merge request tpo/core/arti!1572
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
changelog: Remove reference to TROVE-2023-003
See merge request tpo/core/arti!1571
|
| | |/ /
| | |
| | |
| | | |
It turns out we aren't affected in Arti; our arrays were bounds-checked.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Run "fixup-features" in preparation for release.
See merge request tpo/core/arti!1569
|
| | | | |
|