| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| | * | | rpc-connect: Use try_lock when acquiring fslock | Nick Mathewson | 2024-12-19 | 2 | -1/+9 | |
| | | | | | | | | | | | | | | | | This lets us bail when another process has bound to our connect point, rather than blocking indefinitely. | |||||
| | * | | rpc: More logging when binding addresses | Nick Mathewson | 2024-12-19 | 2 | -1/+25 | |
| | | | | ||||||
| | * | | arti::rpc: Refactor listener options to support defaults properly | Nick Mathewson | 2024-12-19 | 1 | -31/+75 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We want to have every option that applies to a connect point (other than file or dir) exist both as a default version, and as a per-file override. This approach lets us do so: We store _builders_ for these options in the config, and then use ExtendBuilder to merge them together. (There aren't yet any options other than 'enable', but there will be before long.) | |||||
| | * | | arti::rpc: Rename "overrides" field and type. | Nick Mathewson | 2024-12-19 | 2 | -19/+18 | |
| | | | | | | | | | | | | | | | | Per discussion with Diziet, these aren't really "overriding" anything; they're the actual options for a single connect point. | |||||
| | * | | arti_rpc_tests: Use connpt-based server configuration. | Nick Mathewson | 2024-12-19 | 1 | -7/+24 | |
| | | | | ||||||
| | * | | arti: Use connect points to listen for RPC connections. | Nick Mathewson | 2024-12-19 | 5 | -88/+332 | |
| | | | | ||||||
| | * | | arti: Disable RPC reconfiguration for now | Nick Mathewson | 2024-12-19 | 2 | -1/+5 | |
| | | | | ||||||
| | * | | rpc: Configuration options for arti | Nick Mathewson | 2024-12-19 | 4 | -2/+160 | |
| | | | | | | | | | | | | | | | | | | | This adds the options currently specified in rpc-connect-point.rs, though they don't do anything yet. We still have to implement the correct defaulting behavior. | |||||
| | * | | arti: Move RpcConfig to rpc.rs | Nick Mathewson | 2024-12-19 | 2 | -29/+33 | |
| | | | | ||||||
| | * | | map_builder: Add support for default settings. | Nick Mathewson | 2024-12-19 | 1 | -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 Mathewson | 2024-12-19 | 2 | -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 Mathewson | 2024-12-19 | 2 | -0/+180 | |
| | | | | | | | | | | | | | We'll use this to implement defaults for maps in our configuration. | |||||
| | * | | connpt: Make unix socket handling more robust. | Nick Mathewson | 2024-12-19 | 5 | -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 Mathewson | 2024-12-19 | 3 | -1/+4 | |
| | | | | ||||||
| | * | | rpc-connect: fix another very typoed line | Nick Mathewson | 2024-12-19 | 1 | -1/+1 | |
| | | | | ||||||
| | * | | list_builder: fix a very typoed line. | Nick Mathewson | 2024-12-19 | 1 | -1/+1 | |
| | | | | ||||||
| | * | | rtcompat: re-export items from tor_general_addr::general | Nick Mathewson | 2024-12-19 | 1 | -0/+2 | |
| | | | | ||||||
| | * | | tor-general-addr: Add general::SocketAddr::as_pathname() | Nick Mathewson | 2024-12-19 | 1 | -0/+9 | |
| | | | | ||||||
| * | | | Merge branch 'env-var' into 'main' | Nick Mathewson | 2024-12-19 | 2 | -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 values | Steven Engler | 2024-12-18 | 2 | -4/+8 | |
| |/ / | ||||||
| * | | Merge branch 'env-var' into 'main' | Nick Mathewson | 2024-12-18 | 2 | -4/+43 | |
| |\ \ | | | | | | | | | | | | | fs-mistrust: commit to stable env var handling See merge request tpo/core/arti!2674 | |||||
| | * | | fs-mistrust: commit to stable env var handling | Steven Engler | 2024-12-18 | 2 | -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 values | Steven Engler | 2024-12-18 | 1 | -2/+2 | |
| |/ / | ||||||
| * | | Merge branch 'dirauth-0' into 'main' | Ian Jackson | 2024-12-18 | 1 | -0/+242 | |
| |\ \ | | | | | | | | | | | | | Initial sketch of dirauth structure See merge request tpo/core/arti!2635 | |||||
| | * | | dirauth sketch: discuss offline KS_dirauth_id_* | Ian Jackson | 2024-12-17 | 1 | -0/+3 | |
| | | | | ||||||
| | * | | dirauth sketch: mention shared random protocol | Ian Jackson | 2024-12-17 | 1 | -0/+1 | |
| | | | | ||||||
| | * | | dirauth sketch: dircache, expand a bit | Ian Jackson | 2024-12-17 | 1 | -0/+5 | |
| | | | | | | | | | | | | | | | | From https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2635#note_3131826 | |||||
| | * | | dirauth sketch: dircache: mention connection to relays | Ian Jackson | 2024-12-17 | 1 | -1/+2 | |
| | | | | ||||||
| | * | | dirauth deployment plans: Updates apropos comments | Ian Jackson | 2024-12-17 | 1 | -5/+14 | |
| | | | | ||||||
| | * | | dirauth-sketch: Fix typo | Ian Jackson | 2024-12-17 | 1 | -1/+1 | |
| | | | | ||||||
| | * | | dirauth deployment plans: formatting | Ian Jackson | 2024-12-17 | 1 | -1/+4 | |
| | | | | ||||||
| | * | | dirauth deployment plans: typos | Ian Jackson | 2024-12-17 | 1 | -2/+2 | |
| | | | | ||||||
| | * | | dirauth deployment plans: fix formatting | Ian Jackson | 2024-12-17 | 1 | -3/+3 | |
| | | | | ||||||
| | * | | dirauth deployment plans: detailed transition plan | Ian Jackson | 2024-12-17 | 1 | -0/+129 | |
| | | | | ||||||
| | * | | dirauth deployment plans: add rationale for plugin | Ian Jackson | 2024-12-17 | 1 | -0/+20 | |
| | | | | ||||||
| | * | | dirauth deployment plans: fix some hard tabs | Ian Jackson | 2024-12-17 | 1 | -2/+2 | |
| | | | | ||||||
| | * | | Initial sketch of dirauth structure | Ian Jackson | 2024-12-17 | 1 | -0/+71 | |
| | | | | ||||||
| * | | | Merge branch 'docs-notes-service-side-pow' into 'main' | wesleyac | 2024-12-17 | 1 | -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-Cassels | 2024-12-17 | 1 | -0/+4 | |
| | | | | ||||||
| | * | | docs: Fix proposed PoW struct visibility. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -1/+1 | |
| | | | | ||||||
| | * | | docs: Update proposed PoW locking and add explanation. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -10/+56 | |
| | | | | ||||||
| | * | | docs: Move PoW next_expiration_time into PowVerifiers. | Wesley Aptekar-Cassels | 2024-12-17 | 1 | -1/+1 | |
| | | | | ||||||
| | * | | 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 | |
| | | | | ||||||
