| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | | docs: Add note about ReplayLog cleanup. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -1/+10 | |
| | | | ||||||
| * | | docs: Update PoW replay log type. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -1/+1 | |
| | | | ||||||
| * | | docs: Put all datastructures for PoW seeds in the same struct. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -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-Cassels | 2024-12-17 | 1 | -1/+1 | |
| | | | ||||||
| * | | docs: Add note about ReplayLog rotation. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -0/+1 | |
| | | | ||||||
| * | | docs: Add note about PowManagerRecord and StateRecord. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -0/+1 | |
| | | | ||||||
| * | | docs: Adjust check_solve visibility. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -1/+1 | |
| | | | ||||||
| * | | docs: We want nonces to be unique, not solution bytes. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -1/+1 | |
| | | | ||||||
| * | | docs: Add details of ReplayLog to service side PoW notes. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -3/+29 | |
| | | | ||||||
| * | | docs: Update notes on service-side PoW | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -22/+24 | |
| | | | | | | | | | | | | | | | | | | | | | | | This makes a few major changes: * Removes the IptPowInstance type, instead moving that functionality to PowManager, using a RwLock. * Adds detail about the priority queue types / APIs * Makes all members of PowManager wrapped by a Mutex/RwLock, so that the caller doesn't need to worry about that. The caller will still likely need to put it in a Arc, though. | |||||
| * | | docs: Rework service side PoW draft. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -74/+93 | |
| | | | ||||||
| * | | docs: Add note on plan for service side PoW. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -0/+107 | |
| |/ | ||||||
| * | doc/dev/notes: cell-lifecycle: Say that stream management details are elided. | Gabriela Moldovan | 2024-11-21 | 1 | -0/+4 | |
| | | ||||||
| * | doc/dev/notes: cell-lifecycle: We only describe the unbounded buffers. | Gabriela Moldovan | 2024-11-21 | 1 | -3/+3 | |
| | | ||||||
| * | doc/dev/notes: cell-lifecycle: Say that the reactor awaits rather than blocks. | Gabriela Moldovan | 2024-11-21 | 1 | -1/+1 | |
| | | ||||||
| * | doc/dev/notes: cell-lifecycle: Describe the current state of things. | Gabriela Moldovan | 2024-11-20 | 1 | -0/+319 | |
| | | | | | | | | | | | | | | | | | | These are my notes and observations about the circuit and channel reactors. In hindsight, this whole document is just stating the "obvious"[^1], so I'm not sure if it's going to be useful for anyone else. Also, since this isn't part of the code docs or tor-proto crate-level docs, it's very likely to become outdated in the near future. At the end of the document, I also wrote a very rough KIST implementation plan based on the discussion from #1712. Closes #1747 [^1]: scare quotes because the "obvious" is only obvious after you've stared at the circ/chan reactors for a while | |||||
| * | doc/dev/notes: keymgr-certificates: Clarify how keymgr might generate the cert. | Gabriela Moldovan | 2024-11-14 | 1 | -2/+3 | |
| | | | | | | This is not necessarily set in stone, but it seems like a plausible way of going about this. | |||||
| * | doc/dev/notes: keymgr-certificates: Emphasize that we won't manage arbitrary ↵ | Gabriela Moldovan | 2024-11-14 | 1 | -3/+8 | |
| | | | | | certs. | |||||
| * | doc/dev/notes: keymgr-certificates: Abolish get_cert_entry. | Gabriela Moldovan | 2024-11-14 | 1 | -16/+0 | |
| | | | | | This also removes the reference to the `get_entry()` function. | |||||
| * | doc/dev/notes: keymgr-certificates: Allow the cert denotators to be absent. | Gabriela Moldovan | 2024-11-14 | 1 | -11/+9 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Update proposed renaming. | Gabriela Moldovan | 2024-11-14 | 1 | -28/+19 | |
| | | | | | | Based on our discussion in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2565#note_3129065 | |||||
| * | doc/dev/notes: keymgr-certificates: Apply key format clarifications from Diziet. | Gabriela Moldovan | 2024-11-14 | 1 | -0/+7 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Apply suggestions from Diziet. | gabi-250 | 2024-11-14 | 1 | -2/+2 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Clarify code docs. | Gabriela Moldovan | 2024-11-14 | 1 | -4/+8 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Fix typo. | Gabriela Moldovan | 2024-11-14 | 1 | -1/+1 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Remove unreadable chunk from intro. | Gabriela Moldovan | 2024-11-14 | 1 | -8/+3 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Remove unnecessary args. | Gabriela Moldovan | 2024-11-14 | 1 | -4/+0 | |
| | | | | | | We don't actually need a `KeyType` argument (`KeyTypes` are obtained from the `EncodableKey::key_type()` impl of the key/cert). | |||||
| * | doc/dev/notes: keymgr-certificates: Reorder args for clarity. | Gabriela Moldovan | 2024-11-14 | 1 | -4/+4 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Move subject key specifier to trait. | Gabriela Moldovan | 2024-11-14 | 1 | -2/+2 | |
| | | | | | This helps us cut down on the number of args in `get_*_and_cert()`. | |||||
| * | doc/dev/notes: keymgr-certificates: Say that cert paths are derived from key ↵ | Gabriela Moldovan | 2024-11-14 | 1 | -26/+39 | |
| | | | | | paths. | |||||
| * | doc/dev/notes: keymgr-certificates: Mention the uid we settled on in !2577. | Gabriela Moldovan | 2024-11-14 | 1 | -5/+5 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Remove outdated design. | Gabriela Moldovan | 2024-11-14 | 1 | -191/+33 | |
| | | | | | | | | | We decided to go with the second proposed design, so we can safely remove this one now. This also updates the introduction to summarize how we arrived at this design. | |||||
| * | doc/dev/notes: keymgr-certificates: Clarify confusing wording. | Gabriela Moldovan | 2024-11-14 | 1 | -3/+2 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Make the signing_key optionally present ↵ | Gabriela Moldovan | 2024-11-14 | 1 | -3/+37 | |
| | | | | | in keystore. | |||||
| * | doc/dev/notes: keymgr-certificates: Remove redundant fields from ↵ | Gabriela Moldovan | 2024-11-14 | 1 | -5/+0 | |
| | | | | | KeyCertificateSpecifier. | |||||
| * | doc/dev/notes: keymgr-certificates: Clarify what KeyType/CertType is about. | Gabriela Moldovan | 2024-11-14 | 1 | -0/+7 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Remove misleading statement. | Gabriela Moldovan | 2024-11-14 | 1 | -1/+0 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Add a revised proposal. | Gabriela Moldovan | 2024-11-14 | 1 | -0/+358 | |
| | | | | | | Based on Diziet's feedback in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2565#note_3099397 | |||||
| * | doc/dev/notes: keymgr-certificates: Say that the original proposal is rejected. | Gabriela Moldovan | 2024-11-14 | 1 | -7/+12 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Update key notation for clarity. | Gabriela Moldovan | 2024-11-14 | 1 | -6/+8 | |
| | | ||||||
| * | doc/dev/notes: keymgr-certificates: Add note about certificate management. | Gabriela Moldovan | 2024-11-14 | 1 | -0/+177 | |
| | | | | | | | | This describes the storage format and on-disk key store paths of `relaysign_ed` certificates (which we'll soon need to support). Part of #1617 | |||||
| * | Move RPC documents into a new location | Nick Mathewson | 2024-10-24 | 3 | -1894/+0 | |
| | | | | | This will be the start of an mdbook document. | |||||
| * | Merge branch 'rpc-server-sketch' into 'main' | Nick Mathewson | 2024-10-24 | 2 | -15/+201 | |
| |\ | | | | | | | | | | | | | Sketch RPC server and superuser operations. Closes #1702 See merge request tpo/core/arti!2563 | |||||
| | * | rpc-sketch: clean up some ungrammatical/hypothetical language. | Nick Mathewson | 2024-10-24 | 1 | -2/+2 | |
| | | | ||||||
| | * | rpc sketch: show how to override a connect point option. | Nick Mathewson | 2024-10-24 | 1 | -0/+5 | |
| | | | ||||||
| | * | rpc-sketch: specify and permit directories full of connect files. | Nick Mathewson | 2024-10-24 | 1 | -10/+14 | |
| | | | | | | | | | | | | | | | | | | | | | | | The main purpose of this commit is to RPC servers to configure connect points individually, while allowing clients to look at a configuration location that is full of multiple connect points. This change permits us to discard allow_missing_file, which is nice. This commit still pretends that the file extension is "json"; that will be fixed in #1711. | |||||
| | * | rpc-connect: revise description of superuser and fs-mistrust options. | Nick Mathewson | 2024-10-23 | 1 | -5/+17 | |
| | | | ||||||
| | * | rpc-connect: Rewrite server behavior section. | Nick Mathewson | 2024-10-23 | 1 | -16/+58 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The most salient change here is that _everything_, including the default connect string, is a configuration option, so that `--system-arti` (hypothetical) can override it. In order to make the default connect file locations behave like regular options, I've added a `allow_missing_file` sub-option that makes the absence of a file tolerable. There is a behavioral change here: Specifying your own `rpc.listen` entries in the arti.toml _does not_ disable checking the default connect file locations. | |||||
| | * | rpc-connect: Mention #1710 when talking about system-arti case. | Nick Mathewson | 2024-10-23 | 1 | -0/+6 | |
| | | | ||||||
| | * | rpc-connect-sketch: normalize some json | Nick Mathewson | 2024-10-21 | 1 | -6/+6 | |
| | | | ||||||
 |
index : mirrors/arti.git | |
| mirror of https://gitlab.torproject.org/tpo/core/arti |
| summaryrefslogtreecommitdiff |