| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | arti-dirauth: Move plugin spec to crate subdir | Ian Jackson | 2026-07-23 | 1 | -250/+0 |
| | | |||||
| * | Use new TimeRangeBound name throughout the tree | Ian Jackson | 2026-07-16 | 1 | -1/+1 |
| | | |||||
| * | doc/dev/note: Clarify what rejecting a stream request entails | Gabriela Moldovan | 2026-06-18 | 1 | -4/+11 |
| | | |||||
| * | Add a rough plan for relay incoming stream handling | Gabriela Moldovan | 2026-06-18 | 1 | -0/+609 |
| | | | | | Closes #2574 | ||||
| * | authority-plugin: Say we use the netdoc metaformat. | Nick Mathewson | 2026-06-17 | 1 | -1/+2 |
| | | |||||
| * | authority-plugin: Say what NICKNAME is for. | Nick Mathewson | 2026-06-17 | 1 | -1/+1 |
| | | |||||
| * | authority-plugin: Specify error behavior | Nick Mathewson | 2026-06-17 | 1 | -0/+12 |
| | | |||||
| * | authority-plugin: More suggestions from @diziet | Nick Mathewson | 2026-06-10 | 1 | -1/+9 |
| | | |||||
| * | authority-plugin: edits from @diziet | Nick Mathewson | 2026-06-10 | 1 | -8/+15 |
| | | |||||
| * | draft specification for authority plugin API | Nick Mathewson | 2026-06-10 | 1 | -0/+222 |
| | | |||||
| * | doc/dev/notes: A rough outline about how a vote is computed | Nick Mathewson | 2026-05-07 | 1 | -0/+134 |
| | | | | | | This should probably be the basis of a new section in the specification, but for now it's a start. | ||||
| * | Fix typos | Tobias Stoeckmann | 2026-03-24 | 3 | -11/+11 |
| | | | | | Typos found with codespell | ||||
| * | Fix word duplicate typos | Tobias Stoeckmann | 2026-03-15 | 2 | -2/+2 |
| | | |||||
| * | Abolish now-done plans for encoded authcerts | Ian Jackson | 2026-01-15 | 1 | -81/+0 |
| | | | | | | | | The structural confusion hazard is now discussed extensively in torspec and referenced from the code. The proposal has been implemented. | ||||
| * | tor-netdoc: EncodedAuthCert: move future plans to a comment | Ian Jackson | 2026-01-15 | 1 | -22/+0 |
| | | | | | This probably isn't going to happen, but let's keep the idea in-tree. | ||||
| * | tor-netdoc: EncodedAuthCert: move/tidy rationale information | Ian Jackson | 2026-01-15 | 1 | -53/+0 |
| | | | | | | Move the information which still seems relevant out of the plan document. | ||||
| * | authcert-in-consensus: Allow the `fingerprint` anomaly | Ian Jackson | 2026-01-12 | 1 | -1/+1 |
| | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3565#note_3323304 https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/453#note_3323185 | ||||
| * | authcert-in-consensus: Fix some wrong intro item refs | Ian Jackson | 2026-01-12 | 1 | -2/+2 |
| | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3565#note_3323305 https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3565#note_3323306 | ||||
| * | authcert-in-consensus: Revised less-generic proposal | Ian Jackson | 2026-01-12 | 1 | -45/+67 |
| | | |||||
| * | authcert-in-consensus: Improve, clarify, xref requirements | Ian Jackson | 2026-01-12 | 1 | -13/+9 |
| | | |||||
| * | authcert-in-consensus: Fix intro wording and semantic botches | Ian Jackson | 2026-01-12 | 1 | -13/+12 |
| | | | | | | | | Firstly, this only applies to votes, not other kinds of nestatus. Secondly, we wrote "netstatus" a couple of times instead of "vote" which is very confusing. | ||||
| * | authcert-in-consensus: Fix typo | Ian Jackson | 2026-01-12 | 1 | -1/+1 |
| | | |||||
| * | Notes about netdoc shift/reduce conflicts and authcert in netstatus | Ian Jackson | 2026-01-12 | 1 | -0/+139 |
| | | |||||
| * | doc/dev/notes: Say we might want buffering on the inner MPSCs | Gabriela Moldovan | 2025-12-11 | 1 | -4/+7 |
| | | |||||
| * | doc/dev/notes: Say that ConfluxController may be folded into StreamReactor | Gabriela Moldovan | 2025-12-11 | 1 | -1/+4 |
| | | |||||
| * | doc/dev/notes: Add more details on the client side | Gabriela Moldovan | 2025-12-11 | 1 | -7/+198 |
| | | |||||
| * | doc/dev/notes: Say that the split StreamMap design is TBD | Gabriela Moldovan | 2025-12-11 | 1 | -4/+4 |
| | | |||||
| * | doc/dev/notes: Clarify the parts that apply to both stream handling designs | Gabriela Moldovan | 2025-12-11 | 1 | -5/+6 |
| | | |||||
| * | doc/dev/notes: Move clarification closer to the diagram | Gabriela Moldovan | 2025-12-11 | 1 | -6/+5 |
| | | | | | | | I am about to add some text that applies to both designs, so I want to move this closer to the diagram to avoid a confusing interleaving of text. | ||||
| * | doc/dev/notes: Say that we will have a single stream task | Gabriela Moldovan | 2025-12-11 | 1 | -20/+46 |
| | | | | | | For the initial implementation, we don't plan to split the read and write sides of the stream handling task. | ||||
| * | doc/dev/notes: Rename Stream{BWD,FWD} to Stream{Read,Write} | Gabriela Moldovan | 2025-12-10 | 1 | -22/+22 |
| | | | | | | As suggested in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3533#note_3305914 | ||||
| * | doc/dev/notes: Add note on relay conflux | Gabriela Moldovan | 2025-12-08 | 1 | -0/+383 |
| | | | | | Closes #2273 | ||||
| * | doc: add note about relays enforcing proto recommendations | Steven Engler | 2025-10-20 | 1 | -0/+9 |
| | | |||||
| * | doc: Add relay task dev notes | David Goulet | 2025-10-14 | 1 | -0/+208 |
| | | | | | | | Closes #2216 Signed-off-by: David Goulet <[email protected]> | ||||
| * | Merge branch 'describe-channel-padding' into 'main' | Nick Mathewson | 2025-10-06 | 1 | -0/+65 |
| |\ | | | | | | | | | circuit-padding.md: Describe how per-channel padding will work. See merge request tpo/core/arti!3302 | ||||
| | * | circuit-padding: correct how channel padding detects queued cells | Nick Mathewson | 2025-10-02 | 1 | -1/+6 |
| | | | |||||
| | * | circuit-padding: Note interactions with existing channel padding. | Nick Mathewson | 2025-10-01 | 1 | -0/+10 |
| | | | |||||
| | * | circuit-padding.md: Describe how per-channel padding will work. | Nick Mathewson | 2025-10-01 | 1 | -0/+50 |
| | | | |||||
| * | | doc/dev/notes: Add note on tor-proto cell validation. | gabi-250 | 2025-10-02 | 1 | -0/+236 |
| |/ | | | | Closes #2177 | ||||
| * | Note replace difficulties | Mike Perry | 2025-09-25 | 1 | -1/+3 |
| | | |||||
| * | Note about framework consolidation | Mike Perry | 2025-09-25 | 1 | -0/+9 |
| | | |||||
| * | Relocate framework section after intended usage | Mike Perry | 2025-09-25 | 1 | -8/+8 |
| | | |||||
| * | Note about current replace flag implementation | Mike Perry | 2025-09-24 | 1 | -0/+8 |
| | | |||||
| * | Clarify congestion control interactions | Mike Perry | 2025-09-24 | 1 | -2/+13 |
| | | |||||
| * | Clarify where latency defenses belong | Mike Perry | 2025-09-24 | 1 | -4/+8 |
| | | |||||
| * | NN note | Mike Perry | 2025-09-24 | 1 | -0/+3 |
| | | |||||
| * | Add note about threat model scope | Mike Perry | 2025-09-24 | 1 | -0/+11 |
| | | |||||
| * | repeat that this document is current as of sept 2025 | Mike Perry | 2025-09-22 | 1 | -2/+2 |
| | | |||||
| * | Clarifications and changes to padding doc | Mike Perry | 2025-09-18 | 1 | -75/+201 |
| | | |||||
| * | circuit-padding note: Different approach for blocked channels | Nick Mathewson | 2025-09-15 | 1 | -12/+21 |
| | | | | | | This documents the approach I've taken in #2169, which turned out to be way simpler than the other idea. | ||||
