On Wed, 28 Nov 2007 10:06, [EMAIL PROTECTED] said:
> Werner, do you use GetFileSize or GetFileSizeEx? There are also
Since 1.4.3 we are using GetFileSizeEx if available on the platform. We
use it todecide whether a file is close to 4GB - if this is the case we
use OpenPGP's partial encoding form
On Wed, 28 Nov 2007 00:59, [EMAIL PROTECTED] said:
> I also recall that Werner stated the AES code in GnuPG wouldn't be
> optimized for a number of reasons, becasue of security (timing
> attacks), and also a desire to keep GnuPG architecture-agnostinc. The
Nope. It is just that nobody has found
Hi again,
I found the old thread: Trouble decrypting AES256 symmetric encrypted file:
You (Ryan) wrote:
This is surpisingly *not* a Windows issue. We have 200+ GB database
files on many of our database servers. All using NTFS.
I think the issue is that GnuPG is using a 32-bit DWORD file pointer
> Snoken wrote:
> > is the old problem with files greater than 4 GB solved? How large
> > files can gpg handle on WindowsXP? On other systems?
My recollection is that the file size issue was fixed years ago, as it
was a limitation in the MinGW layer or something that was remedied. I
never followed
Snoken wrote:
> is the old problem with files greater than 4 GB solved? How large
> files can gpg handle on WindowsXP? On other systems?
Depends a lot on your filesystem. FAT32 doesn't like files greater than
4GB, no matter what program makes them. NTFS does not have this limitation.
I have see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
is the old problem with files greater than 4 GB solved? How large
files can gpg handle on WindowsXP? On other systems?
Snoken
At 00:39 2007-11-18, you wrote:
- --snip--
>I found a thread discussing a similar decryption problem in the Gnupg-users
