mirrors/arti.git/Cargo.toml, branch arti-v0.5.0

Revert toplevel part of "Lexically sort Cargo.toml dependencies"

2022-06-08T17:27:45Z

This reverts one file from commit bfd41ddb5fefe8808c33669c508dde4325808e35.

Lexically sort Cargo.toml dependencies

2022-05-28T17:05:51Z

Utilize cargo-sort: https://github.com/DevinR528/cargo-sort Signed-off-by: Orhun Parmaksız

Implement a safe-logging facility.

2022-05-06T11:36:48Z

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.

Merge branch 'fs-mistrust-v2' into 'main'

2022-05-03T14:28:28Z

Second cut at a fs-mistrust crate. See merge request tpo/core/arti!468

Second cut at a fs-mistrust crate.

2022-05-03T14:03:32Z

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.

Merge branch 'derive-builder-git-fixup' into 'main'

2022-04-27T14:31:08Z

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 patch

2022-04-27T13:57:59Z

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.

Fix grammar and typos

2022-04-27T12:52:13Z

Use git source for derive_builder for now, for sub_builder feature

2022-04-21T13:07:28Z

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.

Cargo.toml: Edit crate list to reflect dependencies

2022-04-01T15:19:32Z