Charly Avital wrote:
> Thanks for the information. I have never succeeded to build gpg 1.9.xx
> on MacOS, in spite of help and tips from WK, so I gave it up.
>
> If you are kind enough to keep posting your findings and tips, I shall
> be very grateful.
> Charly
Well, everything seems to work as e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks for your message.
All these issues are well beyond my very basic grasp, so I'll just lay
back and wait for you to come up with more solutions ;-)
Remco Post wrote the following on 3/9/06 3:10 AM:
[...]
>
> Well, everything seems to work as
On Wed, 08 Mar 2006, David Shaw wrote:
> > Thanks, that seems to work (as does --expert and sign).
>
> If you're tracking SVN, try the latest. I've added a notation command
> under --edit-key.
Great, thanks. Adding notations and removing all of them works just
fine.
According to the manual pa
GnuPG does not detect injection of unsigned data
(released 2006-03-09, CVE-2006-0049)
Summary
===
In the aftermath of the false positive signature verfication bug
(announced 2006-02-15) more thorough test
On Thu, Mar 09, 2006 at 02:40:33PM +0100, Peter Palfrader wrote:
> | [EMAIL PROTECTED]:~/tmp/gpg$ gpg --edit test1
> [..]
> | Command> notation [EMAIL PROTECTED]
> | No notations on user ID "test1"
> | Adding notation: [EMAIL PROTECTED]
> [..]
> [just doing 'notation [EMAIL PROTECTED]' is not allo
On Thu, 09 Mar 2006, David Shaw wrote:
> Let's make it simpler: I just added the ability to delete notations
> directly by using a minus sign prefix like "[EMAIL PROTECTED]".
>
> Given these notations:
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
> if you use "[EMAIL PROTE
On Thu, Mar 09, 2006 at 10:52:53PM +0100, Peter Palfrader wrote:
> On Thu, 09 Mar 2006, David Shaw wrote:
>
> > Let's make it simpler: I just added the ability to delete notations
> > directly by using a minus sign prefix like "[EMAIL PROTECTED]".
> >
> > Given these notations:
> > [EMAIL PROTE
in the announcement of the fix for this condition
on the gnupg announce list, it says the following:
=[ begin quoted text ]=
The only correct solution to this problem is to get rid of the
feature
to check concatenated signatures - this allows for strict checking
of
valid packet composit
On Thu, Mar 09, 2006 at 05:55:43PM -0500, [EMAIL PROTECTED] wrote:
> in the announcement of the fix for this condition
> on the gnupg announce list, it says the following:
>
> =[ begin quoted text ]=
>
> The only correct solution to this problem is to get rid of the
> feature
> to check
We are pleased to announce the availability of the second release
candidate for the forthcoming 1.4.3 version of GnuPG:
ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.4.3rc2.tar.bz2 (3.0M)
ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.4.3rc2.tar.bz2.sig
SHA-1 checksums for the above files are:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
compiled and installed over existing 1.4.3rc1, with idea.c, Darwin 8.5.0
MacOS 10.4.5 PPC.
Running fine.
Thanks to David, Timo, Werner, and a fine week end.
Charly
David Shaw wrote the following on 3/9/06 7:36 PM:
> We are pleased to anno
11 matches
Mail list logo