<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/src/parse2/poc/authcert.rs, branch arti-v2.2.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.2.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.2.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-03-19T10:37:47Z</updated>
<entry>
<title>tor-netdoc: parse2: Move hash out of signature items</title>
<updated>2026-03-19T10:37:47Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-11T13:06:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=aefa48e251f514a2cdbcb9e4a26292438b74af68'/>
<id>urn:sha1:aefa48e251f514a2cdbcb9e4a26292438b74af68</id>
<content type='text'>
During encoding, including these hashes in the signature items makes
no sense.  The hashes are an *input* to the signature items, but not
part of them.

Move the hashes out of the items.  Instead, provide each signatures
section type with a hash accumulator type, in which the hash(es) are
stored.
</content>
</entry>
<entry>
<title>tor-netdoc: parse2: Introduce SignatureData struct</title>
<updated>2026-03-19T10:37:47Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-03T19:24:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=399c09200a008b02f4a9551fed22032feacf198d'/>
<id>urn:sha1:399c09200a008b02f4a9551fed22032feacf198d</id>
<content type='text'>
This is going to contain body information, and the hashes, too.
</content>
</entry>
<entry>
<title>tor-netdoc: Rename *Signed to *Unverified</title>
<updated>2026-03-03T18:56:01Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-03T18:46:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9018c73d34ca60c5f671eeafc540446864998941'/>
<id>urn:sha1:9018c73d34ca60c5f671eeafc540446864998941</id>
<content type='text'>
This was a weird name, and while working in this area it all seemed to
make the docs strange.

Rename it.  This is quite invasive!

In theory we could have the macros generate compatibility aliases, but
that seems quite complex.
</content>
</entry>
<entry>
<title>tor-netdoc: Abolish poc's AuthCert (rustfmt)</title>
<updated>2026-01-15T12:37:09Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-01-14T18:28:48Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f4a7ba859c45dcb995dbace328790d9f9e4d0193'/>
<id>urn:sha1:f4a7ba859c45dcb995dbace328790d9f9e4d0193</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Abolish poc's AuthCert</title>
<updated>2026-01-15T12:37:09Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-01-14T15:46:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=50e8eaa1f8f8012bc41ad4bfbffa15e3a97647d6'/>
<id>urn:sha1:50e8eaa1f8f8012bc41ad4bfbffa15e3a97647d6</id>
<content type='text'>
We can use the real AuthCert now that it implements the parse2 traits.

The verification function is still used by poc's netstatus code and by
a test case.

We must change the field names in a few places, because the real
AuthCert's struct field names are the keywords, whereas the poc's are
the key names.  (A shame that they're different!)
</content>
</entry>
<entry>
<title>tor-netdoc: Prepare poc's DirAuthKeyCertSigned::verify_selfcert</title>
<updated>2026-01-15T12:37:09Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-01-14T15:46:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=37c3ca300bde7a4a34db4111b5c9192c08b160f6'/>
<id>urn:sha1:37c3ca300bde7a4a34db4111b5c9192c08b160f6</id>
<content type='text'>
Use accessors for the body.

(Eventually this function will replace, be replaced by, or merge with,
the existing signature code outside poc.)
</content>
</entry>
<entry>
<title>tor-netdoc: Introduce `NormalItemArgument` impl-enabler trait</title>
<updated>2025-10-08T11:27:36Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-06T14:50:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c9a414ac29314bcbd285c55ccfb4cc54681d5fa7'/>
<id>urn:sha1:c9a414ac29314bcbd285c55ccfb4cc54681d5fa7</id>
<content type='text'>
This is currently used to enable `parse2::ItemArgumentParseable`.
In a moment it will enable `build::ItemArgument` too.
</content>
</entry>
<entry>
<title>tor-netdoc: parse2 poc: impl Display for several types</title>
<updated>2025-10-08T11:27:36Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-10-06T14:51:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=093c16a45072d153d2a84635605587281b113597'/>
<id>urn:sha1:093c16a45072d153d2a84635605587281b113597</id>
<content type='text'>
</content>
</entry>
<entry>
<title>netdoc parse2: Fix Object handling</title>
<updated>2025-09-29T12:58:22Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-09-03T17:52:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b050d9451a6ffffab3c81cc4c46bca96a124d99b'/>
<id>urn:sha1:b050d9451a6ffffab3c81cc4c46bca96a124d99b</id>
<content type='text'>
Use the standard multiplicity technique rather than the ad-hoc impl on
Option.  This allows us to support an ad-hoc parsing function for a
field that's `Option`.

Disentangle the `label` field attribute, which did both setting the
label, and expecting a different parsing approach: replace it with
`with`.
</content>
</entry>
<entry>
<title>tor-netdoc: Proof-of-concept demo of new parser</title>
<updated>2025-08-14T10:54:33Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-06T13:21:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a83d4b5f82118d2b28e554f9b567ff0439af7407'/>
<id>urn:sha1:a83d4b5f82118d2b28e554f9b567ff0439af7407</id>
<content type='text'>
This can parse and validate the signatures on a consensus.
</content>
</entry>
</feed>
