gpg.conf: settings for security and compatibility

2014-11-25 Thread gnupgpack
Hello to all, my newbie post... I am struggling with gpg.conf for GnuPG-Pack-14.11.x (gpg 1.4.18). Dealing with encryption should be secure, cross-mailer interoperability and compatibility should be maximized between PGP/GnuPG/GPG/OpenPG and different os (Win/Mac/Linux). There are some known has

RE: Setpref is not working or is it a bug or something?

2014-11-25 Thread gnupgpack
Hello, beware of compatibility issues... Older versions of Debian (< sarge) don't support SHA512, AFAIK. Many Smartcards are limited to key size <= 3072 bit, AFAIK. RSA signatures are larger than DSA signatures, even if same bit size. So, what are the most useful cross-over compatibility settings

RE: Setpref is not working or is it a bug or something?

2014-11-26 Thread gnupgpack
Hello, > No. The 2.0 cards from ZeitControl all support 4096 (if you feel a need > for this). The problem was that old GnupG versions limited them to 3k. I am working with GnuPG-Pack, which includes extended gpg-1.4.18. This versions supports smartcard keys with 4096bit? >> So, what are the mo

RE: Setpref is not working or is it a bug or something?

2014-11-28 Thread gnupgpack
Hello, > -Original Message- > From: Gnupg-users [mailto:gnupg-users-boun...@gnupg.org] On Behalf Of > Robin Mathew Rajan > Sent: Thursday, November 27, 2014 8:39 AM > That's why I chose, these four extra configurations which I believe most > secure with fewer compatibility issues with newe

RE: Setpref is not working or is it a bug or something?

2014-11-30 Thread gnupgpack
>> I am sorry, all my replies are sent to gnupg-users@gnupg.org only, > Yes, that's the right procedure. > The problem Peter mentioned is caused by the fact that your replies lack > the message headers (In-reply-to and References) that usually link > replies to the replied-to messages. Yes, that

Order/changing of subkeys derogates compatibility!?

2014-11-30 Thread gnupgpack
Hello to all, while creating some new v4-RSA keypairs a compatibility issue occurs with old PGP-6.5.x: C,E should be RSA, S should be DSA (2048 with SHA256 for smaller signatures...) Sec/pub keyset is used with GPG-1.4.18 (Win7-64), pub key is exported to PGP-6.5.x only for testing purpose on an

RE: Order/changing of subkeys derogates compatibility!?

2014-12-01 Thread gnupgpack
Hello, > 6.5.8 is about sixteen years old now and has many known security > problems. Please stop using it. (Yes, intended only for testing...) > - From (possibly inaccurate) memory, PGP was up to somewhere around > version 8.x before it supported signing subkeys. First PGP version supporting W

RE: Setpref is not working or is it a bug or something?

2014-12-01 Thread gnupgpack
Hello, > I suggest that you stop deleting the In-reply-to and the References > header. Ok, i'll give it a try ;) >> X-MSMAIL-PRIORITY: > Given that you set this on a per-message basis as High/Normal/Low, > it's not a security/privacy issue at all. Deleting it just means all > your messages defa

Re: Order/changing of subkeys derogates compatibility!?

2014-12-03 Thread gnupgpack
After further investigation: Actual version of 'Symantec Encryption Desktop 10.2.3' (former known as PGP...) is supporting subkeys for signing or encryption in both directions, accurate interaction with GPG-2.0.26/GPG-1.4.18. NOT working with subkeys for signing or encryption are: PGP-6.5.1 / 6.