<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-proto/src/crypto/handshake, branch arti-v1.1.2</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.2</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.2'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-02-28T11:10:17Z</updated>
<entry>
<title>Rename onion-* cargo features to hs-* in tor-* crates</title>
<updated>2023-02-28T11:10:17Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-02-24T14:26:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f63c7c48afd94fe9d09746f0b76fbaff8d4a1a79'/>
<id>urn:sha1:f63c7c48afd94fe9d09746f0b76fbaff8d4a1a79</id>
<content type='text'>
Fixes #756
</content>
</entry>
<entry>
<title>Allow clippy::unchecked_duration_subtraction in tests</title>
<updated>2023-01-27T13:28:02Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-27T13:01:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a6dd92843edf2bd4c58de62a0d562921e4191ada'/>
<id>urn:sha1:a6dd92843edf2bd4c58de62a0d562921e4191ada</id>
<content type='text'>
This panics on error, and we're fine with a panic on misbehavior in
tests.
</content>
</entry>
<entry>
<title>tor-proto: Expose support for doing onion service handshakes</title>
<updated>2023-01-17T20:20:03Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-11T19:13:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e8ed46006e4951a7e0098edcac1f0e6a260bd9b5'/>
<id>urn:sha1:e8ed46006e4951a7e0098edcac1f0e6a260bd9b5</id>
<content type='text'>
This is a little tricky, but I think that we're not actually
exposing too much here.  I expect we'll need to tweak this stuff
between now and our final version.
</content>
</entry>
<entry>
<title>test lint blocks: Add many many automatically</title>
<updated>2022-12-12T18:00:30Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-12-12T17:58:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=125a455bdcca841931f33f83f206e57637ae85c4'/>
<id>urn:sha1:125a455bdcca841931f33f83f206e57637ae85c4</id>
<content type='text'>
This is precisely the result of running the rune in
maint/adhoc-add-lint-blocks.
</content>
</entry>
<entry>
<title>test lint blocks: Do some semi-manually</title>
<updated>2022-12-12T18:00:29Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-12-12T17:57:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=baf78361e848269a24a3019d99f87943872e6012'/>
<id>urn:sha1:baf78361e848269a24a3019d99f87943872e6012</id>
<content type='text'>
This is the hunks from running the rune in maint/adhoc-add-lint-blocks
but which require some subsequent manual fixup: usually, deleting
now-superfluous outer allows, but in some cases manually putting back
lints that the adhoc script deleted.
</content>
</entry>
<entry>
<title>Fix a bunch of "needless borrow" warnings on nightly</title>
<updated>2022-11-18T15:12:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-18T15:12:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d51162e55b19036528b4fafc1d4b15c8d9d23a04'/>
<id>urn:sha1:d51162e55b19036528b4fafc1d4b15c8d9d23a04</id>
<content type='text'>
It looks like, despite a few false starts, they've got this warning
right; there weren't any false positives.
</content>
</entry>
<entry>
<title>tor-proto: Use correct SecretBuf in handshakes.</title>
<updated>2022-08-01T19:41:22Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-08-01T19:14:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=37e6c95fdc01319fc8afb34229e7b097851da33d'/>
<id>urn:sha1:37e6c95fdc01319fc8afb34229e7b097851da33d</id>
<content type='text'>
Everything that is a secret encryption key, or an input that is used
to produce a secret encryption key, has to get zeroized.  And that's
all!

Closes #254.
</content>
</entry>
<entry>
<title>tor-proto: Replace SecretBytes with SecretBuf.</title>
<updated>2022-08-01T19:41:22Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-08-01T18:53:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=eedd63d5e9a4e055260b476177ee14972584a1bb'/>
<id>urn:sha1:eedd63d5e9a4e055260b476177ee14972584a1bb</id>
<content type='text'>
This does not yet make sure that `SecretBuf` is used where it
_should_ be, but at least it ensures that most uses of `SecretBytes`
will indeed act as intended, and make sure that whatever they
contain is zeroized.

It requires some corresponding changes to method calls for
correctness and type conformance.
</content>
</entry>
<entry>
<title>tor-proto: Stop using write_infallible in handshake code.</title>
<updated>2022-07-11T15:18:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-11T15:04:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fbb6484025ac024642afbeef6734d88e35210673'/>
<id>urn:sha1:fbb6484025ac024642afbeef6734d88e35210673</id>
<content type='text'>
This change was a bit annoying, since most of this code _can't_ fail,
and so the only reasonable response is to wrap the input in an
internal error... except for one case where we're actually encoding
a caller-provided message, so we _do_ want to wrap the EncodeError
from tor_bytes.
</content>
</entry>
<entry>
<title>Remove "write_and_consume_infallible".</title>
<updated>2022-07-11T15:18:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-08T16:06:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5a61a6d73aa2ddf4dd99c8af9c6082bb8c56d158'/>
<id>urn:sha1:5a61a6d73aa2ddf4dd99c8af9c6082bb8c56d158</id>
<content type='text'>
There were only a few of these.  Removing it required porting
everything to use `write_and_consume` instead, and handling its
(potential) errors.
</content>
</entry>
</feed>
