Skip to content
Snippets Groups Projects
  1. Jul 08, 2023
  2. Mar 13, 2023
  3. Feb 15, 2023
  4. Feb 08, 2023
  5. Jan 19, 2023
  6. Dec 14, 2022
  7. Nov 02, 2022
  8. Oct 27, 2022
  9. Oct 26, 2022
    • Jungmin Park's avatar
      crypto/luks: Support creating LUKS image on Darwin · bf98afc7
      Jungmin Park authored
      
      When the user creates a LUKS-encrypted qcow2 image using the qemu-img
      program, the passphrase is hashed using PBKDF2 with a dynamic
      number of iterations. The number of iterations is determined by
      measuring thread cpu time usage, such that it takes approximately
      2 seconds to compute the hash.
      
      Because Darwin doesn't implement getrusage(RUSAGE_THREAD), we get an
      error message:
      > qemu-img: test.qcow2: Unable to calculate thread CPU usage on this platform
      for this command:
      > qemu-img create --object secret,id=key,data=1234 -f qcow2 -o 'encrypt.format=luks,encrypt.key-secret=key' test.qcow2 100M
      
      This patch implements qcrypto_pbkdf2_get_thread_cpu() for Darwin so that
      the above command works.
      
      Signed-off-by: default avatarJungmin Park <pjm0616@gmail.com>
      Signed-off-by: default avatarDaniel P. Berrangé <berrange@redhat.com>
      bf98afc7
  10. Jul 12, 2022
  11. May 26, 2022
  12. May 14, 2022
    • Paolo Bonzini's avatar
      crypto: make loaded property read-only · 0310641c
      Paolo Bonzini authored
      
      The ``loaded=on`` option in the command line or QMP ``object-add`` either had
      no effect (if ``loaded`` was the last option) or caused options to be
      effectively ignored as if they were not given.  The property is therefore
      useless and was deprecated in 6.0; make it read-only now.
      
      The patch is best reviewed with "-b".
      
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      0310641c
  13. May 11, 2022
  14. Apr 29, 2022
  15. Apr 28, 2022
  16. Apr 06, 2022
  17. Mar 22, 2022
  18. Mar 07, 2022
    • Daniel P. Berrangé's avatar
      crypto: mandate a hostname when checking x509 creds on a client · d41997e4
      Daniel P. Berrangé authored
      
      Currently the TLS session object assumes that the caller will always
      provide a hostname when using x509 creds on a client endpoint. This
      relies on the caller to detect and report an error if the user has
      configured QEMU with x509 credentials on a UNIX socket. The migration
      code has such a check, but it is too broad, reporting an error when
      the user has configured QEMU with PSK credentials on a UNIX socket,
      where hostnames are irrelevant.
      
      Putting the check into the TLS session object credentials validation
      code ensures we report errors in only the scenario that matters.
      
      Reviewed-by: default avatarEric Blake <eblake@redhat.com>
      Signed-off-by: default avatarDaniel P. Berrangé <berrange@redhat.com>
      Message-Id: <20220304193610.3293146-2-berrange@redhat.com>
      Signed-off-by: default avatarEric Blake <eblake@redhat.com>
      d41997e4
  19. Feb 21, 2022
  20. Jul 14, 2021
Loading