On Fri, Sep 04, 2009 at 08:32:26AM +0200, Henk M. de Bruijn wrote:
On Thu, 03 Sep 2009, at 22:26:31 [GMT -0700] (which was 7:26 where I
live) Joseph Oreste Bruni wrote:
Joseph Oreste Bruni wrote:
Here is a UI enhancement request: In the edit-key menu, typing uid
* selects all UID's.
On Thu, 03 Sep 2009, at 22:26:31 [GMT -0700] (which was 7:26 where I
live) Joseph Oreste Bruni wrote:
Joseph Oreste Bruni wrote:
Here is a UI enhancement request: In the edit-key menu, typing uid
* selects all UID's. Currently, I have to type uid # for every UID
individually. Typing uid by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 4 Sep 2009, at 09:49:34 [GMT +0300] (which was 8:49 where I
live) Peter Pentchev wrote:
On Fri, Sep 04, 2009 at 08:32:26AM +0200, Henk M. de Bruijn wrote:
On Thu, 03 Sep 2009, at 22:26:31 [GMT -0700] (which was 7:26 where I
live) Joseph
On Sep 4, 2009, at 12:05 AM, Henk M. de Bruijn wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 4 Sep 2009, at 09:49:34 [GMT +0300] (which was 8:49 where I
live) Peter Pentchev wrote:
On Fri, Sep 04, 2009 at 08:32:26AM +0200, Henk M. de Bruijn wrote:
On Thu, 03 Sep 2009, at
Hi,
im sending *.gpg Mail-Attachments to external Customers , but our
EmailFilter - BCC Mail protect Quarantine stopps the and we have to
release them manual.
I need the HEX File Siganture for GPG Files to customize that in BCC Mail
Protect .
Thanks
Mit freundlichen Grüßen/Best Regards
On Sep 4, 2009, at 10:06 AM, joachim.blomb...@vr-leasing.de wrote:
Hi,
im sending *.gpg Mail-Attachments to external Customers , but our
EmailFilter - BCC Mail protect Quarantine stopps the and we have to
release them manual.
I need the HEX File Siganture for GPG Files to customize that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi list,
when symmetrically encrypting a file, e.g.:
$ gpg --output file.ods.gpg --symmetric file.ods
the command above generates a gpg extension encrypted AND compressed
file, is that correct?
How do I know which compression algorithm was used?
On 04.09.2009, Werner Koch wrote:
We are pleased to announce the availability of a new stable GnuPG-2
release: Version 2.0.13.
[]
I'm unable to compile this version on my system. The configure script
bails out with the following message:
[]
checking for nl_langinfo and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
David Koppenhofer wrote:
I asked the same question in the form of a bug report on g10code
https://bugs.g10code.com/gnupg/issue1126
As you can see from the bug, it was recommended that I use gpg4win -
nevermind the fact I don't want or need all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
What is the reason for the Windows build of 1.4.10 (both the pulled and
fixed binaries) not supporting BZIP2?
D:\Testgpg --version
gpg (GnuPG) 1.4.9
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
Il /04 set 2009/, *John W. Moore III* ha scritto:
Thanks David. Rather than resetting the preferences on My Key and
then asking every correspondent to update the copy on their
Keyring I suppose I shall remain using 1.4.10svn5068 to avoid
receiving messages that I cannot decrypt if they were
On Friday, September 04, 2009, at 01:48PM, Johan Wevers
joh...@vulcan.xs4all.nl wrote:
Compiles and runs fine on Slackware 10.
However, 2 small points: the signature check claims the key has expired, and
gpg --version says it's from 2008.
Werner's current key includes subkeys that don't
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello !
I'm trying 1.4.10a but I get a warning:
gpg: uncompressing failed: unknown compress algorithm
with old messages that previously were decrypted with 1.4.9
I had to suppress Z3 from the compression list; worked with 1.4.9 but
13 matches
Mail list logo