summaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAgeFilesLines
...
* | rpclib: FFI for opening data streams.Nick Mathewson2024-09-091-0/+1
| | | | | | | | | | There's a blocking TODO here about exposing socks error codes that I still need to solve.
* | rpclib: Support opening a data stream.Nick Mathewson2024-09-091-0/+1
|/ | | | | | Requires #1523. Implements #1524.
* Rename tor-keys crate to tor-key-forgeDavid Goulet2024-09-041-19/+19
| | | | Signed-off-by: David Goulet <[email protected]>
* tor-keymgr: Use tor-keys crate and remove dead codeDavid Goulet2024-09-041-0/+2
| | | | | | | | | | | Everything copied in the previous commits to tor-keys is now removed and tor-keys crate is used accross the code. Minor changes to tor-keys to accomodate this change. Part of #1137 Signed-off-by: David Goulet <[email protected]>
* tor-keys: Move HS crypto keys impl from tor-keymgrDavid Goulet2024-09-041-0/+1
| | | | | | | | | | As stated in the comment added in this commit, this is temporary as we want tor-hscrypto to start using tor-keys and define these implementation there. Part of #1137 Signed-off-by: David Goulet <[email protected]>
* tor-keys: Copy several types/traits from tor-keymgrDavid Goulet2024-09-041-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | Move EncodableKey, ToEncodableKey and Keygen to tor-keys crate from tor-keymgr. To pull this off, an err.rs was added taken from tor-keymgr but stripped down to what was needed only. No code was changed in any of the files copied from tor-keymgr. Our deftly macro now auto implement these traits for the key wrapper type created. This gives the ability of the wrapper to be used by a tor-keymgr::Keystore. In order to pull this off, most of the SSH code has been moved into this crate (ssh.rs) meaning that its ABI/API now resides in the tor-keys trait outside of tor-keymgr. Note that Sealed was not put back because the deftly macro is designed to be used outside of this crate and thus implementing EncodableKey. The alternative is that we would need to force all arti keys to be declared in this crate which is not great because it then exposes all these key types to the world outside their subsystem. Part of #1137 Signed-off-by: David Goulet <[email protected]>
* tor-keys: Automatically implement keymgr traitDavid Goulet2024-09-041-0/+1
| | | | | | | | | | | | | | | | | The derive ed25519 keypair macro now implements the keymgr trait so the key wrapper can now be used with a keystore without needing to specify it in the tor-keymgr crate. For this to work, a slight change to the KeygenRng trait was needed as in to expect the CryptoRngCore trait which is what ed25519-dalek requires. And also, the removal of the Sealed trait since now it is accepted to implement these traits outside tor-keymgr. Fixes #1137 Signed-off-by: David Goulet <[email protected]>
* tor-keys: New crate for Tor key declarationDavid Goulet2024-09-041-0/+12
| | | | | | | | | | At this commit, we also add a derive-deftly macro for ed25519 keypair along a helper macro that can define a wrapper around a lower-level ed25519::Keypair. Part of #1137 Signed-off-by: David Goulet <[email protected]>
* arti: Proper testing of the memory limit config parsingIan Jackson2024-09-041-0/+1
| | | | | | Including testing that uncommenting the example generates a config with tracking enabled, and that the example low_water is the default value for the example max.
* arti-client: Unstable cargo feature for exposing info for testingIan Jackson2024-09-041-0/+1
|
* tor-memquota: Unstable cargo feature for exposing info for testingIan Jackson2024-09-041-0/+1
|
* connection-checker: Do not enable arti "experimental" featureIan Jackson2024-09-041-0/+1
| | | | | This breaks config tests in crates/arti which test configuration parsing of disabled experimental features.
* Add memquota cargo features to arti and arti-clientIan Jackson2024-09-041-0/+1
| | | | | | * In arti, memquota simply turns on in memquota arti-client * In arti-client, add an (unconditional) dependency on tor-memquota, and have the memquota feature turn on the feature in tor-memquota.
* tor-memquota: Rework optionality configurationIan Jackson2024-09-041-1/+0
| | | | | | | | | | | | | | | | | | Allow a `Config` to represent "this is supposed to be disabled". This involves wrapping the actual built configuration in an IfEnabled. We treat max = usize::MAX, or max being unspecified, as "disable". We can now reporting an error during config building if max is set but we're compiling the feature out. Conversely, we can now make `MemoryQuotaTracker::new()` unconditional, since enabled confiogurations are uninhabited when the feature is compiled out. We change how we derive the setters, deriving them from the Builder. I chose to abolish the use of derive_builder. See the new comment on ConfigBuilder.
* tor-memquota: Add unit tests for config handlingIan Jackson2024-09-041-0/+1
| | | | | We're about to change the config behaviour; adding these tests first allows us to demonstrate the changes.
* Bump arti crate to 1.2.7Gabriela Moldovan2024-09-031-1/+1
| | | | | | | | Done using: ``` cargo set-version --bump patch -p arti ```
* Bump all the unstable tor- and arti- crates to 0.22.0.Gabriela Moldovan2024-09-031-40/+40
| | | | | | | | | | Done using: ``` for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.22.0 done ```
* Bump the versions of the non-{arti-,tor-} crates.Gabriela Moldovan2024-09-031-6/+6
| | | | | | | | | | | | | | | | | | | | | This bumps the versions of the non-{arti,tor-} crates that have non-functional changes: - fslock-guard (updated rustdoc-args) - equix (comment typo fixes) - caret (updated rustdoc-args) - safelog (updated rustdoc-args) - retry-error (updated rustdoc-args) And of the pre-1.0.0 crates that have new APIs: - fs-mistrust (new `CheckedDir::metadata` API) Done using ``` for c in "${non_tor[@]}"; do maint/bump_nodep $c; done ``` where `non_tor` contains the list above
* oneshot-fused-workaround: Set the initial version to 0.1.0.Gabriela Moldovan2024-09-031-1/+1
| | | | This is the first time we're publishing this, so let's start at 0.1.0.
* tor-async-utils: Re-export oneshot-fused-workaround as oneshot.Gabriela Moldovan2024-09-031-0/+1
|
* Run cargo update in preparation for release.Gabriela Moldovan2024-09-021-259/+247
|
* Merge branch 'ahf/macos-cross-build' into 'main'Alexander Hansen Færøy2024-09-021-2/+3
|\ | | | | | | | | | | | | Fix reproducible build CI job for macOS Closes #1394 and #1507 See merge request tpo/core/arti!2377
| * Bump CC version to 1.1.15.Alexander Færøy2024-09-011-2/+3
| | | | | | | | Fixes: tpo/core/arti#1507.
* | Move stream_peek into tor-async-utilsJim Newsome2024-08-291-1/+3
| |
* | tor-rtmock: remove dependency on tor-async-utilsJim Newsome2024-08-281-1/+0
| | | | | | | | | | Now that `oneshot-fused-workaround` is its own crate, `tor-rtmock` doesn't need `tor-async-utils`.
* | extract tor_async_utils::oneshot into ::oneshot-fused-workaroundJim Newsome2024-08-281-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Having this in the `tor-async-utils` crate prevents us from doing both of the following without introducing a circular dependency: * using it in `tor-rtmock` (which we currently do, particularly in tests). * using `tor-rtmock` to test things in `tor-async-utils`. We don't do this yet, but it is generally sensible to do so. In particular we want to move the `stream_peak` module there, which is currently tested with `tor-rtmock`. Moving this into its own crate avoids this circular dependency.
* | rpc: Use MockRuntime for set_proxy_info test.Nick Mathewson2024-08-281-0/+1
| |
* | arti: Define a new ArtiRpcSession type.Nick Mathewson2024-08-281-0/+1
| | | | | | | | | | | | | | This type exists in the `arti` crate. It wraps and delegates to `arti_rpcserver::RpcSession`. Subsequent commits will use it to expose information from the `arti` crate to the RPC system; right now it does nothing.
* | byte_qty: Support deserialising from strings and floatsIan Jackson2024-08-271-0/+2
| | | | | | | | This finally makes this type suitable for parsing in config files.
* | byte_qty: Implement FromStr, and improve Display implIan Jackson2024-08-271-0/+1
| | | | | | | | Display can now choose appropriate units.
* | Merge branch 'live-reload' into 'main'gabi-2502024-08-221-0/+10
|\ \ | | | | | | | | | | | | | | | | | | tor-hsservice: Add watcher for restricted_discovery config changes Closes #1505 See merge request tpo/core/arti!2353
| * | arti: Use a postage::watch channel in the tests.Gabriela Moldovan2024-08-221-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | The watch channel should help prevent flakiness in the tests (`TestModule` uses `maybe_send` to only send the received config if it's different from the previously received value. This is supposed to prevent the tests from failing when duplicate update events are received).
| * | arti: Add test for config reloading.Gabriela Moldovan2024-08-211-0/+1
| | |
| * | tor-config: Write tests for FileWatcher.Gabriela Moldovan2024-08-211-0/+2
| | |
| * | tor-config: Add getters for FileWatcher.Gabriela Moldovan2024-08-211-0/+1
| | | | | | | | | | | | | | | | | | | | | Sometimes it's useful to know what files/directories are being watched. For example, the descriptor publisher needs to know in order to figure out if it needs to update the watcher in response to changes in the config.
| * | tor-config: Make FileWatcher use an opaque channel type.Gabriela Moldovan2024-08-211-0/+2
| | | | | | | | | | | | The `FileWatcher` now uses a `postage::watch` channel under the hood.
| * | tor-config: Give FileWatcherBuilder a handle to the runtime.Gabriela Moldovan2024-08-211-0/+1
| | | | | | | | | | | | | | | The event handler will soon be made async, so we need a handle to the runtime.
| * | tor-config: Move FileWatcher to tor-config.Gabriela Moldovan2024-08-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | For the most part, this is just code motion. The only change here is that `prepare` is no longer a method on `FileWatcher`. This decouples `FileWatcher` from `ConfigurationSources`, enabling us to use it to watch files and directories that aren't configuration.
* | | Merge branch 'optional-managed-pts' into 'main'Nick Mathewson2024-08-221-0/+1
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | tor-ptmgr: make managed PTs optional ('managed-pts' feature flag) Closes #1334 See merge request tpo/core/arti!2354
| * | tor-ptmgr: added a 'managed-pts' default featureSteven Engler2024-08-211-0/+1
| | | | | | | | | | | | | | | This conditionally compiles most of the code related to managed transports.
* | | Merge branch 'peekable-poll-set' into 'main'Jim Newsome2024-08-211-0/+2
|\ \ \ | |_|/ |/| | | | | | | | Add and use `PeekableStream` and `UnobtrusivePeekableStream` See merge request tpo/core/arti!2345
| * | StreamMap: Use StreamUnobtrusivePeeker instead of PeekableJim Newsome2024-08-211-0/+1
| | |
| * | StreamUnobtrusivePeeker: implement PeekableStream and UnobtrusivePeekableStreamJim Newsome2024-08-211-0/+1
| |/
* | keymanip: Make blind_pubkey exist unconditionallyNick Mathewson2024-08-211-0/+1
| | | | | | | | | | | | | | | | | | Now it exists unconditionally so that we can have our assertion for public key consistency happen unconditionally. (Blinding secret keys is not remotely in the critical path, so I'm not concerned about the critical path.) From a suggestion from Gabi on !2341.
* | relay: Add basic configuration and builderDavid Goulet2024-08-201-0/+13
|/ | | | | | | | | | | | | | | This adds the basic TorRelayConfig object along a builder in order to create a TorRelay object. At this commit, the configuration object only holds a "StorageConfig" which is a simple starting point which will allow to expand to a KeyMgr and then a ChanMgr along more configuration. There is also no custom Error for the crate at this point. Fixes #1534 Signed-off-by: David Goulet <[email protected]>
* rpcserver: Use slotmap-careful instead of generational-arena.Nick Mathewson2024-08-141-10/+1
| | | | | | | | | Unlike generational-arena, slotmap is maintained. Unlike slotmap, slotmap-careful should never be able to reuse the same key for two different objects. Closes #1282.
* Merge branch 'careful-slotmap' into 'main'Nick Mathewson2024-08-141-0/+13
|\ | | | | | | | | New `slotmap-careful` crate to use when we mustn't re-use keys. See merge request tpo/core/arti!2298
| * New `slotmap-careful` crate to use when we mustn't re-use keys.Nick Mathewson2024-08-081-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This crate works as a drop-in replacement for the generational arena types `slotmap::{SlotMap, DenseSlotMap, HopSlotMap}`, and is implemented a set of wrappers around those types. The wrappers guarantee that slot versions numbers can never wrap around by marking as unusable any slot whose version number would otherwise get too high. (We add some leeway between our max allowed version number and the largest possible version number, so that we can detect bugs.) The code relies on the serde encoding of slotmap key versions. For notes on stability and (surprisingly good) performance, see the comments. Test coverage is around 98% for the lib.rs file; it's lower in key_data.rs, since the error cases are unreachable given slotmap's current behavior. Open questions: * What further testing is a good idea? * Will slotmap ever upstream something like this? See "# Limitations" comment for the parts of slotmap that are not implemented; I hope that we don't need them.
* | Resolve unreachable_patterns warnings from nightly.Nick Mathewson2024-08-131-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Nightly rust doesn't like it when you have a `match` arm that can never be reached because of an uninhabited type. As such, we can't say stuff like: ``` let x: Option<Void> = ...; match x { Some(_) => unreachable!(), None => ... } ```
* | Merge branch 'rpc-describe' into 'main'Nick Mathewson2024-08-131-0/+1
|\ \ | | | | | | | | | | | | RPC: Method to expose a list of RPC methods. See merge request tpo/core/arti!2332
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 13:27:34 +0000