qemu-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-commits] [qemu/qemu] fff2f9: crypto: do an explicit check for nett


From: GitHub
Subject: [Qemu-commits] [qemu/qemu] fff2f9: crypto: do an explicit check for nettle pbkdf func...
Date: Wed, 30 Mar 2016 08:30:07 -0700

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: fff2f982ab6ac0dd2b641d30303f72270a019f28
      
https://github.com/qemu/qemu/commit/fff2f982ab6ac0dd2b641d30303f72270a019f28
  Author: Daniel P. Berrange <address@hidden>
  Date:   2016-03-30 (Wed, 30 Mar 2016)

  Changed paths:
    M configure
    M crypto/Makefile.objs

  Log Message:
  -----------
  crypto: do an explicit check for nettle pbkdf functions

Support for the PBKDF functions in nettle was not introduced
until version 2.6. Some distros QEMU targets have older
versions and thus lack PBKDF support. Address this by doing
a check in configure for the desired function and then skipping
compilation of the nettle-pbkdf.o module

Reported-by: Wen Congyang <address@hidden>
Tested-by: Wen Congyang <address@hidden>
Signed-off-by: Daniel P. Berrange <address@hidden>


  Commit: 69bc7f5029db5ea55359f7905e9829777ae5a34f
      
https://github.com/qemu/qemu/commit/69bc7f5029db5ea55359f7905e9829777ae5a34f
  Author: Peter Maydell <address@hidden>
  Date:   2016-03-30 (Wed, 30 Mar 2016)

  Changed paths:
    M configure
    M crypto/Makefile.objs

  Log Message:
  -----------
  Merge remote-tracking branch 
'remotes/berrange/tags/pull-qcrypto-2016-03-30-1' into staging

Merge qcrypto fixes 2016/03/30 v1

# gpg: Signature made Wed 30 Mar 2016 14:59:19 BST using RSA key ID 15104FDF
# gpg: Good signature from "Daniel P. Berrange <address@hidden>"
# gpg:                 aka "Daniel P. Berrange <address@hidden>"

* remotes/berrange/tags/pull-qcrypto-2016-03-30-1:
  crypto: do an explicit check for nettle pbkdf functions

Signed-off-by: Peter Maydell <address@hidden>


Compare: https://github.com/qemu/qemu/compare/b9c27e7ae6fb...69bc7f5029db

reply via email to

[Prev in Thread] Current Thread [Next in Thread]