| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 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. | ||||
| * | circuit-padding: document handling for guard padding on blocked channels. | Nick Mathewson | 2025-09-11 | 1 | -0/+11 |
| | | |||||
| * | circuit-padding: describe the current behavior for limiting padding cells. | Nick Mathewson | 2025-09-11 | 1 | -9/+18 |
| | | |||||
| * | circuit-padding: Update discussion of CC+padblocking. | Nick Mathewson | 2025-09-11 | 1 | -6/+14 |
| | | |||||
| * | circuit-padding: Clarify what a control message is, in artispeak. | Nick Mathewson | 2025-09-11 | 1 | -2/+3 |
| | | |||||
| * | circuit-padding.md: Make "bypass" behavior consider target hops. | Nick Mathewson | 2025-09-10 | 1 | -6/+13 |
| | | |||||
| * | circuit-padding.md: Correct explanation of our "bypass" behavior. | Nick Mathewson | 2025-09-10 | 1 | -2/+2 |
| | | |||||
| * | circuit-padding.md: Correct and explain our actual "replace" behavior. | Nick Mathewson | 2025-09-10 | 1 | -9/+26 |
| | | |||||
| * | circuit-padding.md: Add some notes from discussion. | Nick Mathewson | 2025-09-04 | 1 | -2/+16 |
| | | |||||
| * | Design note for the status quo of how padding might work. | Nick Mathewson | 2025-09-03 | 1 | -0/+238 |
| | | |||||
| * | Merge branch 'relay-reactor-design' into 'main' | gabi-250 | 2025-08-12 | 1 | -0/+491 |
| |\ | | | | | | | | | doc/dev/notes: relay-reactor: Add a relay reactor implementation sketch. See merge request tpo/core/arti!3146 | ||||
| | * | doc/dev/notes: relay-reactor: Add a relay reactor implementation sketch. | Gabriela Moldovan | 2025-08-11 | 1 | -0/+491 |
| | | | | | | | | | | | | | | | | | | | | | This is a rough sketch for the new relay tunnel reactor design. It also contains a proposed refactoring which would enable us to repurpose much of the existing tunnel reactor implementation. This is by no means final, and we might choose not to refactor the tunnel reactor until after we have an initial working (or quasi-working) version for the relay reactor. | ||||
| * | | doc: dev: notes: Add keys-integrity-check.md | hjrgrn | 2025-08-07 | 1 | -0/+169 |
| |/ | |||||
| * | conflux-sketch: spelling fix. | Nick Mathewson | 2025-07-09 | 1 | -1/+1 |
| | | |||||
