| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | 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 | 6 | -0/+16 | |
| |/ | | | | | 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 | |
| | | ||||||
| * | arti: Clarify what the client is supposed to do with the hsc key output. | Gabriela Moldovan | 2024-09-19 | 1 | -0/+8 | |
| | | ||||||
| * | arti: Document that "arti hsc" is experimental. | Gabriela Moldovan | 2024-09-19 | 1 | -0/+3 | |
| | | ||||||
| * | arti: Omit the optional --key-type argument from the docs. | Gabriela Moldovan | 2024-09-19 | 1 | -1/+1 | |
| | | | | | | | By default `--key-type` is set to `restricted-discovery` so it can omitted from these examples (omitting it makes the usage a bit clearer IMO). | |||||
| * | arti: Document the commands for key removal and rotation. | Gabriela Moldovan | 2024-09-19 | 1 | -1/+41 | |
| | | ||||||
| * | arti: Add hsc key subcommand, deprecate hsc get-key. | Gabriela Moldovan | 2024-09-18 | 1 | -5/+5 | |
| | | | | | | | | | | | I am deprecating the old `hsc get-key` subcommand in favor of the new `hsc key get` subcommand. This is because I plan to implement the rest of the key management functionality (key deletion, rotation, etc.) as subcommands of the `hsc key` command. The alternative would be to add a new distinct top-level `hsc rotate-key`, `hsc remove-key`, etc. subcommand alongside the existing `hsc get-key` command (which IMO is less nice than the alternative I'm proposing). | |||||
| * | 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 | |||||
| | * | | Update s101 numbers for Q2 2024 | Alexander Færøy | 2024-07-08 | 1 | -0/+26 | |
| | | | | ||||||
| * | | | rpc-draft: move cancel method to connection object. | Nick Mathewson | 2024-09-11 | 1 | -1/+1 | |
| | | | | ||||||
| * | | | rpc: Add a "client implementation strategies" section. | Nick Mathewson | 2024-09-11 | 1 | -1/+24 | |
| | | | | ||||||
| * | | | rpc: Document pipelining and concurrency. | Nick Mathewson | 2024-09-11 | 1 | -2/+15 | |
| | | | | ||||||
| * | | | rpc: Add a "Cancelled" code to our docs. | Nick Mathewson | 2024-09-11 | 1 | -0/+1 | |
| | | | | ||||||
| * | | | rpc: Replace strong/weak objectIds with reference/handle again | Nick Mathewson | 2024-09-11 | 1 | -5/+18 | |
| | | | | | | | | | | | | | | | | Diziet prefers this terminology; we'll defer a reckoning here till #849 is resolved. | |||||
| * | | | rpc-draft: Adopt a stricter-but-looser rule for anti-framing defense | Nick Mathewson | 2024-09-11 | 1 | -13/+46 | |
| | | | | | | | | | | | | | | | | | | | | | | Instead of saying "no errors before authentication", we now say "no syntax errors ever." This should be easier to implement. | |||||
| * | | | rpc-draft: A few more tweaks based on review. | Nick Mathewson | 2024-09-11 | 1 | -10/+12 | |
| | | | | ||||||
| * | | | Several rpc-draft suggestions from diziet. | Nick Mathewson | 2024-09-11 | 1 | -11/+22 | |
| | | | | ||||||
| * | | | rpc-meta: Note that the appendix is obsolete. | Nick Mathewson | 2024-09-11 | 1 | -0/+3 | |
| | | | | ||||||
| * | | | rpc-meta: Note that most listed requests are hypothetical | Nick Mathewson | 2024-09-11 | 1 | -0/+4 | |
| | | | | ||||||
| * | | | rpc-meta: remove example apis section | Nick Mathewson | 2024-09-11 | 1 | -58/+0 | |
| | | | | | | | | | | | | | (This is obsoleted by arti-rpc-client-core.) | |||||
| * | | | rpc-meta: update cancellation to latest thinking | Nick Mathewson | 2024-09-11 | 1 | -16/+6 | |
| | | | | ||||||
| * | | | rpc-meta: Tweaks to "authentication" section. | Nick Mathewson | 2024-09-11 | 1 | -5/+10 | |
| | | | | ||||||
| * | | | rpc-meta: clarify current method name rules. | Nick Mathewson | 2024-09-11 | 1 | -8/+9 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | Notably, identifiers SHOULD be C identifiers, and everything has a namespace. Reserve "rpc" as a namespace for things that were previously unnamespaced. | |||||
| * | | | rpc-meta: Light edits to parameter description. | Nick Mathewson | 2024-09-11 | 1 | -3/+3 | |
| | | | | ||||||
| * | | | rpc-meta: Rewrite and move documentation on object semantics. | Nick Mathewson | 2024-09-11 | 1 | -32/+117 | |
| | | | | | | | | | | | | | | | | This is probably still far too informal, but it is better than our previous documentation. | |||||
| * | | | rpc-meta: clarify status of Sessions. | Nick Mathewson | 2024-09-11 | 1 | -0/+7 | |
| | | | | | | | | | | | | | | | | (Note what isn't implemented, and one more kind of authentication we'll likely build someday.) | |||||
| * | | | rpc-meta: rewrite front matter | Nick Mathewson | 2024-09-11 | 1 | -29/+38 | |
| | | | | ||||||
| * | | | rpc-meta: Add a top-level heading, and shift other headings | Nick Mathewson | 2024-09-11 | 1 | -35/+37 | |
| | |/ |/| | | | | | (Markdown convention deprecates having more than one top-level heading.) | |||||
| * | | Fix typos | Dimitris Apostolou | 2024-09-03 | 2 | -3/+3 | |
| | | | ||||||
| * | | Sponsor 101 -> Project 101. | Alexander Færøy | 2024-09-02 | 1 | -2/+2 | |
| | | | | | | | | | See: tpo/team#313. | |||||
| * | | Merge branch 'torclient-doc' into 'main' | gabi-250 | 2024-08-15 | 1 | -0/+111 | |
| |\ \ | | | | | | | | | | | | | doc/dev/notes: keymgr-porcelain: Add note about moving keymgr functions out of TorClient. See merge request tpo/core/arti!2314 | |||||
| | * | | doc/dev/notes: keymgr-porcelain: Add note about alternative API. | Gabriela Moldovan | 2024-08-14 | 1 | -0/+12 | |
| | | | | ||||||
| | * | | doc/dev/notes: keymgr-porcelain: Add note about moving keymgr functions out ↵ | Gabriela Moldovan | 2024-08-06 | 1 | -0/+99 | |
| | | | | | | | | | | | | | | | | | | | of TorClient. This would a possible long-term fix for #1496. | |||||
| * | | | dov/dev/notes: Add note about live reloads in restricted discovery mode. | Gabriela Moldovan | 2024-08-12 | 1 | -0/+243 | |
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This describes a couple of options for extending the config reloading logic to support watching for changes in the `restricted_disovery.key_dirs` directories. Note: the options we have here are, in a sense, two extremes * one is about refactoring some of the existing code into a reusable component, and leaving most of the configuration logic unchanged * the other involves rethinking the entire config watching/reloading mechanism to support watching for changes in arbitrary directories I am leaning towards the simpler option, because I'm not sure the other one is worth the added complexity (we currently only have a single use case for it). | |||||
| * | | doc: Add arti hsc subcommand docs to doc/hsc.md. | Gabriela Moldovan | 2024-08-05 | 1 | -0/+28 | |
| | | | | | | | | | | | This also makes the `tests/testcases/hsc/hsc.md` test case a symlink to `doc/hsc.md`. | |||||
| * | | rpc: Remove RpcError data field and use Report | Nick Mathewson | 2024-07-25 | 1 | -26/+44 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | Per discussion, this field isn't really specified in a way that lets us fill it sensibly at the moment. So for now, we're going to just omit it. Additionally, we said that we'd Report on our errors; this branch changes the implementation of RpcError to do that. Question: Will the blanket implementation for Into<RpcError> make it harder to re-add a Data field later on if we want to do so? | |||||
 |
index : mirrors/arti.git | |
| mirror of https://gitlab.torproject.org/tpo/core/arti |
| summaryrefslogtreecommitdiff |