summaryrefslogtreecommitdiff
path: root/doc/dev/notes
Commit message (Collapse)AuthorAgeFilesLines
* Abolish now-done plans for encoded authcertsIan Jackson2026-01-151-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 commentIan Jackson2026-01-151-22/+0
| | | | This probably isn't going to happen, but let's keep the idea in-tree.
* tor-netdoc: EncodedAuthCert: move/tidy rationale informationIan Jackson2026-01-151-53/+0
| | | | | Move the information which still seems relevant out of the plan document.
* authcert-in-consensus: Allow the `fingerprint` anomalyIan Jackson2026-01-121-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 refsIan Jackson2026-01-121-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 proposalIan Jackson2026-01-121-45/+67
|
* authcert-in-consensus: Improve, clarify, xref requirementsIan Jackson2026-01-121-13/+9
|
* authcert-in-consensus: Fix intro wording and semantic botchesIan Jackson2026-01-121-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 typoIan Jackson2026-01-121-1/+1
|
* Notes about netdoc shift/reduce conflicts and authcert in netstatusIan Jackson2026-01-121-0/+139
|
* doc/dev/notes: Say we might want buffering on the inner MPSCsGabriela Moldovan2025-12-111-4/+7
|
* doc/dev/notes: Say that ConfluxController may be folded into StreamReactorGabriela Moldovan2025-12-111-1/+4
|
* doc/dev/notes: Add more details on the client sideGabriela Moldovan2025-12-111-7/+198
|
* doc/dev/notes: Say that the split StreamMap design is TBDGabriela Moldovan2025-12-111-4/+4
|
* doc/dev/notes: Clarify the parts that apply to both stream handling designsGabriela Moldovan2025-12-111-5/+6
|
* doc/dev/notes: Move clarification closer to the diagramGabriela Moldovan2025-12-111-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 taskGabriela Moldovan2025-12-111-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 Moldovan2025-12-101-22/+22
| | | | | As suggested in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3533#note_3305914
* doc/dev/notes: Add note on relay confluxGabriela Moldovan2025-12-081-0/+383
| | | | Closes #2273
* doc: add note about relays enforcing proto recommendationsSteven Engler2025-10-201-0/+9
|
* doc: Add relay task dev notesDavid Goulet2025-10-141-0/+208
| | | | | | Closes #2216 Signed-off-by: David Goulet <[email protected]>
* Merge branch 'describe-channel-padding' into 'main'Nick Mathewson2025-10-061-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 cellsNick Mathewson2025-10-021-1/+6
| |
| * circuit-padding: Note interactions with existing channel padding.Nick Mathewson2025-10-011-0/+10
| |
| * circuit-padding.md: Describe how per-channel padding will work.Nick Mathewson2025-10-011-0/+50
| |
* | doc/dev/notes: Add note on tor-proto cell validation.gabi-2502025-10-021-0/+236
|/ | | | Closes #2177
* Note replace difficultiesMike Perry2025-09-251-1/+3
|
* Note about framework consolidationMike Perry2025-09-251-0/+9
|
* Relocate framework section after intended usageMike Perry2025-09-251-8/+8
|
* Note about current replace flag implementationMike Perry2025-09-241-0/+8
|
* Clarify congestion control interactionsMike Perry2025-09-241-2/+13
|
* Clarify where latency defenses belongMike Perry2025-09-241-4/+8
|
* NN noteMike Perry2025-09-241-0/+3
|
* Add note about threat model scopeMike Perry2025-09-241-0/+11
|
* repeat that this document is current as of sept 2025Mike Perry2025-09-221-2/+2
|
* Clarifications and changes to padding docMike Perry2025-09-181-75/+201
|
* circuit-padding note: Different approach for blocked channelsNick Mathewson2025-09-151-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 Mathewson2025-09-111-0/+11
|
* circuit-padding: describe the current behavior for limiting padding cells.Nick Mathewson2025-09-111-9/+18
|
* circuit-padding: Update discussion of CC+padblocking.Nick Mathewson2025-09-111-6/+14
|
* circuit-padding: Clarify what a control message is, in artispeak.Nick Mathewson2025-09-111-2/+3
|
* circuit-padding.md: Make "bypass" behavior consider target hops.Nick Mathewson2025-09-101-6/+13
|
* circuit-padding.md: Correct explanation of our "bypass" behavior.Nick Mathewson2025-09-101-2/+2
|
* circuit-padding.md: Correct and explain our actual "replace" behavior.Nick Mathewson2025-09-101-9/+26
|
* circuit-padding.md: Add some notes from discussion.Nick Mathewson2025-09-041-2/+16
|
* Design note for the status quo of how padding might work.Nick Mathewson2025-09-031-0/+238
|
* Merge branch 'relay-reactor-design' into 'main'gabi-2502025-08-121-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 Moldovan2025-08-111-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.mdhjrgrn2025-08-071-0/+169
|/
* conflux-sketch: spelling fix.Nick Mathewson2025-07-091-1/+1
|