On 6/21/2012 12:39 PM, Daniel Kahn Gillmor wrote:
> i don't think this is the case.
You and David are completely right, and I have no idea what I was
thinking. Thank you both for the correction!
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http:/
On Jun 21, 2012, at 12:39 PM, Daniel Kahn Gillmor wrote:
> On 06/21/2012 12:52 AM, Robert J. Hansen wrote:
>> Please don't do this. It's error-prone. Those are machine-readable
>> numbers, not human-readable ones. Use the human-readable ones: for
>> instance,
>>
>> default-preference-list TWOF
On 06/21/2012 12:52 AM, Robert J. Hansen wrote:
> Please don't do this. It's error-prone. Those are machine-readable
> numbers, not human-readable ones. Use the human-readable ones: for
> instance,
>
> default-preference-list TWOFISH 3DES SHA256 SHA224 RIPEMD160
completely agreed.
> Also, def
On 21-06-2012 7:47, Robert J. Hansen wrote:
> No, because this is the sort of thing that usually goes in a gpg.conf
> file. I can't think of a use case for default-preference-list on the
> command line -- not saying none exist, mind you, but only that I can't
> think of one.
I have met one in pr
On 06/21/2012 01:36 AM, Laurent Jumet wrote:
> Don't you think that the command line could be too long, using the
> algorithms names instead of their tags?
No, because this is the sort of thing that usually goes in a gpg.conf
file. I can't think of a use case for default-preference-list on the
co
Hello Robert !
"Robert J. Hansen" wrote:
> On 06/21/2012 12:03 AM, Laurent Jumet wrote:
>> default-preference-list S7 S11 S12 S13...
>> personal-cipher-preferences S7 S11 S12...
>> personal-digest-preferences H3 H8 H9 H10...
>> personal-compress-preferences Z1 Z2 Z3 Z0
> Please don't do this.
On 06/21/2012 12:03 AM, Laurent Jumet wrote:
> default-preference-list S7 S11 S12 S13...
> personal-cipher-preferences S7 S11 S12...
> personal-digest-preferences H3 H8 H9 H10...
> personal-compress-preferences Z1 Z2 Z3 Z0
Please don't do this. It's error-prone. Those are machine-readable
number
Hello John !
"John" wrote:
> When someone uses my public key to encrypt a message to me, what prevents
> them from trying to use an encryption algorithm of his choice. In other
> words, does the public key itself limit the options available to the person
> sending the message? Thanks.
Firs
On Jun 20, 2012, at 1:18 PM, Robert J. Hansen wrote:
> On 6/20/12 1:10 PM, John wrote:
>> When someone uses my public key to encrypt a message to me, what
>> prevents them from trying to use an encryption algorithm of his choice.
>
> Nothing. They can use --cipher-algo to force whatever symmetri
On 6/20/12 1:10 PM, John wrote:
When someone uses my public key to encrypt a message to me, what
prevents them from trying to use an encryption algorithm of his choice.
Nothing. They can use --cipher-algo to force whatever symmetric
algorithm they wish. This may wind up with a message that y
On Jun 20, 2012, at 1:10 PM, John wrote:
> Hello.
>
> When someone uses my public key to encrypt a message to me, what prevents
> them from trying to use an encryption algorithm of his choice. In other
> words, does the public key itself limit the options available to the person
> sending the
Hello.
When someone uses my public key to encrypt a message to me, what prevents
them from trying to use an encryption algorithm of his choice. In other
words, does the public key itself limit the options available to the person
sending the message? Thanks.
John
__
12 matches
Mail list logo
