1. 16 6月, 2020 38 次提交
  2. 15 6月, 2020 2 次提交
    • P
      Merge remote-tracking branch 'remotes/berrange/tags/qcrypto-next-pull-request' into staging · 53550e81
      Peter Maydell 提交于
      Misc crypto subsystem fixes
      
      * Improve error message for large files when creating LUKS volumes
      * Expand crypto hash benchmark coverage
      * Misc code refactoring with no functional change
      
      # gpg: Signature made Mon 15 Jun 2020 11:35:17 BST
      # gpg:                using RSA key DAF3A6FDB26B62912D0E8E3FBE86EBB415104FDF
      # gpg: Good signature from "Daniel P. Berrange <dan@berrange.com>" [full]
      # gpg:                 aka "Daniel P. Berrange <berrange@redhat.com>" [full]
      # Primary key fingerprint: DAF3 A6FD B26B 6291 2D0E  8E3F BE86 EBB4 1510 4FDF
      
      * remotes/berrange/tags/qcrypto-next-pull-request:
        crypto: Remove use of GCRYPT_VERSION macro.
        test-crypto-secret: add 'secret_keyring' object tests.
        crypto/linux_keyring: add 'secret_keyring' secret object.
        crypto/secret: move main logic from 'secret' to 'secret_common'.
        crypto: add "none" random provider
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      53550e81
    • R
      crypto: Remove use of GCRYPT_VERSION macro. · d6cca8e1
      Richard W.M. Jones 提交于
      According to the gcrypt documentation it's intended that
      gcry_check_version() is called with the minimum version of gcrypt
      needed by the program, not the version from the <gcrypt.h> header file
      that happened to be installed when qemu was compiled.  Indeed the
      gcrypt.h header says that you shouldn't use the GCRYPT_VERSION macro.
      
      This causes the following failure:
      
        qemu-img: Unable to initialize gcrypt
      
      if a slightly older version of libgcrypt is installed with a newer
      qemu, even though the slightly older version works fine.  This can
      happen with RPM packaging which uses symbol versioning to determine
      automatically which libgcrypt is required by qemu, which caused the
      following bug in RHEL 8:
      
        https://bugzilla.redhat.com/show_bug.cgi?id=1840485
      
      qemu actually requires libgcrypt >= 1.5.0, so we might put the string
      "1.5.0" here.  However since 1.5.0 was released in 2011, it hardly
      seems we need to check that.  So I replaced GCRYPT_VERSION with NULL.
      Perhaps in future if we move to requiring a newer version of gcrypt we
      could put a literal string here.
      Signed-off-by: NRichard W.M. Jones <rjones@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      d6cca8e1