Page MenuHome GnuPG

Libgcrypt in Gpg4Win has AES-NI support disabled
Closed, ResolvedPublic

Description

Commit 85fb77359606462731eb8ee86398d1895b60196a by werner disabled libgcrypt
AES-NI support in gpg4win

"

There is a problem wit VirtualBox when using AES-NI.  Disabling
AES-NI for gpg-agent seems to be sufficient but we better play safe
and disable it completely.

Note that there is no problem with the Libgcrypt tests programs; even
the backported alignment test for 1.6 works fine.  Needs to be
investigated further.

"

This issue should track the further investigation.

Next steps: build a version with aesni support and try to reproduce the problem
on a system that supports it and in VirtualBox.

Werner can you elaborate on the Test you did? Would just encrypting something
with gpgsm (--cipher-algo AES) be enough?

Event Timeline

Since then we did a lot of work on Libgcrypt so that the AES-NI code is
different from May 2012. It is possible that we accidently clobbered a register
which might have been the reason for the VirtualBox failure.

I can't remember the test case, but any use of AES should have hit it. Just use
gpg where AES is the default anyway. I suggest to revert that patch an see what
happens.

AESNI is enabled in the gnupg 2.1 installer which we will use with gpg4win 3.0