chore(deps): bump ofb from 0.6.1 to 0.7.1#1841
Conversation
Bumps [ofb](https://github.com/RustCrypto/block-modes) from 0.6.1 to 0.7.1. - [Commits](RustCrypto/block-modes@ofb-v0.6.1...ofb-v0.7.1) --- updated-dependencies: - dependency-name: ofb dependency-version: 0.7.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4fe1d7f8f0
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| checksum = "5f9e502b30c14fb1fecc196f9543975522c4380e4b0e8dcf4bf42e1d76375173" | ||
| dependencies = [ | ||
| "cipher", | ||
| "cipher 0.5.2", |
There was a problem hiding this comment.
Keep OFB on the same cipher stack as AES
This lockfile update moves ofb onto cipher 0.5, while the rest of the AES stack remains on cipher 0.4 (aes 0.8.4 still depends on cipher 0.4.4, and src/stdlib/{encrypt,decrypt}.rs instantiate Ofb::<aes::Aes{128,192,256}> through aes::cipher::KeyIvInit). Because the default feature set includes enable_crypto_functions/dep:ofb, a normal build now mixes incompatible cipher trait versions for the AES-OFB paths, so those encrypt/decrypt functions stop type-checking unless AES and the call sites are upgraded together or ofb stays on 0.6.x.
Useful? React with 👍 / 👎.
| [[package]] | ||
| name = "ofb" | ||
| version = "0.6.1" | ||
| version = "0.7.1" |
There was a problem hiding this comment.
Match the ofb lockfile version to Cargo.toml
This records ofb 0.7.1 in Cargo.lock, but the manifest still declares ofb = { version = "0.6", optional = true } in Cargo.toml:287; Cargo treats that as ^0.6 (>=0.6.0, <0.7.0), so the check-lockfile workflow in .github/workflows/test.yml (cargo update --workspace --locked) will reject the lockfile as out of sync rather than preserving this bump. Either update the manifest requirement along with compatible code changes or keep the lockfile on 0.6.x.
Useful? React with 👍 / 👎.
|
Looks like ofb is up-to-date now, so this is no longer needed. |
Bumps ofb from 0.6.1 to 0.7.1.
Commits
2fce505ImplementSetIvStatetrait (#114)e9a0336Release new versions dependent oncipherv0.5 (#113)504f0a6belt-ctr: use type alias to defineBeltCtr(#112)0ff441cAddallow(missing_docs)for benchmarks (#111)63a37c8Use release versions of block cipher crates (#110)a19e7bdWorkspace-level lint configuration (#108)fe63a2bcbc+ctr: cut new prereleases (#107)3dbbcf1Bumpcipherto v0.5.1 (#106)9745ef6cfb8: remove tail processing (#105)1403f56Adopt Trusted Publishing (#104)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)