mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.6.0 2025-09-16T12:36:12Z 2025-09-16T12:36:12Z Nick Mathewson nickm@torproject.org 2025-09-15T15:52:48Z urn:sha1:e6abd7361dc69871d23c319506f43e4cc5e612b7 When we want to send Replace padding (that is, padding that should only be sent if nothing else is queued) to hop 1, we can allow it to be replaced by cells from _any_ circuit being sent over the same channel. (Nobody but hop 1 can tell the difference.) Closes #2169 2025-09-10T14:40:15Z Nick Mathewson nickm@torproject.org 2025-09-10T14:35:18Z urn:sha1:8f2062e3f60a580272f4144a1e9a73b98aadf487 2025-08-07T15:28:36Z Nick Mathewson nickm@torproject.org 2025-08-06T01:19:58Z urn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc First, run ``` git grep -l "^edition =" | xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;' ``` Second, manually verify that all Cargo.toml files have changed, and nothing else has changed. Third, run cargo fmt again. 2025-07-23T14:58:47Z Nick Mathewson nickm@torproject.org 2025-06-11T12:02:39Z urn:sha1:ca2eae597953483df799ca32452cf384d14c0236 2025-05-22T09:05:31Z Lionel Goffaux lionel.goffaux@unamur.be 2025-05-22T09:05:31Z urn:sha1:e5653df87971650d356dc9fa7e0e3570df44d504 2025-05-08T09:34:11Z Lionel Goffaux lionel.goffaux@unamur.be 2025-05-08T09:34:11Z urn:sha1:d11b1556751c9e10850c9cad7c1f52aaeb2debec 2025-05-06T22:34:17Z Nick Mathewson nickm@torproject.org 2025-04-30T11:59:47Z urn:sha1:efcca717bd3b90fa29bb0421eeb936f247671549 Now instead of using CryptState for everything, we have specific types for each role and direction of crypto. This turned up a harmless-so-far bug in our onion service code: as an onion service, we were using _client_ crypto layers to respond to a client request. That's not correct, and wouldn't have worked with CGO. Instead, we need to use relay crypto layers, wrapped as client layers. Closes #1975. 2025-05-06T22:34:17Z Nick Mathewson nickm@torproject.org 2025-04-30T00:59:07Z urn:sha1:297aa8027f7528605fe5bf2097f3474d9ba3eef9 The purpose of the trait was to parameterize the tor1 cell crypto on the different possible relay cell layouts. It made sense to have this trait when we thought we would implement the new cell layout for prop340 (packed-and-fragmented) well before we implemented CGO. But it now appears all but certain that CGO will land long before we make any more headway on prop340. Therefore, it doesn't make sense to carry the ability to customize `tor1` for other relay cell layouts. Removing this trait saves a fair bit of complexity. 2025-05-06T22:34:17Z Nick Mathewson nickm@torproject.org 2025-04-30T00:26:15Z urn:sha1:a50692cd37f5e35182b823c67defc5e6cd8810be This changes the code to copy a SendmeTag rather than returning a slice. This isn't actually a big change: sending a slice already required 16 bytes (on 64-bit platforms), so sending a SendmeTag around isn't a big deal. We rely extensively on the compiler's ability to optimize away all the checking in code like this: ``` let slice: &[u8]; let a: [u8;N] = slice[0..N].try_into().expect("Nope"); ``` I've spot-checked it somewhat with "cargo-show-asm", but it could use more thorough checking. Closes #1956. 2025-05-06T22:34:17Z Nick Mathewson nickm@torproject.org 2025-04-29T21:19:51Z urn:sha1:de696fdaf992f2ab92b886b2d42b7eae86b58836 This lets us use `Aes128Dec` and `Aes128Enc` in place of plain old `Aes128`, which can be less space-efficient depending on the back-end.