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

core: use fips-compatible padding for provider passwords #677

Merged
merged 2 commits into from
Sep 27, 2022

Commits on Sep 26, 2022

  1. [NOT MERGE]ovn provider auth: use fips-compatible padding

    Use OAEP with SHA256 and MGF1 padding in password encryption and
    decryption during authenticating with ovirt-ovn-provieder on el9
    deployments where FIPS is enabled.
    
    This change should not be merged until all code paths using the modified
    EngineEncryptionUtils facility are evaluated for correctness and until
    this modification is made active only when FIPS is enabled.
    
    Signed-off-by: Eitan Raviv <eraviv@redhat.com>
    Signed-off-by: Marcin Sobczyk <msobczyk@redhat.com>
    Change-Id: Ie895d2249716d6aafd64d79ae2d61083181b9703
    erav authored and tinez committed Sep 26, 2022
    Configuration menu
    Copy the full SHA
    ad2e339 View commit details
    Browse the repository at this point in the history

Commits on Sep 27, 2022

  1. Configuration menu
    Copy the full SHA
    892f923 View commit details
    Browse the repository at this point in the history