summaryrefslogtreecommitdiff
path: root/doc/dev
Commit message (Collapse)AuthorAgeFilesLines
...
* | 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.
* Merge branch 'ticket1743_02' into 'main'David Goulet2025-01-161-1/+0
|\ | | | | | | | | Implement congestion control from prop324 See merge request tpo/core/arti!2675
| * crates: Remove tor-congestionDavid Goulet2025-01-161-1/+0
| | | | | | | | | | | | | | | | | | Crate is unused and most of its code will be reworked and folded into tor-proto in the future commit with the Congestion Control work. Related #534 Signed-off-by: David Goulet <[email protected]>
* | Merge branch 'rpc-connect-clarify' into 'main'Nick Mathewson2025-01-161-3/+6
|\ \ | |/ |/| | | | | | | | | rpc: Clarify and fix some issues surrounding relative paths. Closes #1748 and #1749 See merge request tpo/core/arti!2712
| * rpc-book: Decline non-absolute paths in our default paths.Nick Mathewson2025-01-151-1/+3
| | | | | | | | Closes #1748.
| * rpc-book: Clarify that relative unix paths should abort.Nick Mathewson2025-01-151-2/+3
| | | | | | | | Closes #1749.
* | Merge branch 'rpc-renaming-1' into 'main'Nick Mathewson2025-01-151-1/+1
|\ \ | | | | | | | | | | | | | | | | | | arti-rpcserver: Rename MethodNotFound to NoSuchMethod. Closes #1500 See merge request tpo/core/arti!2714
| * | rpc-meta-draft.md: Fix a dangling reference to RpcMethodNotFound.Nick Mathewson2025-01-151-1/+1
| | |
* | | rpc: Document windows USER_DEFAULT connect point.Nick Mathewson2025-01-151-0/+7
|/ /
* | Merge branch 'rpc-cookie' into 'main'Nick Mathewson2025-01-152-11/+9
|\ \ | | | | | | | | | | | | | | | | | | RPC: Implement cookie authentication Closes #1529 See merge request tpo/core/arti!2702
| * | rpc: consolodate naming of "inherent" auth.Nick Mathewson2025-01-151-9/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | We don't want to call this "unix path" anywhere, since it corresponds to _any_ case where the ability to negotiate a successful connection means that the client is authorized. We also don't want to call it "none": The authentication is inherent to the connection, not nonexistent.
| * | rpc: Tweak cookie protocol to bind both nonces.Nick Mathewson2025-01-151-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously participants in the cookie protocol only bound the peer nonce in their MACs. With this change, they bind both nonces. This change is _probably_ not necessary for security, but it can't hurt. It follows a general principle that Adam Langley told me a long time ago: you won't regret binding more, but you might regret binding less.
| * | rpc-cookie-sketch: typo fix.Nick Mathewson2025-01-151-1/+1
| |/
* / Update P101 numbers for Q4-2024.Alexander Færøy2025-01-151-0/+26
|/
* RPC spec: specify banner format.Nick Mathewson2025-01-092-1/+28
| | | | | | | | | | | | | See #1753. This banner message will give the client a clear signal that the server is ready, so that the client will know that it can read files (such as a cookie file) written by the server. (We can't use "is the port bound" as a way to signal that the server is ready, since the server needs to bind the port in order to determine that there isn't another server running... which it needs to do before it can write an rpc cookie file.)
* fix: fix typosDimitris Apostolou2025-01-063-7/+7
|
* rpc: Clarify listen_defaults behavior.Nick Mathewson2024-12-191-1/+1
|
* arti::rpc: Rename "overrides" field and type.Nick Mathewson2024-12-191-1/+1
| | | | | Per discussion with Diziet, these aren't really "overriding" anything; they're the actual options for a single connect point.
* Merge branch 'dirauth-0' into 'main'Ian Jackson2024-12-181-0/+242
|\ | | | | | | | | Initial sketch of dirauth structure See merge request tpo/core/arti!2635
| * dirauth sketch: discuss offline KS_dirauth_id_*Ian Jackson2024-12-171-0/+3
| |
| * dirauth sketch: mention shared random protocolIan Jackson2024-12-171-0/+1
| |
| * dirauth sketch: dircache, expand a bitIan Jackson2024-12-171-0/+5
| | | | | | | | | | From https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2635#note_3131826
| * dirauth sketch: dircache: mention connection to relaysIan Jackson2024-12-171-1/+2
| |
| * dirauth deployment plans: Updates apropos commentsIan Jackson2024-12-171-5/+14
| |
| * dirauth-sketch: Fix typoIan Jackson2024-12-171-1/+1
| |
| * dirauth deployment plans: formattingIan Jackson2024-12-171-1/+4
| |
| * dirauth deployment plans: typosIan Jackson2024-12-171-2/+2
| |
| * dirauth deployment plans: fix formattingIan Jackson2024-12-171-3/+3
| |
| * dirauth deployment plans: detailed transition planIan Jackson2024-12-171-0/+129
| |
| * dirauth deployment plans: add rationale for pluginIan Jackson2024-12-171-0/+20
| |
| * dirauth deployment plans: fix some hard tabsIan Jackson2024-12-171-2/+2
| |
| * Initial sketch of dirauth structureIan Jackson2024-12-171-0/+71
| |
* | docs: Update PoW proposal with lock hierarchy.Wesley Aptekar-Cassels2024-12-171-0/+4
| |
* | docs: Fix proposed PoW struct visibility.Wesley Aptekar-Cassels2024-12-171-1/+1
| |
* | docs: Update proposed PoW locking and add explanation.Wesley Aptekar-Cassels2024-12-171-10/+56
| |
* | docs: Move PoW next_expiration_time into PowVerifiers.Wesley Aptekar-Cassels2024-12-171-1/+1
| |
* | docs: Add note about ReplayLog cleanup.Wesley Aptekar-Cassels2024-12-171-1/+10
| |
* | docs: Update PoW replay log type.Wesley Aptekar-Cassels2024-12-171-1/+1
| |
* | docs: Put all datastructures for PoW seeds in the same struct.Wesley Aptekar-Cassels2024-12-171-5/+7
| | | | | | | | | | This will prevent problems when trying to acquire multiple locks to update this data in a consistent way.
* | docs: s/replay_log_dir/pow_replay_log_dir/ for clarity.Wesley Aptekar-Cassels2024-12-171-1/+1
| |
* | docs: Add note about ReplayLog rotation.Wesley Aptekar-Cassels2024-12-171-0/+1
| |
* | docs: Add note about PowManagerRecord and StateRecord.Wesley Aptekar-Cassels2024-12-171-0/+1
| |