| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
These aren't needed anymore now that `KeySpecifierComponent` is in
scope.
|
| | | |
| | |
| | |
| | | |
This will be used for looking up certificates in the keystore.
|
| | | |
| | |
| | |
| | |
| | | |
We're soon going to need the "raw" version of the function (the one that
returns the key as `K::Key`).
|
| | | |
| | |
| | |
| | |
| | | |
These will be soon be returned by
`KeyMgr::{get_key_and_cert,get_or_generate_key_and_cert}`.
|
| | | |
| | |
| | |
| | |
| | | |
This will enable us to store `tor_cert::EncodedEd25519Cert`s in the
keystore.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This will be used by the `Keystore` implementations.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This function now returns a `KeystoreItemType`, enabling us to represent
certs as `EncodableItem`s.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This enables us to auto-generate tests for all the supported key/cert
file extensions.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Items that have an unrecognized file extension now get mapped to
`KeystoreItemType::Unknown`.
|
| | | |
| | |
| | |
| | |
| | | |
This is part of the work needed to support storing certificates in the
keystore (they won't have a `KeyType`, but rather `CertType`).
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is the first step in replacing `EncodableKey` with the new
`EncodableItem` trait (see doc/dev/keymgr-certificates.md).
(this refactoring is split over multiple commits to make reviewing
easier)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The `EncodableKey` trait will soon be extended to support encoding
certificates too (in addition to keys), so we need a type to represent
an object that is either a key or a certificate (in other words, an
encodable *item*).
|
| | | |
| | |
| | |
| | |
| | | |
`tor-key-forge` now depends on `tor-cert` so we need to reorder the deps
in `Cargo.toml` to satisfy `maint/check_toposort`.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This will be used for defining key certificate specifiers.
|
| |/ /
| |
| |
| |
| | |
Soon the keystore will be able to store certs too, so we need something
other than `KeyType` to represent the "type" of a keystore entry.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
maint: Add exclusion feature to `fixup-features`
Closes #1766
See merge request tpo/core/arti!2652
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit adds an `--exclude <PREFIX>` argument to the
`fixup-features` tool in order to ignore crate paths for crates that we
do not publish, mainly those in the `examples/` and `maint/` directory.
Fixes #1766
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Resolve/suppress new clippy warnings in Rust 1.83.
See merge request tpo/core/arti!2654
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This warning is new in 1.83. Surprisingly, it only triggered once.
div_ceil was added in Rust 1.73, and our MSRV is 1.77, so div_ceil
is fine to use.
|
| | | |
| | |
| | |
| | | |
These are new in Rust 1.83.
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
In 1.83, this warning triggers on many of our crates.
We're thinking of fixing them all, but for now,
we're going to disable the warning.
This is part of #1765.
|
| |\ \
| | |
| | |
| | |
| | | |
Remove semver.md files post-release.
See merge request tpo/core/arti!2651
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Version bumps for 1.3.1
See merge request tpo/core/arti!2650
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Done using:
```
cargo set-version --bump patch -p arti
```
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.25.0
done
```
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The non-{arti-,tor-} crates are:
```
./maint/list_crates | rg -v '^(tor|arti)'
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
```
We split them in the following categories:
* crates with no changes (no version bumps):
```
maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
oneshot-fused-workaround: No change.
test-temp-dir: No change.
caret: No change.
```
* crates that only have non-functional changes (bump the patch version):
- slotmap-careful
- fslock-guard
- hashx
- equix
- fs-mistrust
- safelog
- retry-error
* crates where APIs were broken (bump minor):
None
The bumps from this commit were created using this script:
```
PATCH="
slotmap-careful
fslock-guard
hashx
equix
fs-mistrust
safelog
retry-error
"
for crate in $PATCH; do
cargo set-version --bump patch -p $crate;
done
```
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Done using
```
(cd crates/hashx/bench && cargo update)
(cd crates/equix/bench && cargo update)
```
|
| |\ \
| | |
| | |
| | |
| | | |
Changelog for 1.3.1.
See merge request tpo/core/arti!2649
|
| | | | |
|
| | | | |
|
| | | | |
|
