| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| |
| | |
release: Bump versions.
See merge request tpo/core/arti!3311
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| | |
We plan to release on Monday.
|
| |/ |
|
| |\
| |
| |
| |
| | |
release: Run cargo update.
See merge request tpo/core/arti!3305
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This behaviour was changed in humantime 2.3.0. Because they made this
breaking change on a minor semver bump, if we want to depend on this
behaviour, we would need to lock to a specific version. I don't think
this is critical, but I am still looking into where exactly this is
used.
|
| |\ \
| | |
| | |
| | |
| | | |
release: Run fixup-features.
See merge request tpo/core/arti!3303
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | | |
release: Update semver.md files.
See merge request tpo/core/arti!3308
|
| | |/ |
|
| |\ \
| |/
|/|
| |
| | |
tor-proto: Fix comment related to validating stream messages
See merge request tpo/core/arti!3298
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I don't think the previous comment is correct. The main flow control
checks are about receiving SENDME/XON/XOFFs, and ensuring that we don't
receive too many of them. This all happens in the reactor.
In theory the stream should be checking that we don't receive too many
DATA messages for how many stream SENDMEs we've sent. But this is broken
due to arti#2100. We do check this in the halfstream code though.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
tor-netdoc: Abolish `dangerous-expose-struct-fields`; always expose, instead
Closes #2192
See merge request tpo/core/arti!3299
|
| | | |
| | |
| | |
| | | |
Fixes #2192
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
macos-native-tls-notice: Notice for native-tls bug on MacOS
See merge request tpo/core/arti!3297
|
| | | |/
| |/|
| | |
| | | |
native-tls bug on MacOS
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
padding: Remove post-queue blocker.
Closes #2190
See merge request tpo/core/arti!3293
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
We no longer want to _ever_ block non-DATA cells, per discussion
in circuit-padding.md.
Closes #2190.
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
tor-key-forge: Add RSA key types.
See merge request tpo/core/arti!3236
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
As discussed with gabi on IRC today.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some things I'm still considering here:
* We may want to define a tor_llcrypto::pk::rsa::Signature newtype.
* We likely want to rename tor_llcrypto::pk::rsa::PrivateKey to RsaKeypair.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove check_doc_features and doc_auto_cfg.
Closes #1514
See merge request tpo/core/arti!3294
|
| | | | |
| | | |
| | | |
| | | | |
This feature has been removed from nightly, in favor of doc_cfg.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
Fix two clippy warnings
See merge request tpo/core/arti!3295
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes
warning: struct `PossumCage` is never constructed
warning: associated function `make_cast_table` is never used
with
cargo +stable clippy --locked --offline -p tor-rpcbase --all-targets
Most of our builds happen with --all-features so we don't notice. In
that case I think something to do with method
printing:(`describe-methods`) is using things enough for the compiler
not to complain.
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Sort output events for next_circ_action.
See merge request tpo/core/arti!3292
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This sort makes it so that that blocking and unblocking are always
ordered in a sensible way with respect to sending data. This might
help simplify padding machines a bit.
Prerequisite for #2190
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Add experimental OpenTelemetry support
See merge request tpo/core/arti!3239
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We may want to add a way to opt out of this check, if someone asks for
it. Checking for "localhost" and "127.0.0.1" is not a very robust check
for a loopback interface, and it's possible that there could be other
situations we can't detect where HTTP is safe (private network,
WireGuard tunnel, etc). But I don't expect those to be likely to come up
in practice, so this should be fine for now.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
I've added these in places that are useful for the debugging that I've
been doing.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Should fix the minimal versions test?
|