Werner Koch wrote:
> On Thu, 16 Nov 2006 02:37, [EMAIL PROTECTED] said:
>
>> I'm using 2.0.0 on FreeBSD 7-Current, and although I have
>> "no-secmem-warning" in my gpg.conf, I'm still getting "Warning: using
>> insecure memory!" with just about every gpg command I run. Any ideas?
>
> What version
On Thu, 16 Nov 2006 01:15, [EMAIL PROTECTED] said:
> Nope, still the same error:
> gpgsm: error creating signature: No value
It would be helpfukl to see the actual output. If you don't want that
to appear on a public list, send it me by private mail.
> Shall I try to dig into gpgsm_validate_ch
On Thu, 16 Nov 2006 02:37, [EMAIL PROTECTED] said:
> I'm using 2.0.0 on FreeBSD 7-Current, and although I have
> "no-secmem-warning" in my gpg.conf, I'm still getting "Warning: using
> insecure memory!" with just about every gpg command I run. Any ideas?
What version of libgcrypt are you using?
Hi Doug,
I haven't gotten 2.0 to compile on FreeBSD (yet), but with 1.x I have to run
chmod 4775 on the absolute location of the gpg binary. Then it goes away.
HTH,
Eric Buchanan
On Wednesday 15 November 2006 17:37, Doug Barton wrote:
> Howdy,
>
> I'm using 2.0.0 on FreeBSD 7-Current, and alt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Howdy,
I'm using 2.0.0 on FreeBSD 7-Current, and although I have
"no-secmem-warning" in my gpg.conf, I'm still getting "Warning: using
insecure memory!" with just about every gpg command I run. Any ideas?
Doug
- --
If you're never wrong, yo
On Wednesday 15 November 2006 08:23, Werner Koch wrote:
> On Wed, 15 Nov 2006 02:02, [EMAIL PROTECTED] said:
> > But now, with the code compiling, I could track down to where the problem
> > is. The method gpgsm_validate_chain (ctrl, cert, NULL, 0, NULL, 0); on
> > sm/sign.c is failling. Any hints
Now these are promising -
http://www.weethet.nl/english/smartcards_types.php#funcard
Need to crash into bed... I'll look at them in more detail later...
Ben
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnu
Benjamin Donnachie wrote:
> Ah-ha! Amtel are apparently offering samples of their
> AT91SC512384RCT[1], which has an impressive set of features including a
> cryptographic accelerator...
Alternatively, this link raises some interesting possibilities -
http://www.elecdesign.com/Articles/Index.cfm?
Benjamin Donnachie wrote:
> Can you point me in their direction please? I'd much rather try to
> implement RSA from scratch in Java than Basic!
Ah-ha! Amtel are apparently offering samples of their
AT91SC512384RCT[1], which has an impressive set of features including a
cryptographic accelerator.
Wei Wu [H] wrote:
> Yes. That's what I need.
If you're just trying to eliminate pass phrases and set up a key file
only scenario, why not simply create a key pair with a null or "zero
length" pass phrase? Keep those keys on your removable device, and use a
script/batch that calls GnuPG with the a
Original Message
Subject: [Enigmail] IDEA
Date: Wed, 15 Nov 2006 17:18:44 +0100
From: Kristian Fiskerstrand <[EMAIL PROTECTED]>
Reply-To: Enigmail user discussion list
Organisation: The Mozdev Foundation - news server
To: enigmail@mozdev.org
Newsgroups: public.mozdev.enigmail
G
On Wed, 15 Nov 2006 13:50, [EMAIL PROTECTED] said:
> /usr/lib/libpthread.so
> /usr/lib/libpthread_nonshared.a
> /usr/lib/libpthread.a
> /lib/libpthread-0.10.so
> /lib/libpthread.so.0
PTH is is usually in a library named libpth.so. Debian started to
distribute the libpthread emulation which comes
On Wed, 15 Nov 2006 12:13, [EMAIL PROTECTED] said:
> Do you mean that if I did get some VC funding for design of open
> crypto smartcard targeted for OpenPGP use and then published it (as a
> part of the business plan) I would get sued?
Only if that card may be used to create clones of TV cards.
* Henry Bremridge <[EMAIL PROTECTED]> [2006-10-29 18:25:17 +]:
> Question:
>
> - The FSFE website states that the recommended procedure is to use the
> smart card with sub-keys only. If however I am creating a new
> key-pair and backing up the secret key to a safe place, then what i
Yes. That's what I need.
Thanks,
WW
-Original Message-
From: Sven Radde [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 15, 2006 12:46 AM
To: Wei Wu [H]
Cc: gnupg-users@gnupg.org
Subject: Re: how to create a symmetric cipher
Hello!
Wei Wu [H] schrieb:
> The data to be protected res
On Tue, Nov 14, 2006 at 05:49:00PM +0100, Werner Koch wrote:
> On Tue, 14 Nov 2006 13:06, [EMAIL PROTECTED] said:
>
> > Is it very hard to design such a card from scratch, and very expensive
> > to have it produced as custom hardware? I'm sure there are enough
> > chip-producing companies in China
Werner Koch wrote:
>Good for people in China, but here they will go after you as soon as
>you sell them. Recall that we are not yet ready to FTP hardware.
Mail-order from a company in Tadjikistan, who gets them from a front-end
company in Hong Kong who orders them somewhere in mainland China. Go
Hello,
GnuPG 2 doesn't make it easier... I installed all 4 libs, but
configure in gpg2 gave me:
configure:
***
*** You need libassuan with Pth support to build this program.
*** This library is for example available at
*** ftp://ftp.gnupg.org/gcrypt/libassuan/
*** (at least version 0.9.3 (API 1
Hello Wei !
"Wei Wu [H]" <[EMAIL PROTECTED]> wrote:
> I want to create a symmetric cipher such as AES to encrypt some data, and
> think gpg (GnuPG Version 1.4.2.1) may do this. But I found it gives only
> three options, none is symmetric. I would appreciate if anyone can point me
> to another or
Hi,
While you are at it, you might want to add support for the keybox
foramt which is currently used for X.509 but will soon also store
OpenPGP keys:
The KeyBox uses an augmented OpenPGP/X.509 key format. This makes
random access to a keyblock/Certificate easier and also gives the
opportun
On Wed, 15 Nov 2006 02:02, [EMAIL PROTECTED] said:
> But now, with the code compiling, I could track down to where the problem is.
> The method gpgsm_validate_chain (ctrl, cert, NULL, 0, NULL, 0); on sm/sign.c
> is failling. Any hints on what I can do to know why it is failling?
Run
gpgsm --d
21 matches
Mail list logo
