Re: There is no limit on the length of a passphrase,

2008-10-20 Thread Faramir
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Shaw escribió: > On Oct 20, 2008, at 10:15 PM, Morton D. Trace wrote: ... >> GnuPG needs a pass phrase to protect the primary and >> subordinate private keys that you keep in your possession. ... >> What to do if the pass phrase needs to be stro

Re: There is no limit on the length of a passphrase,

2008-10-20 Thread David Shaw
On Oct 20, 2008, at 10:15 PM, Morton D. Trace wrote: Dear List readers! http://www.gnupg.org/gph/en/manual/c14.html GnuPG needs a pass phrase to protect the primary and subordinate private keys that you keep in your possession. You need a Pass phrase to protect your private key. Enter passp

There is no limit on the length of a passphrase,

2008-10-20 Thread Morton D. Trace
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear List readers! http://www.gnupg.org/gph/en/manual/c14.html GnuPG needs a pass phrase to protect the primary and subordinate private keys that you keep in your possession. You need a Pass phrase to protect your private key. Enter passphrase: T

Re: gpg.conf in Gpg4win

2008-10-20 Thread Faramir
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Werner Koch escribió: > On Mon, 20 Oct 2008 21:00, [EMAIL PROTECTED] said: > >> I have been testing (a very little bit) Gpg4win 1.1.3, and I >> noticed changes made in gpg.conf are not working... I changed my default > Check that you are chan

Re: gpg.conf in Gpg4win

2008-10-20 Thread Werner Koch
On Mon, 20 Oct 2008 21:00, [EMAIL PROTECTED] said: > I have been testing (a very little bit) Gpg4win 1.1.3, and I > noticed changes made in gpg.conf are not working... I changed my default > preferences, but keys generated after the change still have the same > preferences (gpg defaults). I

gpg.conf in Gpg4win

2008-10-20 Thread Faramir
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello! I have been testing (a very little bit) Gpg4win 1.1.3, and I noticed changes made in gpg.conf are not working... I changed my default preferences, but keys generated after the change still have the same preferences (gpg defaults). I tri

gpgme 1.1.7 and verify signature

2008-10-20 Thread Florian Schwind
Hello List. I tried to uses the new gpgme-1.1.7 on linux with gpg-1.4.9 and I now get a gpgme "Bad file descriptor" error when I try to verify a normal signature with "gpgme_op_verify(ctx, sig, NULL, plain);" which worked fine with gpgme-1.1.4. Anyone else discovered this behavior or can help me?