| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Without this, the onion client was failing to find a guard.
We recently made this change in shadow's "tor minimal" test as well.
|
| | | | | | |
|
| | | | | | |
|
| | | |/ /
| |/| | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Mark several crates with `publish=false`.
Closes #944
See merge request tpo/core/arti!1371
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This crate is only useful for development; earlier we published it,
but I believe that was in error.
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
These crates were started, but they aren't integrated into
Arti (yet?). As such it doesn't make sense to keep publishing
updated versions of them every time we tweak our standard
lints.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
try making CI faster
See merge request tpo/core/arti!1373
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Additional documentation around bridges/PT configuration
Closes #706
See merge request tpo/core/arti!1370
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This tries to flesh out some of the details for users who may be new
to bridges and PTs.
Closes #706.
|
| |/ / |
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Update Release.md to describe our current process
Closes #942
See merge request tpo/core/arti!1366
|
| | |
| |
| |
| | |
(We didn't do this previously, but it is a good idea.)
|
| | |
| |
| |
| |
| |
| |
| |
| | |
* Remove instructions to sleep
* Explain how to tag
* Remind myself about the workaround for
Fedora's delightful gpg/yubikey configuration.
* Note that we should update "pages" till the blog post is up.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I've split this into
"what I do in the days leading up to the release" and
"what I do right before the release".
There's a lot more detail now, including:
* up-to-date invocations for `cargo upgrade`
* up-to-date changelog instructions
* our current version-bumping instructions
* possible side-effects from version bumps.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Remove references to a couple of things
that our CI now does for us
(`cargo_audit` and `check_licenses`).
* Mention ~Blocker issues and MRs.
* Mention that some of our CI steps are allowed-to-fail,
but failures should be examined.
* Mention that some of our tools have exception lists
that should get reviewed.
* Mention `semver-checks` and `fixup-features`.
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
keymgr: Fix broken doc link.
See merge request tpo/core/arti!1363
|
| |/ |
|
| |\
| |
| |
| |
| | |
Bump all versions in preparation for 1.1.6 release.
See merge request tpo/core/arti!1362
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Done with the commands below.
The following crates have had various changes, and should get a
patchlevel bump. Since they are pre-1.0, we do not need to
distinguish new APIs from other changes.
```
cargo set-version --bump patch -p arti-client
cargo set-version --bump patch -p safelog
cargo set-version --bump patch -p tor-bytes
cargo set-version --bump patch -p tor-cert
cargo set-version --bump patch -p tor-circmgr
cargo set-version --bump patch -p tor-config
cargo set-version --bump patch -p tor-consdiff
cargo set-version --bump patch -p tor-dirclient
cargo set-version --bump patch -p tor-dirmgr
cargo set-version --bump patch -p tor-error
cargo set-version --bump patch -p tor-hsservice
cargo set-version --bump patch -p tor-linkspec
cargo set-version --bump patch -p tor-llcrypto
cargo set-version --bump patch -p tor-netdir
cargo set-version --bump patch -p tor-netdoc
cargo set-version --bump patch -p tor-proto
cargo set-version --bump patch -p tor-rpcbase
cargo set-version --bump patch -p tor-socksproto
```
This crate has new features, but no new non-experimental Rust APIs.
So even though it is post-1.0, it gets a patchlevel bump.
```
cargo set-version --bump patch -p arti
```
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Done with:
```
cargo set-version --bump minor -p tor-hsclient
cargo set-version --bump minor -p arti-rpcserver
cargo set-version --bump minor -p tor-hscrypto
cargo set-version --bump minor -p tor-cell
```
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These crates have had nonfunctional changes only, mostly due to !1271,
or ac90cb7500f2f108, or documentation changes: crates that depend on
them do not require a version bump.
```
arti-bench
arti-config
arti-hyper
arti-testing
caret
fs-mistrust
retry-error
tor-async-utils
tor-basic-utils
tor-chanmgr
tor-checkable
tor-congestion
tor-consdiff
tor-events
tor-guardmgr
tor-persist
tor-protover
tor-ptmgr
tor-rtcompat
tor-rtmock
tor-units
```
|
| |\ \
| |/
|/|
| |
| | |
Finish and copy-edit changelog
See merge request tpo/core/arti!1361
|
| | |
| |
| |
| | |
(Thanks to seborn)
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
keymgr: Allow periods in ArtiPath and ArtiPathComponent.
See merge request tpo/core/arti!1358
|
| | | |
|
| | |
| |
| |
| |
| | |
The docs were lying, we actually support UTF-8 paths (though we might
later decide to restrict the charset further).
|
| | |
| |
| |
| |
| |
| |
| | |
The `ArtiPath` of a client auth key contains the `HsId` of the onion
Since the `HsId` contains a `.onion` component, let's allow `.` for now.
In the future, we may want to update the code (and keystore structure)
to strip away the `.onion` part before building the `ArtiPath`.
|
| |\ \
| |/
|/|
| |
| | |
keymgr: Downgrade "TODO hs" to "TODO HSS"
See merge request tpo/core/arti!1360
|
| | |
| |
| |
| | |
This TODO doesn't need to block the release.
|
| |\|
| |
| |
| |
| | |
arti-client: Rename KeyStore to Keystore.
See merge request tpo/core/arti!1359
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`KeyStore` was renamed to `Keystore` globally in !1355. This fixes a
compile error caused an unfortunate series of non-conflicting (from
git's POV) but incompatible merges:
* !1356 added a line threferencing an error variant that capitalizes the
"s" in "KeyStore" (`ErrorDetail::KeyStore`)
* !1356 landed just before !1355 (the global renaming). Since there was
no conflict between the 2, we're now in a state where the code added
in !1356 is referencing an `ErrorDetail` variant that no longer
exists.
|
| |\ \
| | |
| | |
| | |
| | | |
Add a missing "experimental-api" rustdoc notation
See merge request tpo/core/arti!1353
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Run fixup-features on current `main`
See merge request tpo/core/arti!1352
|
| | | |
| | |
| | |
| | |
| | | |
Some of these seem spurious: it looks like fixup-features resolved
an issue and then complained about it too. I'll investigate further.
|
| | | | |
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | | |
keymgr: Rename KeyStore to Keystore globally.
See merge request tpo/core/arti!1355
|
| | |/
| |
| |
| |
| | |
We've been capitalizing the "s" in "KeyStore" inconsistently. This
`s/KeyStore/Keystore/g` across the codebase.
|