Skip to content

Bump aes crate; aes* crates => MSRV 1.49+#252

Merged
tarcieri merged 1 commit intomasterfrom
bump-aes-crate
Dec 31, 2020
Merged

Bump aes crate; aes* crates => MSRV 1.49+#252
tarcieri merged 1 commit intomasterfrom
bump-aes-crate

Conversation

@tarcieri
Copy link
Member

The aes crate is a key component of several crates in this repo, and just had an MSRV breaking change in RustCrypto/block-ciphers#216.

This commit bumps the MSRV of all crates in this repo which use the aes crate to MSRV 1.49+.

In the case of aes-gcm and aes-gcm-siv specifically, the changes in RustCrypto/universal-hashes#113 bumped the MSRV of ghash and polyval to 1.49+ as well, so there are multiple motivations for this new MSRV.

@tarcieri
Copy link
Member Author

Note: I know bumping MSRV to a Rust version released today is aggressive, but I'm not in any hurry to release any of these crates.

I think it'd be good to spend time making sure cipher is in a good state before releasing a v0.3, and maybe look at doing another breaking release of universal-hash (and potentially aead) as well.

This repo is sort of an integration capstone for all of the crates, so I expect it will take awhile to sort all of the above out, by which point Rust 1.50 may be out and Rust 1.49 will seem less onerous.

The `aes` crate is a key component of several crates in this repo, and
just had an MSRV breaking change in RustCrypto/block-ciphers#216.

This commit bumps the MSRV of all crates in this repo which use the
`aes` crate to MSRV 1.49+.

In the case of `aes-gcm` and `aes-gcm-siv` specifically, the changes in
RustCrypto/universal-hashes#113 bumped the MSRV of `ghash` and `polyval`
to 1.49+ as well, so there are multiple motivations for this new MSRV.
@codecov-io
Copy link

codecov-io commented Dec 31, 2020

Codecov Report

Merging #252 (2f76aae) into master (a28702a) will increase coverage by 0.17%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #252      +/-   ##
==========================================
+ Coverage   84.97%   85.15%   +0.17%     
==========================================
  Files          31       31              
  Lines        1118     1118              
==========================================
+ Hits          950      952       +2     
+ Misses        168      166       -2     
Impacted Files Coverage Δ
crypto_box/tests/lib.rs 100.00% <0.00%> (+2.94%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a28702a...2f76aae. Read the comment docs.

@tarcieri tarcieri merged commit ca612a6 into master Dec 31, 2020
@tarcieri tarcieri deleted the bump-aes-crate branch December 31, 2020 18:25
tarcieri added a commit that referenced this pull request Jan 2, 2021
Like we did with the `aes` crate in #252, this bumps the `chacha20`
crate to a version which implements runtime CPU feature detection
(AVX2/SSE2) and uses new support for `ManuallyDrop` union fields which
became available in Rust 1.49.
tarcieri added a commit that referenced this pull request Jan 2, 2021
Like we did with the `aes` crate in #252, this bumps the `chacha20`
crate to a version which implements runtime CPU feature detection
(AVX2/SSE2) and uses new support for `ManuallyDrop` union fields which
became available in Rust 1.49.
tarcieri added a commit that referenced this pull request Jan 2, 2021
Like we did with the `aes` crate in #252, this bumps the `chacha20`
crate to a version which implements runtime CPU feature detection
(AVX2/SSE2) and uses new support for `ManuallyDrop` union fields which
became available in Rust 1.49.
tarcieri added a commit that referenced this pull request Jan 2, 2021
Like we did with the `aes` crate in #252, this bumps the `chacha20`
crate to a version which implements runtime CPU feature detection
(AVX2/SSE2) and uses new support for `ManuallyDrop` union fields which
became available in Rust 1.49.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants