summaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAgeFilesLines
...
* arti-example-config.toml: Re-un-comment the example settings in testIan Jackson2022-05-121-0/+1
|
* arti-config: Move cmdline to tor-configIan Jackson2022-05-111-0/+1
| | | | | | This does not know anything about arti, only about TOML and Config. Code motion, plus necessary import adjustments.
* ConfigurationSource: Move "usual" logic for constructionIan Jackson2022-05-111-0/+1
|
* Merge branch 'dirmgr-purification-2' into 'main'eta2022-05-101-0/+1
|\ | | | | | | | | Refactor the tor-dirmgr bootstrapping code more gracefully See merge request tpo/core/arti!488
| * tor-dirmgr/state.rs: feed through additional parameters, use themeta2022-05-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - The additional parameters passed to GetConsensusState are now passed through all the states, and used as well. - WriteNetDir doesn't have a now() or config() method any more, since the states now get this from the runtime or the config parameters. - This required modifying the tests to make a mocked runtime and custom config directly, instead of using DirRcv for this purpose. - Additionally, because we don't have to upgrade a weak reference for DirState::dl_config(), that function no longer wraps its return value in Result. - (A bunch of the FIXMEs from the previous commit that introduced the additional parameters have now been rectified as a result.)
* | Remove cargo-husky, and replace with manual instructionseta2022-05-101-7/+0
|/ | | | | | | | A build script reaching into your .git/hooks/ and modifying them nonconsensually was a bit of a horrifying concept, and also made it hard to build arti with the feature disabled. Remove this crate, and replace it with manual instructions on how to install the hooks in CONTRIBUTING.md.
* netdoc: add a new type for NicknamesNick Mathewson2022-05-091-0/+21
| | | | | | | | | | Relay nicknames are always between 1 and 19 characters long, and they're always ASCII: That means that storing them in a [u8;19] will always be possible, and always use less resources than storing them in a String. Fortunately, the tinystr crate already helps us with this kind of thing.
* Merge branch 'use-fs-mistrust'Nick Mathewson2022-05-091-0/+4
|\
| * arti: use fs-mistrust to validate configuration file locations.Nick Mathewson2022-05-091-0/+1
| |
| * arti-client: Configure and use fs-mistrust.Nick Mathewson2022-05-091-0/+3
| | | | | | | | | | | | This is derived from the environment, not the configuration file: We might not want to trust the configuration file until we've decided whether we like its permissions.
* | Bump the version of every* crate to 0.3.0Nick Mathewson2022-05-061-34/+34
| | | | | | | | * Except for safelog and fs-mistrust, which are new.
* | Merge branch 'derive-builder-fork' into 'main'Nick Mathewson2022-05-061-24/+27
|\ \ | | | | | | | | | | | | | | | | | | Switch to derive_builder_arti_fork Closes #446 See merge request tpo/core/arti!490
| * | Switch to derive_builder_arti_forkIan Jackson2022-05-061-24/+27
| |/ | | | | | | | | | | | | | | | | For reference, the git source for this crate (and the others in its workspace) currently lives in my personal github account (ijackson). If this fork turns out to be long-lived and gains features and/or users, it would be good to move it to a gitlab somewhere. I have granted Nick crate ownership on the crates.io system.
* | Apply `sensitive` in some info-level log messages.Nick Mathewson2022-05-061-0/+3
| | | | | | | | | | This specifically applies the `sensitive` wrapper in the places where we're logging target addresses at level "info" or higher.
* | Implement a safe-logging facility.Nick Mathewson2022-05-061-0/+66
|/ | | | | | This is a rough first-cut of an API that I think might help us with keeping limited categories of sensitive information out of our logs. I'll refine it based on experiences with using it.
* Run "cargo update" in preparation for a release... next week?Nick Mathewson2022-05-041-133/+133
|
* list_builder: Use Educe to derive DefaultIan Jackson2022-05-041-0/+1
| | | | | | This allows us to use this with an item builder type which doesn't impl Default. (Obviously this only makes sense for items which aren't actually builders.)
* Add dependency on paste crateIan Jackson2022-05-041-0/+1
| | | | The list accessor macro is going to want this.
* Merge branch 'path' into 'main'Ian Jackson2022-05-031-0/+32
|\ | | | | | | | | | | | | CfgPath overhaul Closes #449 See merge request tpo/core/arti!478
| * CfgPath: Test serialisation round-trip with a binary formatIan Jackson2022-05-031-0/+29
| | | | | | | | | | | | Use MessagePack. Signed-off-by: Ian Jackson <[email protected]>
| * CfgPath: Overhaul APIIan Jackson2022-05-031-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Document that this can contain either a string for expansion, or a literal PathBuf not for expansion. Rename the `from_path` method to `new_literal`: a very important difference is whether it gets expanded - less important than the Rust type. Also, now it takes `Into<PathBuf>`, which avoids a needless clone. (We don't change the API in `arti-client` because `&tempfile::Tempdir()` doesn't implement `Into<PathBuf>`, so `arti-client` has to have some new `as_ref` calls.) Provide accessors `as_unexpanded_str` and `as_literal_path`. The deserialisation already makes this part of the stable API,l so not pvoding accessors seems just obstructive. They are useful for tests, too. Add tests for the new entrypoints, and for deserialisation of both variants from TOML (via config, or directly) and JSON.
* | Merge branch 'fs-mistrust-v2' into 'main'Nick Mathewson2022-05-031-0/+23
|\ \ | |/ |/| | | | | Second cut at a fs-mistrust crate. See merge request tpo/core/arti!468
| * fs-mistrust: Add code to make a self-named group "trusted".Nick Mathewson2022-05-031-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This required a bit of poking through the `users` crate, to mess with the user and group dbs. The original goal was to "trust the group with the same name as us", but it turned into a bit of a production, since: * We want to take our own name from $USER, assuming that matches our uid. (Otherwise we want to ask getpwuid_r().) * We only want to trust the group if we are actually a member of that group. * We want to cache this information. * We want to test this code.
| * fs-mistrust: more examples, documentation.Nick Mathewson2022-05-031-0/+1
| |
| * Add functionality to inspect directory content permissionsNick Mathewson2022-05-031-0/+1
| | | | | | | | Also, explain _why_ this is pretty important.
| * Second cut at a fs-mistrust crate.Nick Mathewson2022-05-031-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This crate is meant to solve #315 by giving a way to make sure that a file or directory is only accessible by trusted users. I've tried to explain carefully (in comments and documentation) what this crate is doing and why, under the assumption that it will someday be read by another person like me who does _not_ live and breathe unix file permissions. The crate is still missing some key features, noted in the TODO section. It differs from the first version of the crate by taking a more principled approach to directory checking: it emulates the path lookup process (reading symlinks and all) one path change at a time, thus ensuring that we check every directory which could enable an untrusted user to get to our target file, _or_ which could enable them to get to any symlink that would get them to the target file. The API is also slightly different: It separates the `Mistrust` object (where you configure what you do or do not trust) from the `Verifier` (where you set up a check that you want to perform on a single object). Verifiers are set up to be a bit ephemeral, so that it is hard to accidentally declare that _every_ object is meant to be readable when you only mean that _some_ objects may be readable.
* | update tls-api to 0.8.0trinity-1686a2022-04-281-63/+10
| | | | | | | | and remove corresponding RUSTSEC from ignored list
* | Merge branch 'derive-builder-git-fixup' into 'main'eta2022-04-271-2/+2
|\ \ | | | | | | | | | | | | derive_builder: Use git dep everywhere, rather than cargo patch See merge request tpo/core/arti!477
| * | derive_builder: Use git dep everywhere, rather than cargo patchIan Jackson2022-04-271-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `[patch]` approach causes the tree not to build when used as a dependency, unless the `[patch]` is replicated into the depending project. Instead, replace our `derive_builer =` dependencies with a reference to a specific git commit: perl -i~ -pe 'next unless m/^derive_builder/; s#"(0\.11\.2)"#{ version = "$1", git = "https://github.com/ijackson/rust-derive-builder", rev = "ba0c1a5311bd9f93ddf5f5b8ec2a5f6f03b22fbe" }#' crates/*/Cargo.toml Note that the commitid has changed. This is because derive_builder is in fact a workspace of 4 crates. 3 of them are of interest to arti itself (the 4th exists only for testing). So the same "add git revision" treatment had to be done to the `derive_builder` and `derive_builder_macro` crates. Each dependency edge involves a new commit in the derive_builder workspace, since we can't create a git commit containing its own commitid. (We want to use commits, rather than a branch, so that what we are depending on is actually properly defined, and not subject to the whims of my personal github namespace.) There are no actual code changes in derive_builder.
* | | Bump async_executors to 0.6Nick Mathewson2022-04-261-2/+2
| | |
* | | Upgrade to AES 0.8Nick Mathewson2022-04-261-9/+18
| | | | | | | | | | | | | | | | | | | | | | | | Now that we require Rust 1.56, we can upgrade to AES 0.8. This forces us to have some slight API changes. We require cipher 0.4.1, not cipher 0.4.0, since 0.4.0 has compatibility issues with Rust 1.56.
* | | Bump to config 0.13Nick Mathewson2022-04-261-2/+2
| | |
* | | Upgrade tracing-journald to 0.3.0Nick Mathewson2022-04-261-2/+2
| | |
* | | Upgrade to Postage 0.5.0Nick Mathewson2022-04-261-2/+3
| | |
* | | Upgrade to rlimit 0.8.3, again.Nick Mathewson2022-04-261-2/+2
|/ / | | | | | | | | | | | | Now that our MSRV is at 1.56, we can use the latest rlimit. It has to be 0.8.3 (not "0.8"), since 0.8.2 has compatibility issues with 1.56.
* / config list-builder: Allow overriding the per-item build methodIan Jackson2022-04-251-0/+1
|/ | | | | This will be useful especially for simple lists where the entry doesn't need a separate builder type.
* fallback list: Move default list into tor-guardmgrIan Jackson2022-04-221-0/+1
| | | | | | | | | | This is where the FallbackList type is. We are going to want to provide a builder too, which ought to impl Default. This means that the default value for the type must be next to the type. In any case, it was anomalous that it wasn't. This commit is pure code motion.
* Use git source for derive_builder for now, for sub_builder featureIan Jackson2022-04-211-21/+18
| | | | | | | | | | | | | | | This commitid is the current head of my MR branch https://github.com/colin-kiegel/rust-derive-builder/pull/253 https://github.com/ijackson/rust-derive-builder/tree/field-builder Using the commitid prevents surprises if that branch is updated. We will require this newer version of derive_builder. The version will need to be bumped again later, assuming the upstream MR is merged and upstream do a release containing the needed changes. We will need the new version of not only `derive_builder_core` (the main macro implementation) but also`derive_builder` for a new error type.
* Merge branch 'ticket_282' into 'main'Nick Mathewson2022-04-141-0/+1
|\ | | | | | | | | | | | | Remove obsolete files from our state directory. Closes #282 See merge request tpo/core/arti!457
| * Remove obsolete files from our state directory.Nick Mathewson2022-04-121-0/+1
| | | | | | | | | | | | | | This patch removes files created by older versions of arti, if they are at least 4 weeks old. Closes #282
* | GuardMgr: publish skew estimates.Nick Mathewson2022-04-121-0/+1
|/ | | | | | Instead of just having a function that recalculates the latest clock skew, instead recalculate the clock skew when it may have changed, and notify other processes via a postage::watch.
* Implement a better clock skew estimator.Nick Mathewson2022-04-111-0/+1
| | | | | | | | This time, our estimator discards outliers, takes the mean of what's left, and uses the standard deviation to try to figure out how seriously to take our report of skew/not-skew. These estimates are still not actually used.
* Initial functions to determine and expose a clock skew estimate.Nick Mathewson2022-04-071-0/+1
| | | | | (This is just a placeholder; I'm going to make the functions smarter in the next commit.)
* Downgrade `rlimit` to 0.7.Nick Mathewson2022-04-061-2/+2
| | | | | | | | | | Upstream 0.8.2 has broken compilation with Rust 1.53; versions 0.8.{0,1} have been yanked. Possibly by the time the next arti version comes out, they'll have fixed this situation, or we'll have upgraded our MSRV. Upstream issue at https://github.com/Nugine/rlimit/issues/42 .
* RetryTime: use strum::EnumDiscriminants to simplify loose_cmp.Nick Mathewson2022-04-041-0/+29
| | | | | Also add tests for RetryTime comparison functions to make sure they work as expected.
* tor-error: Add a new RetryTime type and related trait.Nick Mathewson2022-04-041-0/+1
|
* Update rlimit to 0.8.1Nick Mathewson2022-04-021-2/+2
| | | | This is necessary to fix build for M1 apples.
* Bump all arti*, tor* crates to 0.2.0Nick Mathewson2022-04-011-31/+31
| | | | | | | | Not all of these strictly need to be bumped to 0.2.0; many could go to 0.1.1 instead. But since everything at the tor-rtcompat and higher layers has had breaking API changes, it seems not so useful to distinguish. (It seems unlikely that anybody at this stage is depending on e.g. tor-protover but not arti-client.)
* Bump caret, retry-error to 0.1.1Nick Mathewson2022-04-011-2/+2
| | | | | | | | | | | | Unlike the rest of the crates, these don't have a "tor-" or "arti-" prefix, and are potentially used by code outside arti. With that in mind, it's probably for the best not to bump them to 0.2.0 along with the rest of our crates. They have had no changes since 0.1.0 other than refactoring and changing of clippy lints. Therefore, I'm not bumping the dependencies from other crates onto these: it's fine whether our other crates use caret/retry-error 0.1.0 or 0.1.1.
* Update Cargo.lock based on build.Nick Mathewson2022-04-011-4/+30
|
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 15:06:38 +0000