| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With his commit, our SOCKS ports now accept both SOCKS
and HTTP CONNECT requests, per proposal 365.
There are still some infelicities, marked with
"XXXX" or "TODO".
I've tested this with curl, though, and it works. :)
Typo-fixes-by: Gabriela Moldovan <[email protected]>
|
| | |
| |
| |
| |
| | |
This will let us speak HTTP CONNECT as well; there is a stub
for initiating an http proxy.
|
| | | |
|
| | |
| |
| |
| | |
This will let us implement bilingual HTTP proxies.
|
| | |
| |
| |
| | |
This is _all_ renaming and comment adjustments.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
We want to abstract every part of this code that knows that it's
speaking SOCKS, so that we can in turn add a new proxy type.
Note that several methods and types here have names that are no
longer appropriate for their functionality. I'll revise those in a
later commit.
|
| | |
| |
| |
| |
| | |
(I'm not sure why this wasn't already done, but let's do it as a
separate MR.)
|
| | |
| |
| |
| | |
I'm about to add another proxy type.
|
| |\ \
| | |
| | |
| | |
| | | |
arti: Mark restricted-discovery as non-experimental
See merge request tpo/core/arti!3384
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| | |
As per the team decision from the 14 Oct Arti sync.
|
| |/ |
|
| |
|
|
| |
This is flaky, ignoring until #1607 is fixed.
|
| |\
| |
| |
| |
| |
| |
| | |
arti config: Fix flaky watch_single_file test.
Closes #1607
See merge request tpo/core/arti!2503
|
| | |
| |
| |
| | |
Thanks to gabi for the suggestion.
|
| | |
| |
| |
| | |
Fixes: #1607
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
and `keystores`
|
| | |
| |
| |
| | |
The function now returns `Result<Vec<InvalidKeystoreEntry<'a>>>`
|
| | |
| |
| |
| |
| |
| |
| | |
Add a check in `run_check_integrity` to verify that the `expired_entries`
collection is empty after processing all registered keystores. This should
always be true, as all expired entries are expected to be removed during
iteration. If not, it indicates a bug.
|
| | |
| |
| |
| |
| | |
Replace raw tuples with named structs to reduce type complexity and improve
code clarity and maintainability.
|
| | | |
|
| | |
| |
| |
| | |
`run_check_integrity`
|
| | |
| |
| |
| |
| |
| | |
- Fix bug where expired keys from one keystore were incorrectly
associated with all keystores
- Remove unnecessary clone
|
| | |
| |
| |
| | |
`run_check_integrity`
|
| | |
| |
| |
| |
| |
| | |
- Add `display_invalid_keystore_entries` helper function
`print_check_integrity_incipit`
- Add `display_invalid_keystore_entries` comment
|
| | |
| |
| |
| |
| |
| | |
Add initial functional implementation of `display_invalid_keystore_entries`,
which processes a list of invalid keystore entries grouped by `KeystoreId`
and displays them with associated error messages.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Create the skeletal version of the new `display_invalid_keystore_entries` function
and adapt `run_check_integrity` to use it.
The function now takes a slice of pairs, each containing a `KeystoreId` and a vector
of invalid keystore entries along with their error messages, and processes all
entries internally by iterating over each keystore, instead of being called
once per keystore.
|
| |/
|
|
|
|
|
|
|
| |
Previously, the function worked with a flat `Vec<KeystoreEntryResult<KeystoreEntry>>`.
Now, it uses a structured `Vec<(KeystoreId, Vec<KeystoreEntryResult<KeystoreEntry>>)>`,
grouping entries by keystore.
This makes it easier to track which keystore each entry belongs to,
and prepares the code for upcoming improvements.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because we've updated our MSRV, we must bump the minor version for every
package.
This was done as follows:
cargo set-version -p arti 1.6.0
cargo set-version -p oneshot-fused-workaround 0.4.0
cargo set-version -p slotmap-careful 0.4.0
cargo set-version -p test-temp-dir 0.5.0
cargo set-version -p fslock-guard 0.4.0
cargo set-version -p hashx 0.5.0
cargo set-version -p equix 0.4.0
cargo set-version -p caret 0.7.0
cargo set-version -p fs-mistrust 0.12.0
cargo set-version -p safelog 0.6.0
cargo set-version -p retry-error 0.8.0
xargs -I P <<END cargo set-version -p P 0.35.0
tor-basic-utils
tor-error
tor-general-addr
tor-geoip
tor-rtcompat
tor-rtmock
tor-async-utils
tor-config
tor-config-path
tor-rpc-connect
tor-log-ratelim
tor-rpcbase
tor-memquota
tor-units
tor-llcrypto
tor-bytes
tor-protover
tor-checkable
tor-cert
tor-key-forge
tor-hscrypto
tor-socksproto
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-relay-selection
tor-persist
tor-keymgr
tor-chanmgr
tor-ptmgr
tor-dircommon
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-dirserver
tor-hsclient
tor-hsservice
tor-hsrproxy
tor-relay-crypto
arti-client
arti-relay
arti-rpcserver
arti-ureq
arti-rpc-client-core
END
|
| | |
|
| |
|
|
| |
This feature has been removed from nightly, in favor of doc_cfg.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
It's unlikely these arguments will be particularly useful, and omitting
skip_all can have security implications, so it's better to avoid it to
reflect good practice.
|
| | |
|