On Mar 14, 2010, at 10:17 AM, MFPA wrote:
>> On Mar 14, 2010, at 8:26 AM, MFPA wrote:
>>> Would "--disable-cipher-algo AES" add anything to
>>> that? Or cause potential problems?
>
>> Potential problems. If you have AES in your key
>> preferences, but you disable it, you are telling people
>> to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Sunday 14 March 2010 at 1:19:46 PM, in
, David Shaw
wrote:
> On Mar 14, 2010, at 8:26 AM, MFPA wrote:
>> Would "--disable-cipher-algo AES" add anything to
>> that? Or cause potential problems?
> Potential problems. If you have AES in your
On Mar 14, 2010, at 8:26 AM, MFPA wrote:
>>> It was just curiosity. By the way, is it possible to disable some
>>> other encryption algo, but without forcing GnuPG to use a chosen algo? I
>>> mean... lets suppose I don't want to use AES, but I'm ok with twofish,
>>> 3DES, and Camellia (any of there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi David
On Sunday 14 March 2010 at 2:49:34 AM, you wrote:
> On Mar 13, 2010, at 8:03 PM, Faramir wrote:
>> It was just curiosity. By the way, is it possible to disable some
>> other encryption algo, but without forcing GnuPG to use a chosen al
On Mar 13, 2010, at 8:03 PM, Faramir wrote:
> It was just curiosity. By the way, is it possible to disable some
> other encryption algo, but without forcing GnuPG to use a chosen algo? I
> mean... lets suppose I don't want to use AES, but I'm ok with twofish,
> 3DES, and Camellia (any of there wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John Clizbe escribió:
> Faramir wrote:
>> Just a question, and I don't have any intention about doing it, but,
>> is there a way to disable the usage of 3DES in GnuPG, when encrypting?
>
> Sure, the source is available -- the result just won't be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi David
On Saturday 13 March 2010 at 12:58:40 PM, you wrote:
> It won't work anyway. You can't remove 3DES from the cipher
> preferences with disable-cipher-algo.
[...]
> To make matters worse, not only does it not work in
> preventing 3DES bein
Thanks David for helping to clarify.
-Original Message-
From: David Shaw [mailto:ds...@jabberwocky.com]
Sent: Friday, March 12, 2010 5:15 PM
To: Robert Palmer
Cc: gnupg-users@gnupg.org
Subject: Re: updprefs command and changing key
On Mar 10, 2010, at 4:07 PM, Robert Palmer wrote
On Mar 13, 2010, at 5:14 AM, MFPA wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi
>
>
> On Saturday 13 March 2010 at 12:07:08 AM, in
> , David Shaw
> wrote:
>
>
>> On Mar 12, 2010, at 6:31 PM, Faramir wrote:
>
>>> is there a way to disable the usage of 3DES in GnuPG, when
>
On Mar 13, 2010, at 5:55 AM, John Clizbe wrote:
> MFPA wrote:
>> On Saturday 13 March 2010 at 12:07:08 AM, in
>> , David Shaw
>> wrote:
>>> On Mar 12, 2010, at 6:31 PM, Faramir wrote:
is there a way to disable the usage of 3DES in GnuPG, when
encrypting?
>>> Patch the source :)
>>> There
ES] won't do it? Faramir was asking
> only about disabling it when encrypting: I was under the impression
> --cipher-algo could be used to do that.
We were discussing this in the context of the cipher preferences system
(Subject "updprefs command and changing key"). You c
MFPA wrote:
> On Saturday 13 March 2010 at 12:07:08 AM, in
> , David Shaw
> wrote:
>> On Mar 12, 2010, at 6:31 PM, Faramir wrote:
>>> is there a way to disable the usage of 3DES in GnuPG, when
>>> encrypting?
>> Patch the source :)
>> There is no way other than that.
>
> Wouldn't "--disable-cipher
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Saturday 13 March 2010 at 12:07:08 AM, in
, David Shaw
wrote:
> On Mar 12, 2010, at 6:31 PM, Faramir wrote:
>> is there a way to disable the usage of 3DES in GnuPG, when
>> encrypting?
> Patch the source :)
> There is no way other than t
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello David !
David Shaw wrote:
>> Just a question, and I don't have any intention about doing it, but,
>> is there a way to disable the usage of 3DES in GnuPG, when encrypting?
> Patch the source :)
> There is no way other than that. 3DES
> There is no way other than that. 3DES is a required part of OpenPGP, so if
> you remove it, you're not going to play well with the other programs out
> there.
--cipher-algo [something other than 3DES] won't do it? Faramir was asking only
about disabling it when encrypting: I was under the i
> Just a question, and I don't have any intention about doing it, but,
> is there a way to disable the usage of 3DES in GnuPG, when encrypting?
Kind of, but it's not recommended.
"--cipher-algo AES" will do it, but please don't. This kind of brute force
approach is almost always the wrong thin
Faramir wrote:
> Just a question, and I don't have any intention about doing it, but,
> is there a way to disable the usage of 3DES in GnuPG, when encrypting?
Sure, the source is available -- the result just won't be a valid OpenPGP
implementation any longer.
Now for my "Just a Question": Why o
On 3/12/2010 6:31 PM, Faramir wrote:
>
> Just a question, and I don't have any intention about doing it, but,
> is there a way to disable the usage of 3DES in GnuPG, when encrypting?
>
> Best Regards
Doing that wouldn't comply with the spec. The spec says that
implementations MUST support 3
On Mar 12, 2010, at 6:31 PM, Faramir wrote:
> David Shaw escribió:
> ...
>> However, your 3rd party should not have rejected the key. The OpenPGP
>> preferences system is designed to *always* reach a valid answer. Every
>> preference list contains Triple-DES, whether you explicitly list it ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Shaw escribió:
...
> However, your 3rd party should not have rejected the key. The OpenPGP
> preferences system is designed to *always* reach a valid answer. Every
> preference list contains Triple-DES, whether you explicitly list it there
On Mar 10, 2010, at 4:07 PM, Robert Palmer wrote:
> During exchange of a public key to a 3rd party – they rejected the key for
> not having a compatible cipher; so, after doing some research the key was
> edited within gpg to update prefs on the key which now shows a compatible
> cipher (in thi
On 3/10/2010 4:07 PM, Robert Palmer wrote:
> During exchange of a public key to a 3^rd party – they rejected the key
> for not having a compatible cipher; so, after doing some research the
> key was edited within gpg to update prefs on the key which now shows a
> compatible cipher (in this case, A
During exchange of a public key to a 3rd party - they rejected the key for
not having a compatible cipher; so, after doing some research the key was
edited within gpg to update prefs on the key which now shows a compatible
cipher (in this case, AES-256). I re-exported the public key and noticed
th
23 matches
Mail list logo
