summaryrefslogtreecommitdiff
path: root/doc/dev
Commit message (Collapse)AuthorAgeFilesLines
...
| * rpc-connect-sketch: expand on defaults.Nick Mathewson2024-10-211-1/+20
| |
* | Merge branch 'p101-2024-q3' into 'main'Alexander Hansen Færøy2024-10-241-0/+26
|\ \ | | | | | | | | | | | | Update P101 numbers for Q3-2024. See merge request tpo/core/arti!2571
| * | Update P101 numbers for Q3-2024.Alexander Færøy2024-10-221-0/+26
| | |
* | | tor-circmgr: Clarify that using guarded for client rend is an exception.Gabriela Moldovan2024-10-241-0/+13
| | |
* | | doc/dev/notes/vanguards: Use the new circuit stem terminology.Gabriela Moldovan2024-10-241-25/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | "Circuit stubs" are now called "circuit stems". We are also replacing the STUB/STUB+ terminology (STUB/STUB+ circuits are now called NAIVE/GUARDED). Part of #1479
* | | Merge branch 'rpc-cookie-auth-sketch' into 'main'Nick Mathewson2024-10-222-0/+136
|\ \ \ | |/ / |/| | | | | | | | RPC cookie authentication spec sketch. See merge request tpo/core/arti!2440
| * | rpc-cookie: Formatting cleanup wrt `P`.Nick Mathewson2024-10-211-3/+3
| | |
| * | rpc-cookie: Make more text normative; defined a malformed cookie fileNick Mathewson2024-10-211-6/+11
| | |
| * | rpc-cookie: More naming consistencyNick Mathewson2024-10-211-8/+9
| | |
| * | rpc-sketches: Unify, clarify, and clean up socket_canonicalNick Mathewson2024-10-212-31/+32
| | |
| * | rpc-cookie-sketch: unify non-address field names.Nick Mathewson2024-10-211-9/+8
| | |
| * | rpc-cookie-sketch: re-order SADDR_USE and SADDR_VERIFY.Nick Mathewson2024-10-211-7/+8
| | |
| * | rpc-cookie-sketch: specify cookie IO failures.Nick Mathewson2024-10-211-0/+13
| | |
| * | cookie-sketch: Revise "in arti-rpc" section for clarityNick Mathewson2024-10-211-6/+12
| | | | | | | | | | | | In particular, specify which methods are invoked on which objects.
| * | rpc-cookie-sketch: Clarifications from @dizietNick Mathewson2024-10-211-6/+7
| | |
| * | cookie-sketch: More security concerns on addr_canonicalNick Mathewson2024-10-211-0/+13
| | |
| * | cookie-sketch: Use a separate set of methods for cookie-auth.Nick Mathewson2024-10-211-10/+16
| | |
| * | cookie-sketch: Describe use of TupleHashNick Mathewson2024-10-211-15/+17
| | | | | | | | | | | | | | | Also, rename values to S_MAC and C_MAC, and include SADDR_CANONICAL in messages.
| * | cookie-sketch: Use agreed-upon mitm prevention.Nick Mathewson2024-10-211-5/+12
| | |
| * | cookie-sketch: "nonce", not "secret".Nick Mathewson2024-10-211-3/+3
| | |
| * | RPC cookie authentication spec sketch.Nick Mathewson2024-10-211-0/+81
| |/ | | | | | | Part of #1521.
* | Merge branch 'inet_not_tcp' into 'main'David Goulet2024-10-221-5/+5
|\ \ | | | | | | | | | | | | | | | | | | general::SocketAddr: Say "inet" rather than "tcp" Closes #1701 See merge request tpo/core/arti!2554
| * | general::SocketAddr: Say "inet" rather than "tcp"Nick Mathewson2024-10-171-5/+5
| |/ | | | | | | | | | | | | | | | | | | "inet" makes more sense, since in principle these can also be used for udp, etc. Also making a corresponding change in rpc-connect-sketch.md, which uses this format. Closes #1701.
* / rpc-draft: Clarify and weaken cancel guaranteesNick Mathewson2024-10-211-9/+28
|/ | | | | | Part of #818. Tries to match the set of guarantees specified by @diziet on that ticket.
* rpc-connect-sketch: Clarify and restrict socket addr formatNick Mathewson2024-10-171-8/+16
|
* rpc-connect: add some example connect strings.Nick Mathewson2024-10-171-1/+32
|
* rpc-connect: clarify that "embedded" is not final.Nick Mathewson2024-10-171-0/+10
|
* rpc-connect: unknown builtins are "decline".Nick Mathewson2024-10-171-2/+2
|
* rpc-connect: replace a "may" with a "must"Nick Mathewson2024-10-171-1/+1
|
* Apply suggestions about authentication/socket relationships.Nick Mathewson2024-10-171-3/+6
|
* rpc-connect-sketch: Slightly clarify escaping.Nick Mathewson2024-10-171-5/+4
|
* rpc-connect-sketch: Revise connect string spec.Nick Mathewson2024-10-171-118/+130
|
* rpc-connect-sketch: Revise search-order-and-config sectionNick Mathewson2024-10-171-38/+76
|
* rpc-connect-sketch: Add suggested "security concerns" section.Nick Mathewson2024-10-171-1/+34
|
* rpc-connect-sketch: Add suggested clarifications about cookie file.Nick Mathewson2024-10-171-1/+16
|
* rpc-connect-sketch: Remove file type indicator.Nick Mathewson2024-10-171-3/+0
|
* rpc-connect-sketch: Classify our previously-undecided error casesNick Mathewson2024-10-171-6/+7
|
* rpc-connect-sketch: call setuid-detection nice-to-have.Nick Mathewson2024-10-171-0/+1
|
* RPC: Sketch for how connect strings workNick Mathewson2024-10-171-0/+316
| | | | | This is based on conversations with Diziet, and is a followup from arti!2388 and arti!2429.
* Merge branch 'rpc_verb_methods' into 'main'David Goulet2024-10-161-0/+14
|\ | | | | | | | | | | | | rpc spec: Start to document method naming convention Closes #1678 See merge request tpo/core/arti!2539
| * rpc spec: Start to document method naming conventionNick Mathewson2024-10-091-0/+14
| | | | | | | | | | All but one of our current methods follows this convention, and we're about to rename it.
* | rpc spec: use valid JS syntax.Nick Mathewson2024-10-091-1/+1
| |
* | rpc-draft: clarify how we should handle error changes.Nick Mathewson2024-10-091-0/+11
| | | | | | | | | | | | | | This is based on a suggestion from @diziet, but edited to say that: - we will take this approach when possible, and that we're not making a categorical promise. - this approach only applies to stable fields.
* | rpc spec: Revise design for `error.data` fieldNick Mathewson2024-10-091-24/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | IIUC: Previously, `error.data` was meant to be the serialized error object from Arti. As such, it was specified to be deliberately unstable, and likely to change. This didn't seem like such great idea, especially as we started to come up with structured and stable data that we _did_ want to put in `error.data`. With this commit I'm taking a new approach to `error.data`. Specifically: * `error.data`, if present, is always an object. * Unlike before, it can have multiple keys. * The keys of `error.data` are always namespaced. * There is a requirement that documentation exist for every key in an`error.data` document, including the type, semantics, and stability of its values. There is also new "anticipated use of error.data" section to clarify our plans: * We plan to use error.data deliberately when it actually serves a purpose. * We don't plan to have an on-by-default serialization or Debug of every Arti error. (If we wanted an optional one, there is a short sketch of what it might look like.)
* | RPC spec: move the data field back into ErrorNick Mathewson2024-10-091-30/+25
|/ | | | | | This is *not* how we actually want the `data` field to behave! But moving it as a separate commit will make it easier to see what changes we do make.
* rpc spec: correct the name of a field.Nick Mathewson2024-10-071-2/+1
|
* Merge branch 'rpc-forward-compat' into 'main'Nick Mathewson2024-10-031-3/+112
|\ | | | | | | | | rpc-meta-draft: describe compatibility rules and mechanisms See merge request tpo/core/arti!2475
| * rpc-meta-draft: add TODO note about unsupported_featuresNick Mathewson2024-10-031-1/+5
| |
| * rpc-meta-draft: Use SHOULD NOT instead of USUALLY NOT RECOMMENDEDNick Mathewson2024-10-031-2/+1
| | | | | | | | AIUI they mean the same thing
| * rpc-meta-draft: describe rules for remembering feature supportNick Mathewson2024-10-031-0/+20
| | | | | | | | From a suggestion from @diziet