| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| | * | | cookie-sketch: Revise "in arti-rpc" section for clarity | Nick Mathewson | 2024-10-21 | 1 | -6/+12 | |
| | | | | | | | | | | | | | In particular, specify which methods are invoked on which objects. | |||||
| | * | | rpc-cookie-sketch: Clarifications from @diziet | Nick Mathewson | 2024-10-21 | 1 | -6/+7 | |
| | | | | ||||||
| | * | | cookie-sketch: More security concerns on addr_canonical | Nick Mathewson | 2024-10-21 | 1 | -0/+13 | |
| | | | | ||||||
| | * | | cookie-sketch: Use a separate set of methods for cookie-auth. | Nick Mathewson | 2024-10-21 | 1 | -10/+16 | |
| | | | | ||||||
| | * | | cookie-sketch: Describe use of TupleHash | Nick Mathewson | 2024-10-21 | 1 | -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 Mathewson | 2024-10-21 | 1 | -5/+12 | |
| | | | | ||||||
| | * | | cookie-sketch: "nonce", not "secret". | Nick Mathewson | 2024-10-21 | 1 | -3/+3 | |
| | | | | ||||||
| | * | | RPC cookie authentication spec sketch. | Nick Mathewson | 2024-10-21 | 1 | -0/+81 | |
| | |/ | | | | | | | Part of #1521. | |||||
| * | | Merge branch 'inet_not_tcp' into 'main' | David Goulet | 2024-10-22 | 1 | -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 Mathewson | 2024-10-17 | 1 | -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 guarantees | Nick Mathewson | 2024-10-21 | 1 | -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 format | Nick Mathewson | 2024-10-17 | 1 | -8/+16 | |
| | | ||||||
| * | rpc-connect: add some example connect strings. | Nick Mathewson | 2024-10-17 | 1 | -1/+32 | |
| | | ||||||
| * | rpc-connect: clarify that "embedded" is not final. | Nick Mathewson | 2024-10-17 | 1 | -0/+10 | |
| | | ||||||
| * | rpc-connect: unknown builtins are "decline". | Nick Mathewson | 2024-10-17 | 1 | -2/+2 | |
| | | ||||||
| * | rpc-connect: replace a "may" with a "must" | Nick Mathewson | 2024-10-17 | 1 | -1/+1 | |
| | | ||||||
| * | Apply suggestions about authentication/socket relationships. | Nick Mathewson | 2024-10-17 | 1 | -3/+6 | |
| | | ||||||
| * | rpc-connect-sketch: Slightly clarify escaping. | Nick Mathewson | 2024-10-17 | 1 | -5/+4 | |
| | | ||||||
| * | rpc-connect-sketch: Revise connect string spec. | Nick Mathewson | 2024-10-17 | 1 | -118/+130 | |
| | | ||||||
| * | rpc-connect-sketch: Revise search-order-and-config section | Nick Mathewson | 2024-10-17 | 1 | -38/+76 | |
| | | ||||||
| * | rpc-connect-sketch: Add suggested "security concerns" section. | Nick Mathewson | 2024-10-17 | 1 | -1/+34 | |
| | | ||||||
| * | rpc-connect-sketch: Add suggested clarifications about cookie file. | Nick Mathewson | 2024-10-17 | 1 | -1/+16 | |
| | | ||||||
| * | rpc-connect-sketch: Remove file type indicator. | Nick Mathewson | 2024-10-17 | 1 | -3/+0 | |
| | | ||||||
| * | rpc-connect-sketch: Classify our previously-undecided error cases | Nick Mathewson | 2024-10-17 | 1 | -6/+7 | |
| | | ||||||
| * | rpc-connect-sketch: call setuid-detection nice-to-have. | Nick Mathewson | 2024-10-17 | 1 | -0/+1 | |
| | | ||||||
| * | RPC: Sketch for how connect strings work | Nick Mathewson | 2024-10-17 | 1 | -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 Goulet | 2024-10-16 | 1 | -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 convention | Nick Mathewson | 2024-10-09 | 1 | -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 Mathewson | 2024-10-09 | 1 | -1/+1 | |
| | | | ||||||
| * | | rpc-draft: clarify how we should handle error changes. | Nick Mathewson | 2024-10-09 | 1 | -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` field | Nick Mathewson | 2024-10-09 | 1 | -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 Error | Nick Mathewson | 2024-10-09 | 1 | -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 Mathewson | 2024-10-07 | 1 | -2/+1 | |
| | | ||||||
| * | Merge branch 'rpc-forward-compat' into 'main' | Nick Mathewson | 2024-10-03 | 1 | -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_features | Nick Mathewson | 2024-10-03 | 1 | -1/+5 | |
| | | | ||||||
| | * | rpc-meta-draft: Use SHOULD NOT instead of USUALLY NOT RECOMMENDED | Nick Mathewson | 2024-10-03 | 1 | -2/+1 | |
| | | | | | | | | | AIUI they mean the same thing | |||||
| | * | rpc-meta-draft: describe rules for remembering feature support | Nick Mathewson | 2024-10-03 | 1 | -0/+20 | |
| | | | | | | | | | From a suggestion from @diziet | |||||
| | * | rpc-meta-draft: describe feature namespacing. | Nick Mathewson | 2024-10-03 | 1 | -2/+12 | |
| | | | ||||||
| | * | rpc-meta-draft: describe compatibility rules and mechanisms | Nick Mathewson | 2024-09-30 | 1 | -3/+79 | |
| | | | | | | | | | | | | | This tries to memorialize the mechanism that @diziet and I came up with and memorialized on #1634. Once this is merged I can implement it. | |||||
| * | | doc/dev: Rename client authorization to restricted discovery. | Gabriela Moldovan | 2024-10-03 | 3 | -4/+4 | |
| | | | | | | | | | | | | | This renames "client auth" to "restricted discovery" where appropriate. Closes #1476 | |||||
| * | | doc: Note that client authorization was renamed. | Gabriela Moldovan | 2024-10-03 | 5 | -0/+14 | |
| |/ | | | | | This adds a note mentioning the new "restricted discovery" terminology to the various docs that talk about client authorization. | |||||
| * | rpc-meta-draft.md: correct some minor typos | Jim Newsome | 2024-09-25 | 1 | -7/+7 | |
| | | ||||||
| * | Merge branch 'mq-tidy' into 'main' | David Goulet | 2024-09-17 | 1 | -172/+8 | |
| |\ | | | | | | | | | memquota: be more firm about avoiding panics, and tidy up docs See merge request tpo/core/arti!2404 | |||||
| | * | memory-limit.md: Make the rubric accurate | Ian Jackson | 2024-09-10 | 1 | -8/+4 | |
| | | | | | | | | | And remove the rest of the now-obsolete text. | |||||
| | * | tor-memquota: Use clippy::arithmetic_side_effects, against panics | Ian Jackson | 2024-09-10 | 1 | -6/+0 | |
| | | | | | | | | | | | | | This detect possibly-panicking operations. Empirically this lint seems rather better now. | |||||
| | * | memory-limit: Fix heading depth for cache discussions | Ian Jackson | 2024-09-10 | 1 | -4/+4 | |
| | | | ||||||
| | * | memory-limit.md: Remove obsolete overview docs | Ian Jackson | 2024-09-10 | 1 | -31/+0 | |
| | | | | | | | | | All of this is now documented in the lib.rs. | |||||
| | * | tor-memquota: Move some information into the proper docs | Ian Jackson | 2024-09-10 | 1 | -2/+0 | |
| | | | | | | | | | | | This sentence is very important piece of overall explanation, but didn't make it into the crate level docs. | |||||
| | * | memory-limit.md: Remove obsolete docs of implemented channel facility | Ian Jackson | 2024-09-10 | 1 | -121/+0 | |
| | | | | | | | | | All of this is now implemented. Delete the obsolete sketch. | |||||
| * | | Merge branch 's101-2024-q2' into 'main' | Alexander Hansen Færøy | 2024-09-17 | 1 | -0/+26 | |
| |\ \ | | | | | | | | | | | | | Update s101 numbers for Q2 2024 See merge request tpo/core/arti!2245 | |||||
 |
index : mirrors/arti.git | |
| mirror of https://gitlab.torproject.org/tpo/core/arti |
| summaryrefslogtreecommitdiff |