summaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
* Two more patchlevel bumpsNick Mathewson2023-12-048-9/+9
| | | | | | | | | These crates both depend on tor-error. Since tor-error got a patchlevel bump, they now depend on the new version, which means by our rules that _they_ get a patchlevel bump themselves. tor-geoip tor-rpcbase
* Bump minor versions in preparation for releaseNick Mathewson2023-12-0432-183/+183
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This crate is new, and gets a bump to 0.1.0. tor-log-ratelim This crate had a breaking change: tor-persist tor-llcrypto had a breaking change. These crates _are_ tor-llcrypto, or (transitively) depend on it. I am assuming that they all re-expose something from it in a way that matters: tor-llcrypto tor-bytes tor-hscrypto tor-socksproto tor-checkable tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-consdiff tor-netdir tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr tor-keymgr tor-hsclient tor-hsservice tor-hsrproxy arti-client arti-rpcserver arti-hyper
* Bump patchlevel versions in preparation for releaseNick Mathewson2023-12-0434-97/+97
| | | | | | | | | | | | | | | These crates had backward-compatible changes, and get a patchlevel bump only: fs-mistrust tor-error tor-config tor-rtcompat tor-rtmock This crate exposes no non-CLI APIs, and gets a patchlevel bump only: arti
* Run fixup-features in preparation for release.Nick Mathewson2023-12-043-2/+3
|
* arti cfg: suppress a warningIan Jackson2023-12-041-0/+1
| | | | | | | | | | | | | There is a TODO HSS for this. Fixes cargo check --workspace --all-targets producing warning: unused variable: `result` --> crates/arti/src/cfg.rs:1060:13 | 1060 | let result = file.resolve::<(TorClientConfig, ArtiConfig)>(); | ^^^^^^ help: if this is intentional, prefix it with an underscore: `_result` | = note: `#[warn(unused_variables)]` on by default
* Move from `trust-dns` to `hickory`Andrew2023-11-302-8/+8
| | | | | | This is not a change of ownership but just rebranding. Signed-off-by: Andrew <[email protected]>
* Merge branch 'hss-notes' into 'main'Ian Jackson2023-11-303-0/+118
|\ | | | | | | | | hssvc-ipt-algorithms.md: Move and fix up some text See merge request tpo/core/arti!1777
| * tor-hsclient: ipt_establisher: Fix a broken rustdoc linkIan Jackson2023-11-301-1/+1
| | | | | | | | | | | | This rune RUSTDOCFLAGS="-Dwarnings --cfg docsrs" nailing-cargo +nightly doc --all-features --document-private-items --no-deps is clean now.
| * hssvc-ipt-algorithms.md: Fix moved text syntaxIan Jackson2023-11-291-2/+2
| | | | | | | | | | Fixes a rustdoc warning. This was already wrong in the .md file but nothing checked it there.
| * hssvc-ipt-algorithms.md: Move some text to ipt_setIan Jackson2023-11-292-0/+72
| | | | | | | | | | This is describing the detailed algorithm in compute_iptsetstatus_publish. Move it there (and add an xref).
| * hssvc-ipt-algorithms.md: Move some text to ipt_mgrIan Jackson2023-11-292-0/+37
| | | | | | | | | | This is describing the detailed algorithm in idempotently_progress_things_now. Move it there (and add an xref).
| * hssvc-ipt-algorithms.md: Delete rendundant textIan Jackson2023-11-292-0/+9
| | | | | | | | | | | | | | | | This is describing our data structures and IPT states. But we have this documented elsewhere, largely. There are a few sentences here that can usefully be replaced with a bit of extra text in the data structure docs.
* | Merge branch 'remove-impl' into 'main'Ian Jackson2023-11-301-9/+1
|\ \ | | | | | | | | | | | | tor-keymgr: Remove unnecessary impls for KeystoreCorruptionError. See merge request tpo/core/arti!1779
| * | tor-keymgr: Remove unnecessary impls for KeystoreCorruptionError.Gabriela Moldovan2023-11-291-9/+1
| | | | | | | | | | | | | | | | | | | | | These impl only exist because they were needed back when we didn't have the `tor_keymgr::Error` enum and all errors _had_ to implement `KeystoreError`. They are not used or required anymore, so let's remove them.
* | | Merge branch 'msrv-bump-1.70' into 'main'Ian Jackson2023-11-3050-50/+50
|\ \ \ | | | | | | | | | | | | | | | | Increase our MSRV to 1.70 See merge request tpo/core/arti!1773
| * | | In every crate, change rust-version to 1.70.Nick Mathewson2023-11-2850-50/+50
| | | |
* | | | Merge branch 'report_error_message' into 'main'gabi-2502023-11-304-9/+23
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Preserve HTTP status text in dirclient errors. See merge request tpo/core/arti!1780
| * | | | Preserve HTTP status text in dirclient errors.Nick Mathewson2023-11-294-9/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The HTTP status text is often useful for diagnosing errors. Tor directory and hsdir caches frequently put useful messages there, especially when rejecting an uploaded document. Inspired by #1142.
* | | | | Merge branch 'rustdoc_fix' into 'main'Nick Mathewson2023-11-301-1/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Fix a rustdoc error. See merge request tpo/core/arti!1781
| * | | | | Fix a rustdoc error.Nick Mathewson2023-11-291-1/+1
| | | | | |
* | | | | | hsrproxy: Allow ports to be specified as integersNick Mathewson2023-11-291-5/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, we required the user to specify a pattern matching a single port as `"80"`, with quotes. Now we allow the user to omit the quotes.
* | | | | | Revert "hsrproxy: Temporarily change the format of ProxyRule."Nick Mathewson2023-11-294-85/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 21605d2c9e601c3a5099bfd8d8c887cbb3b36c0a. We're doing this because we wanted the configuration of proxy rules to be a 2-tuple, as in `[ "22", "127.0.0.1:22" ]`. But `config` couldn't handle that before, so we temporarily changed it to a string, as in "22 => 127.0.0.1:22". Closes #1058.
* | | | | | Require config ≥ 0.13.4Nick Mathewson2023-11-293-4/+4
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This version of the config crate includes a fix for the issue (https://github.com/mehcode/config-rs/issues/464) that had prevented us from using the format we had wanted for our rproxy configuration.
* | | | | Merge branch 'semver-breaking-upgrade-of-the-daleks' into 'main'Nick Mathewson2023-11-2935-579/+344
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | Convert to the latest versions of dalek-cryptography Closes #808 See merge request tpo/core/arti!1767
| * | | | Resolve an unfinished sentenceNick Mathewson2023-11-291-1/+2
| | | | |
| * | | | grammar fix in commentgabi-2502023-11-291-1/+1
| | | | |
| * | | | llcrypto: remove a comment suggesting a grand renaming.Nick Mathewson2023-11-291-3/+3
| | | | |
| * | | | llcrypto testvec: remove redundant "kp" variable.Nick Mathewson2023-11-291-11/+6
| | | | |
| * | | | llcrypto: Hide the members of ExpandedKeypair.Nick Mathewson2023-11-297-27/+39
| | | | | | | | | | | | | | | | | | | | | | | | | With this change, we no longer expose the ExpandedSecretKey unescorted, which makes it harder to misuse the API.
| * | | | llcrypto: Undo internal ed25519-dalek renamings in keymanip.rsNick Mathewson2023-11-291-8/+7
| | | | |
| * | | | llcrypto: Remove redundant re-exports in keymanip.Nick Mathewson2023-11-294-13/+7
| | | | | | | | | | | | | | | | | | | | (These types were all already re-exported from pk::ed25519.)
| * | | | llcrypto: Remove ExpandedSecretKey export.Nick Mathewson2023-11-293-11/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This type was part of `hazmat`, and was no longer necessary anywhere in our codebase. (It had one remaining user, which was easy enough to remove.) By removing it, we remove the opportunity for using an unescorted ed25519 private key.
| * | | | Fix a typo in comment in llcrypto.Nick Mathewson2023-11-291-1/+1
| | | | |
| * | | | Clarify and downgrade TODO about ReusableSecret.Nick Mathewson2023-11-291-1/+8
| | | | |
| * | | | Deprecate convert_ed25519_to_curve25519_private as unusedNick Mathewson2023-11-292-0/+6
| | | | |
| * | | | Remove RngCompatExt.Nick Mathewson2023-11-2920-299/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This code was needed with the old version of dalek-cryptography, which wasn't compatible with up-to-date versions of the `rand` crate(s). But now that we've upgraded, we can drop this. (We could have left it around and deprecated it, but we are already making a breaking change to tor-llcrypto by upgrading dalek-cryptography.)
| * | | | Convert to the latest versions of dalek-cryptographyNick Mathewson2023-11-2934-269/+292
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The main changes that we have to adjust for are as follows: * In x25519-dalek: * `StaticSecret` is now behind a feature. * `StaticSecret::new` is deprecated in favor of `StaticSecret::random_from_rng`. * StaticSecret no longer does its own clamping. * In ed25519-dalek: * `SecretKey` has (in effect) been renamed to `SigningKey`. The name `SecretKey` is now an alias for `[u8; 32]`. * `SigningKey` is effectively a keypair, since it contains a public key as well. * `PublicKey` has been renamed to `VerifyingKey`. * The functions to extract a signing key and verifying key have been renamed as you might expect. * `ExpandedSecretKey` has been moved to `hasmat` and no longer implements `sign`. * `ExpanededSecretKey` now has as its elements a scalar and a hash prefix. * Various functions that took `&[u8]` now take `&[u8; N]`. * We no longer need a wrapper for older versions of rand. There is a single test in tor-keymgr that does not pass. I've marked it as ignore for now, in hopes that @gabi-250 can help me figure it out. This closes #808. There are several changes I want to make before we merge, however. They are marked with TODO DALEK.
* | | | | debug log: Downgrade circuit lifecycle messages to traceIan Jackson2023-11-291-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes it possible to see the wood for the trees. This may be controversial, but I think it's an improvement.
* | | | | Downgrade some messages to traceIan Jackson2023-11-294-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | These messages are very verbose and I doubt anyone will want them, usually, even when debugging.
* | | | | Merge branch 'persist-tempdir' into 'main'Ian Jackson2023-11-294-25/+354
|\ \ \ \ \ | |_|_|/ / |/| | | | | | | | | | | | | | tor-hsservice tests: Introduce new test_temp_dir helper module See merge request tpo/core/arti!1762
| * | | | tor-hsservice: test_temp_dir: Fix comment syntaxNick Mathewson2023-11-291-1/+1
| | | | |
| * | | | tor-hsservice: test_temp_dir: Rename to used_byIan Jackson2023-11-292-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from obtain_in. As per irc discussion.
| * | | | tor-hsservice: test_temp_dir: Rename to TestTempDirGuardIan Jackson2023-11-292-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from UsingTempDir. As per irc discussion.
| * | | | tor-hsservice: test_temp_dir: Expand on the TODO (fmt)Ian Jackson2023-11-291-1/+0
| | | | | | | | | | | | | | | | | | | | Mandatory whitespace degradation.
| * | | | tor-hsservice: test_temp_dir: Expand on the TODOIan Jackson2023-11-291-1/+3
| | | | |
| * | | | tor-hsservice test_temp_dir: Add commentary about why do thisIan Jackson2023-11-291-0/+25
| | | | |
| * | | | tor-hsservice test_temp_dir: Add more docs about in_obtainIan Jackson2023-11-291-0/+5
| | | | |
| * | | | tor-hsservice test_temp_dir: Add docs about early deletion hazardIan Jackson2023-11-291-0/+19
| | | | |
| * | | | tor-hsservice test_temp_dir: Make a lifetime explicit (fmt)Ian Jackson2023-11-291-1/+5
| | | | |
| * | | | tor-hsservice test_temp_dir: Make a lifetime explicitIan Jackson2023-11-291-1/+1
| | | | |