summaryrefslogtreecommitdiff
path: root/doc/dev/notes
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Typo fixes (automatic and hand-verified)Nick Mathewson2025-07-091-1/+1
| | | | Made with https://crates.io/crates/typos-cli
* tor-hsservice: Initial parts of PowManager.Wesley Aptekar-Cassels2025-05-271-10/+5
| | | | | | | This adds PowManager, as described in doc/dev/notes/service-side-pow.md, hooks it into IptManager and Publisher, and adds code to publish and rotate seeds, and to keep a updated list of Verifier instances for currently active seeds.
* fix: fix typosTobias Stoeckmann2025-04-251-1/+1
| | | | Typos found with codespell
* Address review - revert lint changes other than MD012hashcatHitman2025-04-081-48/+41
| | | | | A lot of these lints are better off agreed upon through policy and enforced globally.
* dev doc: Replaced outdated referenced to KeystoreSweeperhashcatHitman2025-04-061-3/+4
| | | | | | | | | | | | | | As of commit `0db0b6ede6ddba88e9a270a3e07587fefaab6fb4`, `crates/tor-hsservice/src/svc/keystore_sweeper.rs` was deleted and the key deletion was moved to `crates/tor-hsservice/src/svc/publish/reactor.rs`. As of commit `bebb6bdc6e15f42a3e1de7b3a4a68aa16f815294`, `crates/tor-hsservice/src/svc/publish/reactor.rs` was moved to `crates/tor-hsservice/src/publish/reactor.rs`, which is where it resides as of writing this. Whoever ends up being the one to work on this will probably appreciate having a more relevant reference point.
* dev doc: Respect Markdown lints in state-management-cli.mdhashcatHitman2025-04-061-45/+47
| | | | | | | | Fixes all the lints caught by the markdownlint extension in the file `doc/dev/notes/state-management-cli.md`, with the exception that MD024 is set to have `siblings_only` enabled, since it makes sense to allow here. It would be nice to set up a global markdownlint configuration some time, but that might be tricky.
* Deprecate --onion-name; introduce --onion-addressdisha2025-03-121-1/+1
|
* doc: Add Conflux sketch dev notesDavid Goulet2025-02-051-0/+141
| | | | Signed-off-by: David Goulet <[email protected]>
* tor-hsservice: Add more notes about publisher_update_tx.Wesley Aptekar-Cassels2025-01-161-1/+3
|
* tor-hsservice: Clarify PowManager publisher_update_tx.Wesley Aptekar-Cassels2025-01-161-0/+2
|
* tor-hsservice: Remove impl Clone for PowManager.Wesley Aptekar-Cassels2025-01-161-2/+0
| | | | Now that it's not in a Arc internally it shouldn't have this.
* tor-hsservice: Update PowManager persistence plan.Wesley Aptekar-Cassels2025-01-161-7/+19
|
* tor-hsservice: Make PowManager not use internal Arc.Wesley Aptekar-Cassels2025-01-161-4/+4
| | | | | | | | | | Per review feedback: > We have discovered that as a general rule of thumb, it is a good idea > to expose the `Arc`. This has a number of advantages; for example, if a > caller wants a `Weak` for any reason, that's right there. The typical > pattern is for the constructor to return `Arc<Self>` and methods to take > `self: &Arc<Self>`.
* tor-hsservice: Make PoW seed expiration be per-TP.Wesley Aptekar-Cassels2025-01-161-7/+6
| | | | | | This is something we wanted to do in general for security reasons, and ad I was implementing I discovered that it actually makes the code simpler, rather than more complicated.
* tor-hsservice: Update notes about PowManager persistence.Wesley Aptekar-Cassels2025-01-161-1/+1
|
* tor-hsservice: Add KeyMgr and HsNickname to PowManager.Wesley Aptekar-Cassels2025-01-161-0/+6
| | | | | These are needed to allow the PowManager to get the blinded ID needed to construct a PoW verifier.
* tor-hsservice: Give PowManager its own update loop.Wesley Aptekar-Cassels2025-01-161-14/+19
|
* tor-hsservice: Make PowManager use Arc internally.Wesley Aptekar-Cassels2025-01-161-1/+3
| | | | It is cleaner to not force callers to wrap it.
* fix: fix typosDimitris Apostolou2025-01-062-2/+2
|