summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* | Merge branch 'rpc-configuration' into 'main'opara2025-03-253-3/+142
|\ \ | | | | | | | | | | | | | | | | | | Cleanups related to rpc configuration Closes #1309 and #1830 See merge request tpo/core/arti!2887
| * | Add examples and tests for RPC options.Nick Mathewson2025-03-253-3/+121
| | | | | | | | | | | | Closes #1830.
| * | arti: warn when rpc options are set without rpc feature.Nick Mathewson2025-03-251-0/+21
| | | | | | | | | | | | Closes #1309.
* | | Merge branch 'circuit-action' into 'main'opara2025-03-253-16/+31
|\ \ \ | |_|/ |/| | | | | | | | tor-proto: simplify `ConfluxSet::circuit_action` See merge request tpo/core/arti!2884
| * | tor-basic-utils: move `flatten` from tor-protoSteven Engler2025-03-252-10/+15
| | | | | | | | | | | | I also added an additional non-doc TODO comment.
| * | tor-proto: simplify tunnel `run_once`Steven Engler2025-03-241-7/+1
| | | | | | | | | | | | As far as I can tell, the extra drop handling code isn't needed anymore.
| * | tor-proto: remove `CircuitActionResult` aliasSteven Engler2025-03-241-4/+1
| | | | | | | | | | | | | | | I think the return type is simplified enough now that we don't need this.
| * | tor-proto: change `ConfluxSet::next_circ_action` to return a `Future`Steven Engler2025-03-242-6/+25
| | | | | | | | | | | | | | | | | | Now returns only the first item of the stream rather than the stream itself. We use this in `Reactor::run_once`, which means we only ever use the first item anyways.
| * | tor-proto: rename `ConfluxSet::circuit_action` to `next_circ_action`Steven Engler2025-03-242-6/+6
| | |
* | | Merge branch 'rpc-stable' into 'main'Nick Mathewson2025-03-255-24/+30
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | Mark RPC stable, and revise READMEs for RPC crates. Closes #1883 See merge request tpo/core/arti!2871
| * | Revise READMEs for RPC crates.Nick Mathewson2025-03-253-20/+24
| | | | | | | | | | | | | | | | | | We'll want to add more text here, but that should probably wait until we have a permanent home for the rendered RPC documentation. (see #1829)
| * | Mark rpc features as non-experimental.Nick Mathewson2025-03-252-4/+6
|/ /
* | Merge branch 'choose_multiple_cleanup' into 'main'Nick Mathewson2025-03-253-11/+116
|\ \ | | | | | | | | | | | | | | | | | | Cleanups and followups for rand 0.9 choose_multiple_weighted and friends. Closes #1903 See merge request tpo/core/arti!2880
| * | netdir: Add a (hopefully) temporary workaroundNick Mathewson2025-03-251-3/+27
| | | | | | | | | | | | | | | Instead of doing the more sensible thing when every relay has weight 0, give a warning message.
| * | netdir: Add a note about using f64Nick Mathewson2025-03-251-0/+8
| | |
| * | netdir: Another test for choose_multiple_weighted.Nick Mathewson2025-03-251-0/+17
| | | | | | | | | | | | | | | | | | Here we test the (arguably inconsistent behavior) where can we return fewer items than requested if no item had zero weight. (If this ever becomes an error, we need to modify the calling code.)
| * | netdir: Warn on unexpected WeightedErrorsNick Mathewson2025-03-251-5/+13
| | | | | | | | | | | | | | | | | | WeightedError::InsufficientNonzero is expected under some circumstances, but the other instances would mean that we have a bug.
| * | netdir: add a test to verify weighted samplingNick Mathewson2025-03-251-3/+37
| | | | | | | | | | | | | | | We want to make sure that behavior for 0-weighted elements is consistent for choose_multiple_weighted and choose_weighted.
| * | circmgr: test behavior of IteratorRandom::choose_multipleNick Mathewson2025-03-251-1/+15
| | |
* | | Merge branch 'circuit-cmd' into 'main'gabi-2502025-03-253-66/+155
|\ \ \ | | | | | | | | | | | | | | | | tor-proto: Replace RunOnceCmdInner with CircuitCmd in Circuit impl See merge request tpo/core/arti!2881
| * | | tor-proto: Add a TODO about supporting incoming streams with conflux.Gabriela Moldovan2025-03-241-0/+1
| | | |
| * | | tor-proto: Clarify the semantics of various CircuitCmds.Gabriela Moldovan2025-03-241-3/+3
| | | | | | | | | | | | | | | | Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2881#note_3178624
| * | | tor-proto: Add a TODO about the unnecessary Vec allocations.Gabriela Moldovan2025-03-242-2/+11
| | | |
| * | | tor-proto: Add TODO about rethinking the circuit *Cmd enums.Gabriela Moldovan2025-03-241-0/+6
| | | |
| * | | tor-proto: s/CircuitAction::Single/CircuitAction::RunCmd.Gabriela Moldovan2025-03-243-8/+6
| | | | | | | | | | | | | | | | | | | | There is no `Multiple` counterpart in `CircuitAction`, so the `Single` variant name doesn't make much sense.
| * | | tor-proto: Remove now-unused leg_id argument.Gabriela Moldovan2025-03-242-7/+1
| | | | | | | | | | | | | | | | | | | | The `LegId` is now added by the caller, when converting the resulting `CircuitCmd`s to `RunOnceCmdInner`.
| * | | tor-proto: Add docs to SendRelayCell.Gabriela Moldovan2025-03-241-3/+3
| | | |
| * | | tor-proto: Replace RunOnceCmdInner with CircuitCmd where appropriate.Gabriela Moldovan2025-03-243-47/+61
| | | | | | | | | | | | | | | | | | | | `CircuitCmd`s are a subset of `RunOnceCmdInner`, and don't have a `LegId`.
| * | | tor-proto: Add CircuitCmd enum.Gabriela Moldovan2025-03-242-1/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A `CircuitCmd`, unlike `RunOnceCmdInner`, doesn't know anything about `LegId`s. The user of the `CircuitCmd`s is supposed to know the `LegId` of the circuit the `CircuitCmd` came from. This is necessary because circuits don't know (and can't know) their own `LegId`. The various `Circuit` operations (e.g. `handle_cell`) will soon be updated to return `CircuitCmd` instead of `RunOnceCmdInner` (because the `RunOnceCmdInner` variants will soon be updated to also have an associated `LegId`, and `Circuit`s don't have access to their `LegId`s). The calling code, which *does* know the `LegId`, will then map `CircuitCmd`s to `RunOnceCmdInner`.
| * | | tor-proto: Put the leg id of the circuit in CircuitAction::HandleCell.Gabriela Moldovan2025-03-232-7/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This tells the reactor which circuit leg the input message originated from. Addresses a TODO.
* | | | Merge branch 'cautious_rng' into 'main'Nick Mathewson2025-03-2418-25/+291
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | Use a very cautious Rng for deriving longer-lived keys Closes #1898 See merge request tpo/core/arti!2874
| * | | llcrypto: Document some design choices from CautiousRng.Nick Mathewson2025-03-241-1/+12
| | | |
| * | | Use an EntropicRng trait to enforce key generation rules.Nick Mathewson2025-03-2410-20/+82
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We want to require that whenever we generate a key that's persistent (stored in KeyMgr), it's going to be made from a stronger-than-usual Rng. This trait helps us enforce that. We also add a FakeEntropicRng struct to use for testing. Note that this turned up a case that we'd missed, which required an internal change in tor-hsservice.
| * | | Use CautiousRng for keys going into the KeyMgr.Nick Mathewson2025-03-247-6/+23
| | | |
| * | | llcrypto: new CautiousRng for constructing long-lived keysNick Mathewson2025-03-244-0/+176
|/ / / | | | | | | | | | | | | | | | This Rng combines inputs from several sources, including OsRng, to minimize the likelihood of falling to a vulnerability in any particular one.
* | | Merge branch 'tests-rpcserver-msgs' into 'main'Nick Mathewson2025-03-241-6/+25
|\ \ \ | | | | | | | | | | | | | | | | rpcserver: Increase coverage in msgs module See merge request tpo/core/arti!2870
| * | | rpcserver: Increase coverage in msgs modulevcrn2025-03-241-6/+25
| | | |
* | | | Merge branch 'coc_link' into 'main'David Goulet2025-03-243-3/+3
|\ \ \ \ | |_|_|/ |/| | | | | | | | | | | Update links to the code of conduct See merge request tpo/core/arti!2882
| * | | Update links to the code of conductNick Mathewson2025-03-243-3/+3
| | |/ | |/| | | | | | | The old link seems not to work any more.
* | | Merge branch 'fallbackdirs-03-2025' into 'main'opara2025-03-241-920/+897
|\ \ \ | | | | | | | | | | | | | | | | fallbackdir: Update list generated on March 20, 2025 See merge request tpo/core/arti!2875
| * | | fallbackdir: Update list generated on March 20, 2025Tor CI Release2025-03-241-920/+897
| | | | | | | | | | | | | | | | Signed-off-by: Tor CI Release <[email protected]>
* | | | Merge branch 'return-errors-through-channel' into 'main'opara2025-03-243-50/+74
|\ \ \ \ | |/ / / |/| | | | | | | | | | | tor-proto: some TODO fixes in `ControlHandler` See merge request tpo/core/arti!2867
| * | | tor-proto: send errors to oneshot channel in more placesSteven Engler2025-03-241-16/+38
| | | |
| * | | tor-proto: made `StreamTarget::send_sendme` async and fixed a TODOSteven Engler2025-03-243-10/+28
| | | |
| * | | tor-proto: remove previously completed TODOsSteven Engler2025-03-241-21/+7
| | | |
| * | | tor-proto: fix small TODOSteven Engler2025-03-241-3/+1
| |/ /
* | | Merge branch 'af-unix' into 'main'Ian Jackson2025-03-2423-70/+142
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Correct terminology for unix-domain sockets Closes #827 See merge request tpo/core/arti!2841
| * | Style.md: Be more nuanced about identifiers with `Unix` inIan Jackson2025-03-241-3/+7
| | |
| * | RPC: Explain in more detail about Windows "named pipe"sIan Jackson2025-03-241-2/+5
| | |
| * | AF_UNIX terminology: Rename two error structsIan Jackson2025-03-2410-21/+43
| | | | | | | | | | | | | | | | | | We change `NoUnixAddressSupport` to `NoAfUnixSocketSupport` because it doesn't make much sense to talk about support for the addresses separately from support for the sockets.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 03:18:10 +0000