libgcrypt-1.6 removed the entire module interface (upstream commit http://git.gnupg.org/cgi-bin/gitweb.cgi ... 64e2331752). The "ntfsdecrypt" utility uses this interface, so it does not build:



That's from ntfs-3g_ntfsprogs-2013.1.13, configured with --enable-crypto --enable-extras.

It looks like only ntfsdecrypt uses libgcrypt, and it is not built by default, so this is fairly minor. Unfortunately fixing it is also not entirely trivial, as I do not think libgcrypt provides a replacement for the module system (see the commit message I linked to).

Anyone affected by this can work around it by not configuring with --enable-crypto.

Hi,


Moreover, ntfs encryption is only supported by professional builds of Windows, which I do not have. I can do something about it only if somebody makes available a test set with the three pieces below :

- an encrypted file (to be extracted using the efs_raw mount option),
- the EFS information associated to the file (see http://www.tuxera.com/community/ntfs-3g ... s/#efsinfo)
- the encryption key in pkcs#12 format (*.pfx) of a user allowed to decrypt the file, with the private key included (which can apparently be extracted from Windows through the command "mmc.exe")

Obviously, only test files and keys should be posted.

Apart from downgrading to libgcrypt-1.5, this is unfortunately the only thing that can be done for the short term.

Regards

Jean-Pierre

Hi,

Attached is a patch for using libgcrypt in a different way, compatible with both existing libgcrypt and upcoming libgcrypt-1.6

Regards

Jean-Pierre