<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-keymgr, branch arti-v1.2.8</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.8</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.8'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-09-30T13:04:32Z</updated>
<entry>
<title>Bump arti- and tor- crates to 0.23.0</title>
<updated>2024-09-30T13:04:32Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-30T13:04:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d6890da4b1f87fd5e834aeb0cc9a7cd4b1d99e88'/>
<id>urn:sha1:d6890da4b1f87fd5e834aeb0cc9a7cd4b1d99e88</id>
<content type='text'>
Per our policy, every one of these gets a minor bump.

Generated with:

```
for crate in $(./maint/list_crates | grep '^\(tor\|arti\)-' ); do
    cargo set-version --bump minor -p $crate;
done
```
(Note the use of `-` at the end end of the grep pattern to prevent
matching the `arti` crate.)
</content>
</entry>
<entry>
<title>Minor bumps on non-tor/arti crates</title>
<updated>2024-09-30T12:56:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-30T12:56:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b29dd6d7f90cf077e8809a1ab317e23535e165c8'/>
<id>urn:sha1:b29dd6d7f90cf077e8809a1ab317e23535e165c8</id>
<content type='text'>
These crates are not in the tor/arti namespace,
but we have given them MSRV bumps:

```
oneshot-fused-workaround
slotmap-careful
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
test-temp-dir
retry-error
```

We are counting this as a breaking change.
Since all of these crates are at 0.x.x,
we have indicated the breaking change with a minor version bump.

This commit was generated with the following script:

```
BUMPS="
oneshot-fused-workaround
slotmap-careful
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
test-temp-dir
retry-error
"

for crate in $BUMPS; do
    cargo set-version --bump minor -p $crate;
done
```
</content>
</entry>
<entry>
<title>Merge branch 'msrv-1.77-and-rusqlite-update' into 'main'</title>
<updated>2024-09-26T14:24:02Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2024-09-26T14:24:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2ad24dd46615d908cefa68f5a9752d4863b89b6c'/>
<id>urn:sha1:2ad24dd46615d908cefa68f5a9752d4863b89b6c</id>
<content type='text'>
Upgrade MSRV to 1.77 , and rusqlite to 0.32.1

See merge request tpo/core/arti!2451</content>
</entry>
<entry>
<title>Upgrade MSRV to 1.77</title>
<updated>2024-09-26T01:54:22Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-25T14:46:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ff9e93a2a10ef02f436c6f7d7a05739a818b094a'/>
<id>urn:sha1:ff9e93a2a10ef02f436c6f7d7a05739a818b094a</id>
<content type='text'>
This will allow us to upgrade to the latest version of rusqlite.
</content>
</entry>
<entry>
<title>Upgrade to derive_more version 1.0.0</title>
<updated>2024-09-25T14:37:18Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-25T14:37:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6a12c2ba8515226a772d5f4a81930bf42d67535a'/>
<id>urn:sha1:6a12c2ba8515226a772d5f4a81930bf42d67535a</id>
<content type='text'>
The `derive_more` crate broke backward compatibility with this version,
so this change involved quite a few manual fixups.
With luck, they'll keep compatibility for some while in the future.
</content>
</entry>
<entry>
<title>tor-keymgr: Rename keystore.type to keystore.kind.</title>
<updated>2024-09-23T18:55:23Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-23T14:43:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7d075d16e615138552f91a72e9cf0faf0fcb1739'/>
<id>urn:sha1:7d075d16e615138552f91a72e9cf0faf0fcb1739</id>
<content type='text'>
In !2394 we settled on `kind`. This updates the error messages to
reference the new field name.
</content>
</entry>
<entry>
<title>tor-keymgr: Move keystore config under keystore.primary.</title>
<updated>2024-09-23T18:55:23Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-23T14:14:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dcb29c0e5d5ad1c3795baa50f778a0f13d668325'/>
<id>urn:sha1:dcb29c0e5d5ad1c3795baa50f778a0f13d668325</id>
<content type='text'>
The keystore settings only configure the *primary* keystore, so they
should be under `keystore.primary`.
</content>
</entry>
<entry>
<title>arti: Reinstate the keystore.enabled option.</title>
<updated>2024-09-23T18:37:41Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-23T14:08:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c359a7abd1543c53c596e9092350b0810f72765e'/>
<id>urn:sha1:c359a7abd1543c53c596e9092350b0810f72765e</id>
<content type='text'>
This is a follow-up from !2394

I want to keep the `keystore.enabled` option, because I'm planning on
extending `ArtiKeystoreConfig` to support configuring secondary
keystores too (currently, the only supported setting is `keystore.kind`,
which configures the primary keystore). `keystore.enabled` will disable
keystore use altogether (i.e. both primary and secondary).

Currently, we only support configuring the "primary" (previously known
as "default") keystore, which can be either "native" (the on-disk Arti
keystore), or "ephemeral" (an in-memory keystore). To implement #858,
we will need to support configuring additional keystores too, so we will
need to move to a config of the form
```toml
[storage.keystore]
# Whether the keystore is enabled.
#enabled = "auto"

# Configure the primary keystore.
[storage.keystore.primary]
# The type of primary keystore to use
kind = "auto" | "native" | "ephemeral"

# Optionally configure C Tor keystores for arti to use.
#
# Note: The keystores listed here are read-only (keys are only
# ever written to the primary keystore, configured in
# `storage.keystore.primary`).
[[storage.keystore.ctor]]
# If the `kind` is `service`, this should be set to the `HiddenServiceDirectory`
# of your hidden service. Arti will read `HiddenServiceDirectory/hostname`
# and `HiddenServiceDirectory/private_key`. (Note: if your service is running
# in restricted discovery mode, you must set the
# `[[onion_services."&lt;the nickname of your svc&gt;".restricted_discovery.key_dirs]]`
# to `HiddenServiceDirectory/client_keys`
#
# If the `kind` is `client`, this should be set to `ClientOnionAuthDir` of
# your client. If Arti is configured to run as a client (i.e. if it runs in SOCKS
# proxy mode), it will read the client restricted discovery keys from this path.
path  = "/foo/bar"
# The type of keystore `path` should be interpreted as
kind = "client" | "service"
```

This moves the current keystore settings to `storage.keystore.primary`
in preparation for that change.
</content>
</entry>
<entry>
<title>tor-keymgr: Add back ArtiKeystoreConfig::is_enabled().</title>
<updated>2024-09-23T17:58:55Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-23T14:23:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b3cf77ed943e97428d2d6c3ef1f352ee9b273617'/>
<id>urn:sha1:b3cf77ed943e97428d2d6c3ef1f352ee9b273617</id>
<content type='text'>
I am adding `is_enabled()` back because I plan to un-deprecate the
`enabled` setting.
</content>
</entry>
<entry>
<title>tor-keymgr: Rename the primary keystore for clarity.</title>
<updated>2024-09-23T13:17:49Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-20T10:20:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=80095da1aa47978cdba26c2b3d254a99c075cf53'/>
<id>urn:sha1:80095da1aa47978cdba26c2b3d254a99c075cf53</id>
<content type='text'>
Previously, arti's primary keystore was referred to as its "default"
keystore. However, "default" is inaccurate here: there is no way to
meaningfully override this "default" (the "default" store acts as the
main keystore). Throughout the codebase, we query all keystores for keys
(including the secondary ones), but only ever write to the
default/primary keystore. This is OK for now, because it enables us to
have one mutable keystore, and multiple secondary, read-only stores.
</content>
</entry>
</feed>
