| 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
|
| |\ \
| | |
| | |
| | |
| | | |
release: Update CHANGELOG.md
See merge request tpo/core/arti!3329
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Fix minimal-versions CI
See merge request tpo/core/arti!3327
|
| | | | |
|
| |/ /
| |
| |
| |
| | |
Empirically, this is no longer present in our Cargo.lock.
The problem was fixed upstream, presumably.
|
| |\ \
| | |
| | |
| | |
| | | |
release: Update changelog.
See merge request tpo/core/arti!3310
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
release: Update release date.
See merge request tpo/core/arti!3319
|
| | | |
| | |
| | | |
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.
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
doc/dev/notes: Add note on tor-proto cell validation.
Closes #2177
See merge request tpo/core/arti!3291
|
| | | |
| | |
| | |
| | | |
Closes #2177
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
release: Run fixup-features.
See merge request tpo/core/arti!3303
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
release: Update semver.md files.
See merge request tpo/core/arti!3308
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
docs: Fix broken link in release checklist.
See merge request tpo/core/arti!3306
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Start a security response policy
See merge request tpo/core/arti!3233
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3233#note_3253024
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
docs: Fix release checklist item.
See merge request tpo/core/arti!3304
|
| | |/ / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
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
|
| | | | |
| | | |
| | | |
| | | | |
native-tls bug on MacOS
|
| | | |/
| |/|
| | |
| | | |
native-tls bug on MacOS
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
tor-rtmock-simple-time-typos: Fix typos
See merge request tpo/core/arti!3289
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | | | |
|