<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/src/doc/routerdesc.rs, branch arti-v0.1.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.1.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.1.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-02-14T18:08:28Z</updated>
<entry>
<title>Refactor tor_netdoc::Error</title>
<updated>2022-02-14T18:08:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-14T18:08:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b6d23c36bef1322e4fc6f89769222daa91c4d8f3'/>
<id>urn:sha1:b6d23c36bef1322e4fc6f89769222daa91c4d8f3</id>
<content type='text'>
This error type doesn't impement HasKind, since the kind will depend
on context.

However, the existing implementation was pretty messy and inconsistent:
Some errors had positions, some didn't.
Some took messages as str, some as String.
Some had internal errors that were somewhat orthogonal to their actual
types.

This commit refactors tor_netdoc::Error to use a ParseErrorKind, and
adds a set of convenience functions to add positions and
messages to the errors that need them.
</content>
</entry>
<entry>
<title>tor-netdoc: Change an XXX to a TODO.</title>
<updated>2021-12-20T14:46:56Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-20T14:46:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8cf143217e2655b90cb2a8690bc4ef75957906df'/>
<id>urn:sha1:8cf143217e2655b90cb2a8690bc4ef75957906df</id>
<content type='text'>
Our behavior in handling not-yet-valid router descriptors doesn't match
the C Tor implementation, but it's not a big deal:
we don't currently use router descriptors at all.
</content>
</entry>
<entry>
<title>tor-netdoc: Use a more correct error type</title>
<updated>2021-12-20T13:58:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-20T13:58:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6299ca70b43a8e93064fbd12e249f74566761d68'/>
<id>urn:sha1:6299ca70b43a8e93064fbd12e249f74566761d68</id>
<content type='text'>
If we fail to convert a curve25519 key to an ed25519 key for checking
the onion-key crosscert, don't call that an internal error: it means
that something is wrong with the provided ntor key.
</content>
</entry>
<entry>
<title>Remove an XXXX about ed25519 signatures.</title>
<updated>2021-12-20T13:53:42Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-20T13:53:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=92e53bff62742bce06989f6ad560f9510274d520'/>
<id>urn:sha1:92e53bff62742bce06989f6ad560f9510274d520</id>
<content type='text'>
As of tor-spec commit 01122c5bd7d2f0f, the spec is no longer ambiguous
on this point.
</content>
</entry>
<entry>
<title>Run "cargo update" to get latest versions.</title>
<updated>2021-11-29T19:52:53Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-11-29T19:45:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=805e558045018663d0d47b5f30733c6ca19b86ac'/>
<id>urn:sha1:805e558045018663d0d47b5f30733c6ca19b86ac</id>
<content type='text'>
Also fix a couple of warnings introduced by now-unneeded imports
with new ed25519 crate.

This is part of the process for releasing our next version.
</content>
</entry>
<entry>
<title>tor-netdoc: Put the "routerdesc" document type behind a feature.</title>
<updated>2021-11-12T17:15:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-11-12T16:19:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7b12b54d407580f8574975f5c7e864d65d986dd0'/>
<id>urn:sha1:7b12b54d407580f8574975f5c7e864d65d986dd0</id>
<content type='text'>
Nothing in arti currently uses this document type.  Eventually it
will be useful for relays and for bridge clients.

I've left the "SHA1 digest of a router descriptor" type available
unconditinoally, however, since it does get used in a few places.

Part of #125.
</content>
</entry>
<entry>
<title>derive 'Default' where possible</title>
<updated>2021-09-11T19:02:33Z</updated>
<author>
<name>Daniel Eades</name>
<email>danieleades@hotmail.com</email>
</author>
<published>2021-09-11T19:02:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=27cca7197811e1dc5ba531ddacaeaa210f48f021'/>
<id>urn:sha1:27cca7197811e1dc5ba531ddacaeaa210f48f021</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix/silence clippy lints in test modules</title>
<updated>2021-09-08T15:28:31Z</updated>
<author>
<name>Daniel Eades</name>
<email>danieleades@hotmail.com</email>
</author>
<published>2021-08-30T07:52:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fb3b8b84b5709ebe8a29051c43b82c4eef85decc'/>
<id>urn:sha1:fb3b8b84b5709ebe8a29051c43b82c4eef85decc</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Move all crates into a `crates` subdirectory.</title>
<updated>2021-08-27T13:53:09Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-08-27T13:53:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=557a0ff40b3731d4690767de27010bbeff08777d'/>
<id>urn:sha1:557a0ff40b3731d4690767de27010bbeff08777d</id>
<content type='text'>
This will cause some pain for now, but now is really the best time
to do this kind of thing.
</content>
</entry>
</feed>
