summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | arti: Move RpcConfig to rpc.rsNick Mathewson2024-12-192-29/+33
| | |
| * | map_builder: Add support for default settings.Nick Mathewson2024-12-191-10/+133
| | | | | | | | | | | | | | | | | | This is a little tricky (beyond the usual macro fun) because we needed to use ExtendBuilder to get reasonable behavior for our default trees.
| * | Define macros to create a map-builder type.Nick Mathewson2024-12-192-0/+216
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We're about to need this to define some of the configuration for RPC listeners. The provided map-builder type is much less voluminous in terms of APIs added than the list-builder type: It just uses Deref* and sub_builder. I think this simplicity may be a win. I'll need to rethink how this type handles defaults in order to implement connect points properly; I've left XXXXs for that issue.
| * | tor-config: Add "extend" functionality for config builders.Nick Mathewson2024-12-192-0/+180
| | | | | | | | | | | | We'll use this to implement defaults for maps in our configuration.
| * | connpt: Make unix socket handling more robust.Nick Mathewson2024-12-195-21/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Grab an associated lock file... - ... then delete the socket file (if it's present) ... - ... then bind to it. On exit: - remove the socket - then drop the lock.
| * | rpc-connect: Make LoadOptions buildable.Nick Mathewson2024-12-193-1/+4
| | |
| * | rpc-connect: fix another very typoed lineNick Mathewson2024-12-191-1/+1
| | |
| * | list_builder: fix a very typoed line.Nick Mathewson2024-12-191-1/+1
| | |
| * | rtcompat: re-export items from tor_general_addr::generalNick Mathewson2024-12-191-0/+2
| | |
| * | tor-general-addr: Add general::SocketAddr::as_pathname()Nick Mathewson2024-12-191-0/+9
| | |
* | | Merge branch 'env-var' into 'main'Nick Mathewson2024-12-192-4/+8
|\ \ \ | |/ / |/| | | | | | | | | | | | | | fs-mistrust: trim whitespace in env var values Closes #1782 See merge request tpo/core/arti!2677
| * | fs-mistrust: trim whitespace in env var valuesSteven Engler2024-12-182-4/+8
|/ /
* | Merge branch 'env-var' into 'main'Nick Mathewson2024-12-182-4/+43
|\ \ | | | | | | | | | | | | fs-mistrust: commit to stable env var handling See merge request tpo/core/arti!2674
| * | fs-mistrust: commit to stable env var handlingSteven Engler2024-12-182-4/+43
| | | | | | | | | | | | | | | | | | | | | | | | Since these environment variables become part of the stable API for applications that use fs-mistrust, we should be explicit about how these environment variables are interpreted so that applications can show the values in their documentation or help text, and so that we don't accidentally change the behaviour and break applications.
| * | fs-mistrust: (docs) fix incomplete list of env variable valuesSteven Engler2024-12-181-2/+2
|/ /
* | 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
| | |
* | | Merge branch 'docs-notes-service-side-pow' into 'main'wesleyac2024-12-171-0/+217
|\ \ \ | |/ / |/| | | | | | | | docs: Add note on plan for service side PoW. See merge request tpo/core/arti!2663
| * | 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
| | |
| * | docs: Adjust check_solve visibility.Wesley Aptekar-Cassels2024-12-171-1/+1
| | |
| * | docs: We want nonces to be unique, not solution bytes.Wesley Aptekar-Cassels2024-12-171-1/+1
| | |
| * | docs: Add details of ReplayLog to service side PoW notes.Wesley Aptekar-Cassels2024-12-171-3/+29
| | |
| * | docs: Update notes on service-side PoWWesley Aptekar-Cassels2024-12-171-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-Cassels2024-12-171-74/+93
| | |
| * | docs: Add note on plan for service side PoW.Wesley Aptekar-Cassels2024-12-171-0/+107
|/ /
* | Merge branch 'reverse-hscrypto-key-forge-dep' into 'main'David Goulet2024-12-126-116/+114
|\ \ | | | | | | | | | | | | | | | | | | tor-hscrypto: Move encodable key trait impls from tor-key-forge. Closes #1778 See merge request tpo/core/arti!2668
| * | check_toposort: Topologically sort the dependency.Gabriela Moldovan2024-12-111-1/+1
| | | | | | | | | | | | | | | Now `tor-hscrypto` depends on `tor-key-forge`, so we need to update their ordering in `Cargo.toml`.
| * | tor-hscrypto: Move encodable key trait impls from tor-key-forge.Gabriela Moldovan2024-12-115-115/+113
| |/ | | | | | | | | | | | | | | | | This enables us to get rid of the tor-key-forge -> tor-hscrypto dependency, partially addressing the TODO from `tor_key_forge::traits`. This commit is mostly code motion. Best reviewed with `--color-moved`. See also #1778
* | Merge branch 'nowat_warning' into 'main'gabi-2502024-12-121-1/+1
|\ \ | | | | | | | | | | | | streamops: Resolve unused-variable warnings. See merge request tpo/core/arti!2673
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 16:48:13 +0000