Re: [Enigmail] My key can not be imported by others since v1.9.x

2016-05-14 Thread Hauke Westemeier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, > Yes, 8192 is non standard if one considers gnupg (where enigmail is build on top), 4096 is non standard but supported; but 8192 is not supported. That's a difference. If you really think you need that high security, I would recommend to use

Re: [Enigmail] My key can not be imported by others since v1.9.x

2016-05-13 Thread Robert J. Hansen
> Yes, 8192 is non standard but what you link to is not correct for real > world front end applications The FAQ entry is correct. > but 4096 is not too big to be default, if > it is why do lots modern interface default to larger than 2048? Because there are a lot of people who demand

Re: [Enigmail] My key can not be imported by others since v1.9.x

2016-05-13 Thread diggler
On 2016-05-12 19:31, Hauke Westemeier wrote: My master key is 8192 RSA to my knowledge GnuPG only supports up to 4096-bit keys. See here https://www.gnupg.org/faq/gnupg-faq.html#default_rsa2048 for my source and some explanation why already a 4096 bit key is to large to be made the default.

Re: [Enigmail] My key can not be imported by others since v1.9.x

2016-05-12 Thread Robert J. Hansen
> to my knowledge GnuPG only supports up to 4096-bit keys. This is correct. To use larger keys requires patching GnuPG. And once you run a custom-patched version of GnuPG, we really can't help you very much. Once you play with GnuPG internals, all bets are off.