Re: About my prefered settings...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 David Shaw escribió: >> Also, I couldn't locate the list of equivalences between names and >> codes, like AES256 - S9 in the gpg.man file... I found a list using >> google, but it is for an older version, which didn't include all the >> things avai

Re: About my prefered settings...

On Jun 24, 2008, at 12:27 AM, Faramir wrote: Thanks for the answers. I am a bit confused about if I should use names like aes256 or codes like S9. Also, do I have to include all the cipher/digest/compress algorithms available to my installed gpg, or just one or two? The idea would be "if you

About my prefered settings...

Typing gpg -v --version will give you the capabilities along with the relative numbers for your compiled version of gpg Example: $ gpg -v --version gpg (GnuPG) 1.4.10-svn4783 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: About my prefered settings...

Faramir wrote: > Thanks for the answers. I am a bit confused about if I should use > names like aes256 or codes like S9. Six of one, half dozen of another. I think it's generally for the best if people use names, since they're easier to read and harder to screw up. > Also, do I have to include

Re: About my prefered settings...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Shaw escribió: ... > Put this in your gpg.conf: > > personal-cipher-preferences aes256 > personal-digest-preferences sha256 > personal-compress-preferences zip > > GPG will then use those algorithms when possible, but will never use > them i

Re: About my prefered settings...

There are Members of this List who understand I 'break rules' and some call Me an I-D-I-O-T', I prefer the term /Bleeding Edge/ but this in NO way makes Me correct. I'd characterize it this way, actually: The source is free. You're free to do with it as you like, and most people here will ste

Re: About my prefered settings...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Faramir wrote: > Cifrado: AES256, AES192, AES, CAST5, 3DES (cipher) > Resumen: SHA1, SHA256, RIPEMD160 (hashing) > Compresin: ZLIB, BZIP2, ZIP, Sin comprimir [no compression] (compression) > Caracter¡sticas: MDC, Sevidor de claves no-modif

Re: About my prefered settings...

On Mon, Jun 23, 2008 at 05:59:44AM -0400, Faramir wrote: > Now the question is: how do I set a "default prefered ^thing to use^" > without making unavailable the other algorithms? The idea is to use the > custom setting only when the recipient can receive messages using these > settings... I think

Re: About my prefered settings...

Faramir wrote: > But now, I would like to know what cipher algorithms, hash function and > compression I am using... and of course, I don't know how to know it. Is > there a way to know, by looking at my public key (or sending some > command to gpg), what is my preferred settings? The best way is

Re: About my prefered settings...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John W. Moore III escribió: > Faramir wrote: > >> But now, I would like to know what cipher algorithms, hash function and >> compression I am using... and of course, I don't know how to know it. Is >> there a way to know, by looking at my public key (

Re: About my prefered settings...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Faramir wrote: > But now, I would like to know what cipher algorithms, hash function and > compression I am using... and of course, I don't know how to know it. Is > there a way to know, by looking at my public key (or sending some > command to gpg)

About my prefered settings...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, I have avoided messing with the preferences settings of gpg, since I don't fully understand how does it works, and I am a bit afraid of breaking something. In special, I don't want to deliver messages that can't be read by the recipient... I con