On 7/12/2012 1:03 PM, Laurent Jumet wrote:
> Choose your preferences using this:
This is not recommended.
The codes are meant for machine use. They're easy to parse and machines
never get confused between "H1" and "H2".
The names are meant for human use. They're easy to read, easy to
under
Hello Sam !
Sam Smith wrote:
> When I use "personal-digest-preferences", should I be inputting a list? Or
> is a single entry all that's necessary?
Choose your preferences using this:
??
? Cipher-Algos:? Digest-Algos:? Compre
On 07/12/2012 08:16 AM, Werner Koch wrote:
> On Wed, 11 Jul 2012 22:55, nicholas.c...@gmail.com said:
>
>> But one thing that might be helpful to explain is this: what needs to
>> be in the V5 key format aside from the change in fingerprint hash?
>> Aside from that issue, the V4 key format seems t
On 7/12/2012 11:52 AM, Robert J. Hansen wrote:
> GnuPG would likewise be forbidden from using RIPEMD160, but would be
> more likely to use SHA-1 than SHA256.
Reverse those two, please. Clearly I need to go drink coffee directly
from the pot -- I'm making far too many errors today.
__
On 7/12/2012 12:39 PM, Hauke Laging wrote:
> "Appear"? Is that what the documentation says? Do you prefer telling
> us your guesses over reading the neccessary information?
> Do you read what we tell you? How does this question fit to my
> statement (which you even quote)?
> Stop trying to unders
Am Do 12.07.2012, 12:11:11 schrieb Sam Smith:
> The "setpref" and "showpref" commands appear to only relate to what is
> stipulated with the "default-preference-list".
"Appear"? Is that what the documentation says? Do you prefer telling us your
guesses over reading the neccessary information?
>
On 7/12/2012 12:11 PM, Sam Smith wrote:
> I mean how are "personal-digest-preferences" even seen by others if
> SETPREF does not embed them in the key?
The preferences on the key are, as I mentioned, really a capability set,
but other GnuPG implementations will treat it as the algorithms you
prefe
(Many people on this list have passionate feelings about HTML email. I
understand these feelings and sympathize, but sometimes HTML is very
useful for drawing particular attention to text.)
> Thx for this explanation.
You're quite welcome.
> Is the "personal-digest-preferences" shown in the pu
On Wed, 11 Jul 2012 22:55, nicholas.c...@gmail.com said:
> But one thing that might be helpful to explain is this: what needs to
> be in the V5 key format aside from the change in fingerprint hash?
> Aside from that issue, the V4 key format seems to have been resilient.
> What are the other issue
The "setpref" and "showpref" commands appear to only relate to what is
stipulated with the "default-preference-list".
Setpref just resorts back to the "default" settings if
"default-preference-list" is not given. So if one sets
"default-preference-list" it's not necessary to set
"personal-dig
Thx for this explanation.
Is the "personal-digest-preferences" shown in the public key? Is this
preference list something others can see (how do I make it appear in the public
key)? If it is not displayed in the public key, I don't understand what good it
is or how/where it would get used.
Am Do 12.07.2012, 11:39:44 schrieb Sam Smith:
> It's overriding the recipient key preferences.
And sets the value for non-encrypted signatures.
> So "default-preference-list" is embedded into the public key
Into new keys. Existing keys need --edit-key 0x... setpref...
> to tell others
> your
On 7/12/2012 11:39 AM, Sam Smith wrote:
> Say I want to tell everyone, "Hey, I prefer you use SHA256 when
> communicating with me." What command should I use to communicate
> this? "default-preference-list" right?
There's a difference between what you can enforce and what you might be
able to sug
It's overriding the recipient key preferences.
So "default-preference-list" is embedded into the public key to tell others
your preferences. But if I set a string for "personal-digest-preferences" then
this string will override the "default-preference-list" that the other user set
in his publ
Am Do 12.07.2012, 11:27:03 schrieb Sam Smith:
> When I use "personal-digest-preferences", should I be inputting a list? Or
> is a single entry all that's necessary?
Why don't you simply have a look at the documentation?
--personal-digest-preferences string
Set the list of personal digest preferen
When I use "personal-digest-preferences", should I be inputting a list? Or is a
single entry all that's necessary?
> To: smick...@hotmail.com
> From: laurent.ju...@skynet.be
> Subject: RE: cert-digest-algo clarification
> Date: Thu, 12 Jul 2012 17:08:46 +0200
>
>
> Hello Sam !
>
> Sam Smith
What is the difference between "personal-digest-preferences" AND
"default-preference-list"
My understanding is that "default-preference-list" will define what is used for
new key generation.
Based on what I recently read in this mailing list, "default-preference-list"
also defines the "showpr
On Jul 12, 2012, at 8:41 AM, Sam Smith wrote:
> regarding #1: you said there are no preferences. Assuming I don't set
> cert-digest-algo, what is the HASH that is used to sign keys with?
cert-digest-algo has no preferences (no ranked lists, etc). - it defaults to
SHA-1, but you can override it
regarding #1: you said there are no preferences. Assuming I don't set
cert-digest-algo, what is the HASH that is used to sign keys with?
> Subject: Re: cert-digest-algo clarification
> From: ds...@jabberwocky.com
> Date: Wed, 11 Jul 2012 13:28:12 -0400
> CC: gnupg-users@gnupg.org
> To: smick..
Am Mi 11.07.2012, 22:10:11 schrieb Daniel Kahn Gillmor:
> If the attacker can convince you to sign a chosen text (perhaps one that
> looks reasonable), then a failure in the digest's collision-resistance
> could very well be used to replay that signature over a different (but
> colliding) text (wh
20 matches
Mail list logo
