Commit Graph

15 Commits

Author SHA1 Message Date
Brian Smith 16a2638bd0 Upgrade to *ring* 0.17 and untrusted 0.9.
untrusted 0.9 is used by *ring*. untrusted stopped providing a `PartialEq`
for `Input` in 0.9; this was the driver for all the code changes.
2023-10-02 14:24:17 -07:00
Brian Smith 177c39eee5 NFC: Address Clippy `clone_on_copy`. 2023-08-30 17:04:56 -07:00
Brian Smith ae7a99f281 NFC: Address Clippy `useless_asref`. 2023-08-30 17:04:56 -07:00
Brian Smith 6d409c9039 NFC: Address Clippy `redundant_closure`. 2023-08-30 17:04:56 -07:00
Brian Smith 0cd0b31beb Revert main branch crate contents to the 0.22.0 release contents.
Reset the crate contents (sources, tests, etc.)
to what they were at that commit, while retaining the newer CI
configuration.

The changes since the 0.22.0 release were primarily intended to
accomplish two goals:

* Fix and improve the GitHub Actions configuration.
* Prepare a 0.21.5 release that was backward compatible with 0.21.4
  but which also contained the improvements that were in 0.22.0.

0.21.5 was never released and will not be released. Therefore all
of the noise to facilitate the 0.21.5 release can just be deleted,
as long as we leave the CI changes that are necessary for GitHub
Actions to work correctly now.

The exact commands I used were:

```
git checkout \
    6c334a2cf5 \
    -- \
    Cargo.toml \
    LICENSE \
    README.md \
    src \
    tests \
    third-party
git rm src/trust_anchor_util.rs
```

Commit 6c334a2cf5 was the commit from
which 0.22.0 was released. It is confusing because the commit
immediately prior, 0b7cbf2d32, has
commit message "0.22.0". It appears that I merged the "0.22.0"
commit, expecting to `cargo publish` from that commit, but then
`cargo publish` failed. Then I added
6c334a2cf5 to fix `cargo publish`
and did the `cargo publish` from that commit. That's why I added
the `package` CI step at that time, to prevent this confusing
situation from happening again.

`trust_anchor_utils.rs` was not in 0.22.0; the `git checkout` didn't
delete it, so I had to do it separately.

I left the tests added subsequent to 0.22.0 in `tests/` (e.g.
`name_tests.rs`) since those tests pass with the 0.22.0 sources too.

Unfortunately, this requires disabling a bunch of Clippy lints, to
avoid modifying the contents from 0.22.0.

(I know it is confusing. It took me a while to figure it out myself
today.)
2023-08-30 08:31:51 -07:00
Brian Smith 97507d40ab Appease the newest stable Clippy. 2021-12-13 21:44:26 -08:00
Brian Smith 17d9189981 Temporarily undo some renaming that can't be alised, to get back webpki 0.21.4 compat.
Make it easier to maintain support for Rustls 0.19.1 by restoring the webpki main branch to a
state compatible with webpki 0.21.4.
2021-05-07 15:12:11 -07:00
Brian Smith cd59614740 Rename internal names to conform to Rust conventions. 2021-04-09 15:58:41 -07:00
Brian Smith 5b67fb92da Rename error variants according to Rust conventions. 2021-04-09 15:58:41 -07:00
Brian Smith 4942c65d97 Tweak `AllowWildcards` to pass `clippy::needless-pass-by-value`. 2021-02-18 13:50:37 -08:00
Brian Smith 0789a90d94 Avoid using `as` for conversions from `Tag` to `u8`.
*ring* added a safer way to do this conversion a while back.
2021-02-18 12:30:28 -08:00
Stiopa Koltsov db1f0d1d64 Fix clippy warnings
I agree to license my contributions to each file under the terms given at the top of each file I changed.
2021-02-17 00:24:12 -08:00
Brian Smith 13a50e7dfb Move `EndEntityCert` to its own module. 2021-01-25 21:49:15 -08:00
Brian Smith 2deeb79c74 Refactor features.
Test all feature configurations in CI.

Remove the `trust_anchor_utils` feature flag.

Guard all features that directly require allocation with a new `alloc` feature.
The RSA features will be handled separately.

Document the features. Tell docs.rs to document all features.

Adjust some tests so that tests are run in more configurations.
2021-01-07 00:36:28 -08:00
Brian Smith cf94476d5c Split DNS name and IP address aspects of `name` into their own modules. 2020-12-29 23:40:43 -08:00