Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] master from RustCrypto:master #4

Open
wants to merge 263 commits into
base: master
Choose a base branch
from

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 26, 2020

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

aloucks and others added 3 commits February 25, 2020 21:29
Use `thiserror` instead of `failure`
Rename `serde1` feature to `serde`
@pull pull bot added ⤵️ pull merge-conflict Resolve conflicts manually labels Feb 26, 2020
baloo and others added 30 commits November 27, 2023 17:35
…ds (#386)

This is used on Yubico HSM for import/export under wrap as well as when
importing a key unsealed.
This reverts commit 00eaa91.

Unfortunately while `#` comments work in rustdoc, they are visible when
GitHub renders the README.md, so this doesn't work.
This returns the `AlgorithmIdentifierOwned` assuming the default
situation where the salt_len is the `output_size` of the `Digest`.

This is meant to be used by HSM where the private key is hidden behind
an abstraction but to still expose a `DynSignatureAlgorithmIdentifier`
trait.
This allows reuse of the `RsaSignatureAssociatedOid` trait to pull
implementation of `SignatureAlgorithmIdentifier` in other crates (like
`yubihsm.rs`).
Bumps [spki](https://github.com/RustCrypto/formats) from 0.7.2 to 0.7.3.
- [Commits](RustCrypto/formats@spki/v0.7.2...spki/v0.7.3)

---
updated-dependencies:
- dependency-name: spki
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Added
 - expose a `pss::get_default_pss_signature_algo_id` helper ([#393])
 - expose `pkcs1v15::RsaSignatureAssociatedOid` ([#392])
Newer versions of rustc report these. They were previously ignored
because they were `pub use`, but inside of a non-`pub` module.
NOTE: not for release.

This signifies that we are going to make breaking changes to the
`master` branch which are incompatible with v0.9 releases.

The first prerelease of this series published to crates.io will be
v0.10.0-pre.0 at some point in the future.
This makes it possible to use `rsa` with prerelease versions of
`x509-cert`.

Bumps the following dependencies:

- `const-oid` v0.10.0-pre.2
- `digest` v0.11.0-pre.7
- `pkcs1` v0.8.0-pre.0
- `pkcs8` v0.11.0-pre.0
- `signature` v2.3.0-pre.2
- `sha1` v0.11.0-pre.2
- `sha2` v0.11.0-pre.2
- `sha3` v0.11.0-pre.2
- `spki` v0.8.0-pre.0
Bumps the following:

- `digest` v0.11.0-pre.8
- `signature` v2.3.0-pre.3
- `sha1` v0.11.0-pre.3
- `sha2` v0.11.0-pre.3
This contains a Docker image which can be used for testing for the Marvin Attack:

https://people.redhat.com/~hkario/marvin/
* pkcs1v15: ensure that these keys are used only with the old RSA OID

RSA PSS keys can be used either with the old rsaEncryption OID or with
the id-RSASSA-PSS, while PKCS1v15 are limited to rsaEncryption. Enforce
this limitation before adding support for is-RSASSA-PSS handling.

Signed-off-by: Dmitry Baryshkov <[email protected]>

* feat: allow id-RSASSA-PSS in verify_algorithm_id()

Allow both rsaEncoding and id-RSASSA-PSS OIDs in verify_algorithm_id().

Signed-off-by: Dmitry Baryshkov <[email protected]>

* pss: support DecodePrivateKey and DecodePublicKey traits

Implement necessary conversion traits to enable DecodePrivateKey and
DecodePublicKey traits implementation.

---------

Signed-off-by: Dmitry Baryshkov <[email protected]>
Co-authored-by: Tony Arcieri <[email protected]>
Updates the following dependencies:

    $ cargo update
    Updating crates.io index
    Updating aes v0.8.3 -> v0.8.4
    Updating autocfg v1.1.0 -> v1.3.0
    Removing bitflags v1.3.2
    Removing bitflags v2.4.1
      Adding bitflags v2.5.0
    Updating cpufeatures v0.2.11 -> v0.2.12
    Updating errno v0.3.7 -> v0.3.9
    Updating fastrand v2.0.1 -> v2.1.0
    Updating getrandom v0.2.11 -> v0.2.15
    Updating hybrid-array v0.2.0-rc.5 -> v0.2.0-rc.8
    Updating libc v0.2.150 -> v0.2.155
    Updating linux-raw-sys v0.4.11 -> v0.4.14 (latest: v0.6.4)
    Updating num-integer v0.1.45 -> v0.1.46
    Updating num-iter v0.1.43 -> v0.1.45
    Updating num-traits v0.2.17 -> v0.2.19
    Updating proc-macro2 v1.0.79 -> v1.0.85
    Updating quote v1.0.35 -> v1.0.36
    Removing redox_syscall v0.4.1
    Updating regex-syntax v0.8.2 -> v0.8.3
    Updating rustix v0.38.25 -> v0.38.34
    Updating serde v1.0.197 -> v1.0.203
    Updating serde_derive v1.0.197 -> v1.0.203
    Updating smallvec v1.11.2 -> v1.13.2
    Updating syn v2.0.53 -> v2.0.66
    Updating tempfile v3.8.1 -> v3.10.1
    Updating windows-sys v0.48.0 -> v0.52.0
    Updating windows-targets v0.48.5 -> v0.52.5
    Updating windows_aarch64_gnullvm v0.48.5 -> v0.52.5
    Updating windows_aarch64_msvc v0.48.5 -> v0.52.5
    Updating windows_i686_gnu v0.48.5 -> v0.52.5
      Adding windows_i686_gnullvm v0.52.5
    Updating windows_i686_msvc v0.48.5 -> v0.52.5
    Updating windows_x86_64_gnu v0.48.5 -> v0.52.5
    Updating windows_x86_64_gnullvm v0.48.5 -> v0.52.5
    Updating windows_x86_64_msvc v0.48.5 -> v0.52.5
    Updating zeroize v1.7.0 -> v1.8.1
As per #418, let me know if this is the preferred way or if you'd rather
remove the limit some other way

Co-authored-by: Gabriele Musco <[email protected]>
Bumps the following dependencies to their latest prerelease versions:

- `const-oid` v0.10.0-rc.0
- `digest` v0.11.0-pre.9
- `pkcs1` v0.8.0-rc.0
- `pkcs8` v0.11.0-rc.0
- `signature` v2.3.0-pre.4
- `spki` v0.8.0-rc.0
- `sha1` v0.11.0-pre.4
- `sha2` v0.11.0-pre.4

Note: `pkcs5` is temporarily sourced from this PR due to circular
dependency problems:

RustCrypto/formats#1461
Some vendor serialization (NDA :() of signature and public keys will
need the size of the salt that was used for signature. Sadly this is
only exposed in the signing key (which may be out of reach (HSM)).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⤵️ pull merge-conflict Resolve conflicts manually
Projects
None yet
Development

Successfully merging this pull request may close these issues.