<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/Cargo.lock, branch arti-v1.1.11</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.11</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.11'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-12-04T16:37:56Z</updated>
<entry>
<title>Two more patchlevel bumps</title>
<updated>2023-12-04T16:37:56Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:37:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c730cd00e5c131f62425be190579c7ce4748e11c'/>
<id>urn:sha1:c730cd00e5c131f62425be190579c7ce4748e11c</id>
<content type='text'>
These crates both depend on tor-error.  Since tor-error got a
patchlevel bump, they now depend on the new version, which means by
our rules that _they_ get a patchlevel bump themselves.

tor-geoip
tor-rpcbase
</content>
</entry>
<entry>
<title>Bump minor versions in preparation for release</title>
<updated>2023-12-04T16:35:23Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:22:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fba95e4b4708929ed09554632acd2e9f15e3c086'/>
<id>urn:sha1:fba95e4b4708929ed09554632acd2e9f15e3c086</id>
<content type='text'>
This crate is new, and gets a bump to 0.1.0.

tor-log-ratelim

This crate had a breaking change:

tor-persist

tor-llcrypto had a breaking change.  These crates _are_
tor-llcrypto, or (transitively) depend on it. I am assuming that
they all re-expose something from it in a way that matters:

tor-llcrypto
tor-bytes
tor-hscrypto
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-hyper
</content>
</entry>
<entry>
<title>Bump patchlevel versions in preparation for release</title>
<updated>2023-12-04T16:33:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:22:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=606905bd1fa3307a77a02463fa863f4c2b7cb890'/>
<id>urn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890</id>
<content type='text'>
These crates had backward-compatible changes, and get a patchlevel
bump only:

fs-mistrust
tor-error
tor-config
tor-rtcompat
tor-rtmock

This crate exposes no non-CLI APIs, and gets a patchlevel bump only:

arti
</content>
</entry>
<entry>
<title>Run cargo-update in preparation for release.</title>
<updated>2023-12-04T14:44:24Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T14:44:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e4655a316832502f305e9b3592076e98184e9503'/>
<id>urn:sha1:e4655a316832502f305e9b3592076e98184e9503</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Move from `trust-dns` to `hickory`</title>
<updated>2023-11-30T17:05:13Z</updated>
<author>
<name>Andrew</name>
<email>adoubt@disroot.org</email>
</author>
<published>2023-11-28T14:26:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cfb1212577219547b2c9eacae96de707329e827b'/>
<id>urn:sha1:cfb1212577219547b2c9eacae96de707329e827b</id>
<content type='text'>
This is not a change of ownership but just rebranding.

Signed-off-by: Andrew &lt;adoubt@disroot.org&gt;
</content>
</entry>
<entry>
<title>Require config ≥ 0.13.4</title>
<updated>2023-11-30T00:54:41Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-28T14:03:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=68dffd2a7f8020d3bdd1fdcb7955be3b0f82cbe5'/>
<id>urn:sha1:68dffd2a7f8020d3bdd1fdcb7955be3b0f82cbe5</id>
<content type='text'>
This version of the config crate includes a fix for the issue
(https://github.com/mehcode/config-rs/issues/464)
that had prevented us from using the format we had wanted for
our rproxy configuration.
</content>
</entry>
<entry>
<title>Merge branch 'semver-breaking-upgrade-of-the-daleks' into 'main'</title>
<updated>2023-11-29T20:51:12Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-29T20:51:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bdea25be86cd3e0e327d34f6748140af1c6f3b69'/>
<id>urn:sha1:bdea25be86cd3e0e327d34f6748140af1c6f3b69</id>
<content type='text'>
Convert to the latest versions of dalek-cryptography

Closes #808

See merge request tpo/core/arti!1767</content>
</entry>
<entry>
<title>Merge branch 'persist-tempdir' into 'main'</title>
<updated>2023-11-29T17:10:04Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2023-11-29T17:10:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=722ddc578e88c2fbe8a839c34dba60ebdd06a22c'/>
<id>urn:sha1:722ddc578e88c2fbe8a839c34dba60ebdd06a22c</id>
<content type='text'>
tor-hsservice tests: Introduce new test_temp_dir helper module

See merge request tpo/core/arti!1762</content>
</entry>
<entry>
<title>Remove RngCompatExt.</title>
<updated>2023-11-29T15:55:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-29T15:49:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7fb24cb69da537ac04ab2dae80997c6d481622ef'/>
<id>urn:sha1:7fb24cb69da537ac04ab2dae80997c6d481622ef</id>
<content type='text'>
This code was needed with the old version of dalek-cryptography,
which wasn't compatible with up-to-date versions of the `rand`
crate(s).  But now that we've upgraded, we can drop this.

(We could have left it around and deprecated it, but we are already
making a breaking change to tor-llcrypto by upgrading
dalek-cryptography.)
</content>
</entry>
<entry>
<title>Convert to the latest versions of dalek-cryptography</title>
<updated>2023-11-29T15:34:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-21T15:58:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=98037a2c788bd901679139178d25f855324637f3'/>
<id>urn:sha1:98037a2c788bd901679139178d25f855324637f3</id>
<content type='text'>
The main changes that we have to adjust for are as follows:

* In x25519-dalek:
  * `StaticSecret` is now behind a feature.
  * `StaticSecret::new` is deprecated in favor of
    `StaticSecret::random_from_rng`.
  * StaticSecret no longer does its own clamping.

* In ed25519-dalek:
  * `SecretKey` has (in effect) been renamed to `SigningKey`. The name
    `SecretKey` is now an alias for `[u8; 32]`.
  * `SigningKey` is effectively a keypair, since it contains a
     public key as well.
  * `PublicKey` has been renamed to `VerifyingKey`.
  * The functions to extract a signing key and verifying key have
    been renamed as you might expect.
  * `ExpandedSecretKey` has been moved to `hasmat` and no longer
    implements `sign`.
  * `ExpanededSecretKey` now has as its elements a scalar and a hash
    prefix.
  * Various functions that took `&amp;[u8]` now take `&amp;[u8; N]`.
  * We no longer need a wrapper for older versions of rand.

There is a single test in tor-keymgr that does not pass.  I've
marked it as ignore for now, in hopes that @gabi-250 can help me
figure it out.

This closes #808.  There are several changes I want to make before
we merge, however. They are marked with TODO DALEK.
</content>
</entry>
</feed>
