mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.3.0 2026-04-28T16:27:56Z 2026-04-28T16:27:56Z Clara Engler cve@cve.cx 2026-04-28T08:09:13Z urn:sha1:67c4e02d595fed7ce3afc06e43f2577244b67ff4 If extra-infos is set to NULL, which might be the case for micro descriptors or even router descriptors because the field is optional there, this SQL query fails because it cannot LEFT JOIN server.extra_unsigned_sha1 when this field is NULL. To fix this, we simply add an additional clause to the WHERE statement that filters such rows out. 2026-04-27T15:46:58Z Clara Engler cve@cve.cx 2026-04-14T09:01:32Z urn:sha1:6b26ebb430da64239c1698798b2ee1543129cba7 This commit makes use of the presence of only one descriptor hash inside consensus_router_descriptor_member by adding a respective AND clause to the select statements of missing descriptors to only select the rows with a non-null SHA-1 (or SHA-2 for the sake of microdescs) in the consensus_router_descriptor_member table. This is defensive programming and should not be required in practice because the docid as well as the "XOR" CHECK should already ensure that this value is always non-NULL. However, if it still happens and slips through, the statement would return NULL rows, which is not what we want and was previously prevented by ensuring this field was never NULL in the first place. 2026-04-27T15:46:58Z Clara Engler cve@cve.cx 2026-04-14T08:49:56Z urn:sha1:0b07bd3ee6a19af1025c02c52971a9071b937620 This commit modifies the consensus_router_descriptor_member table in the database schema, removing the NOT NULL constraint on unsigned_sha1 and unsigned_sha2 by replacing it with a new CHECK constraint that checks that either one of them is set but not both. The reason for this is as follows: We are going to use this table to compute the queue of missing descriptors, which means that we can only populate this table with the data we know from the consensus. The consensus however tells us only one of those hashes, namely sha1 in the case of a consensus-ns and sha2 in the case of a consensus-md. In other words: This commit can also be seen as an effort to change the design of the operation in such a way that the queue is obtained directly from the database and not computed at the start during state transition. 2026-04-21T14:52:33Z Nick Mathewson nickm@torproject.org 2026-04-19T20:06:44Z urn:sha1:80460f968db2c90d3d1dbc6a1592bff5e68f8de9 Rust 1.95 warns us that this is an experimental API that could be stabilized in the future. 2026-03-24T16:04:08Z Tobias Stoeckmann tobias@stoeckmann.org 2026-03-24T16:04:08Z urn:sha1:1fb2b8dd4aee7c943ce90d6631be473f2a296fe6 Typos found with codespell 2026-03-09T08:31:28Z Clara Engler cve@cve.cx 2026-02-25T11:16:09Z urn:sha1:ec1dc8a0dba0c7e2389dcf6291c80b5626472354 2026-03-09T08:31:28Z Clara Engler cve@cve.cx 2026-02-25T10:41:43Z urn:sha1:c3738787191c3f21b74e592ea67cce6a60f1af53 This commit replaces the uses of sha1, sha2, and sha3 with their respective pedants from tor-llcrypto for better consistency. Internally, they still use the same logic and underlying crates but let's use this encapsulation nonetheless. 2026-03-09T08:31:28Z Clara Engler cve@cve.cx 2026-02-25T10:29:55Z urn:sha1:27a1ebcef3263522acb9a02763f52eadf113fe4c 2026-03-09T08:31:28Z Clara Engler cve@cve.cx 2026-02-25T09:11:55Z urn:sha1:7814e15ae0f88da389349d2ada0e1101f235063c This commit moves the database schema into schema_v1.sql and uses include_str to include it. For now, the schema lives in the `src/` directory. If this becomes a problem because we get more schemas and schema upgrades, we can move it into another sub directory, but let's not overengineer the hierarchy there. 2026-03-09T08:31:23Z Clara Engler cve@cve.cx 2026-02-09T13:13:33Z urn:sha1:03b54563e88b41c63bc176ecbfcac364b0a389f5 This commit implements the logic required for retrieving, validating, and storing authority certificates. The implementation determines the missing certificates by looking at the signatories of the unvalidated consensus and checking them in the db. Afterwards, they will be queried and individually filtered and verified before being inserted into the database. A return of this implementation notably DOES NOT imply all missing certificates have been downloaded. This was chosen for a simplified retry logic.