Re: Where is ECC in gpg2 (specifically gnupg-2.0.21

2013-09-20 Thread Werner Koch
On Thu, 19 Sep 2013 20:59, jo...@netpage.dk said: > Yes, but it isn't only HIS stuff! You have to trust the recipient anyway that he keep the information confidential. It does not help to use string encryption if the message is later re-tweeted by the recipient. Unfortunately this is too often

Can't adduid (can't read pubring.gpg?)

2013-09-20 Thread Christopher W. Richardson
Hi folks, First off, I'm new to the list, so if I violate any etiquette, feel free to educate me. Second, a couple of quick questions before I get to the heart of the matter: 1) is there any general place to go look for help with debugging issues other than Chapter 10 of the manual? 2) is the

Re: Where is ECC in gpg2 (specifically gnupg-2.0.21

2013-09-20 Thread Mark H. Wood
On Fri, Sep 20, 2013 at 01:44:32PM +0200, Werner Koch wrote: > On Thu, 19 Sep 2013 20:59, jo...@netpage.dk said: > > Yes, but it isn't only HIS stuff! > You have to trust the recipient anyway that he keep the information > confidential. It does not help to use string encryption if the message > is

Re: Can't adduid (can't read pubring.gpg?)

2013-09-20 Thread C. Rossberg
On Fri, 20 Sep 2013, Christopher W. Richardson wrote: > 2) is there a way to search the mail archives? > (http://www.gnupg.org/documentation/mailing-lists.en.html say to go > tohttp://marc.theaimsgroup.com/, but the latter is down, at least ATM — not > sure if that's temporary or permanent (and

Re: Can't adduid (can't read pubring.gpg?)

2013-09-20 Thread Christopher W. Richardson
On 20 Sep 2013, at 21:50, "C. Rossberg" wrote: > On Fri, 20 Sep 2013, Christopher W. Richardson wrote: > >> 2) is there a way to search the mail archives? >> (http://www.gnupg.org/documentation/mailing-lists.en.html say to go >> tohttp://marc.theaimsgroup.com/, but the latter is down, at leas

Re: Can't adduid (can't read pubring.gpg?)

2013-09-20 Thread Christopher W. Richardson
On 21 Sep 2013, at 10:58, Christopher W. Richardson wrote: > > gpg(5521) malloc: *** error for object 0x7: pointer being freed was not > allocated > *** set a breakpoint in malloc_error_break to debug > > I guess there are some corrupted public key(s)? Like I said, my problem is > effect