-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/19/2013 09:58 AM, Alessandro Basili wrote:
> On 19/01/2013 15:21, LeRoy wrote:
> []
>>>> Why don't you edit your key and add a user ID like:
> 
>>>> gpg --edit-key 0x7388FD80 adduid
> 
>>> I'm afraid I haven't understood what is this for and how this
>>> would solve the problem I had. I believe I have an User ID
>>> attached to my key which correspond to my email.
> 
>>>> At the same time you might want to add a couple of sub keys (1
>>>> for signing and 1 for encrypting) that have a preset expiration
>>>> date.
> 
>>> I believe that if you import my public key you should be able to
>>> see a primary key (keyID 0x7388FD80) and a sub-key (keyID
>>> 0x1622208F) which is used for encryption.
> 
>> [email protected] is not one of the user ID's Your key looks like: gpg2
>> --fingerprint 0x7388FD80 pub   2048R/7388FD80 2013-01-18 Key
>> fingerprint = 36CE 2A86 53F5 AC4F 2CAD  925E 1A2A CAC4 7388 FD80 
>> uid                  Alessandro Basili
>> <[email protected]> sub   2048R/1622208F 2013-01-18
> 
>> With adding an additional UID of [email protected] you could alleviate
>> the trouble you have had.
> 
> 
> I now understand your point, even though I believe you missed mine. I
> used [email protected] as a recipient for testing purposes only and not as
> an a.k.a. of the same key pair.

Personally I use GnuPG not only for email but for also encrypting files
like my password file that contains about 100 different passwords.  I
use a random password generator pwgen for each new account.  I use emacs
to edit the file which I keep in my home directory as a hidden file.

gpg2 -aesr [email protected] .passwd

will ascii encrypt filename with my own public key.  If my laptop ever
gets stolen not only is /home encrypted but several files within it are
encrypted with my 4096 bit key.

When you encrypt a file you need to first make sure that you can open
the file and read it.

gpg2 -d .passwd.asc | less

You need a passphrase to unlock the secret key for
user: "LeRoy D. Cressy (15 Nov 2011) <[email protected]>"
4096-bit RSA key, ID E9147D70, created 2012-11-20 (main key ID C34B77CC)

After you have tested that you can open the encrypted file it is safe to
remove the original unencrypted file.  I like using shred for this so
that the file is overwritten numerous times.

shred -uvzn 20 .passwd

Just using rm or del will not over write the file and erase it cleanly
from the disk.



> 
> I indeed thought in the beginning that for a key pair there was only
> one email account bound to it, but I guess this was a very silly
> assumption. I now have two key pairs for two different email accounts.
> Any suggestion on how to 'merge' them? Should I simply revoke one and
> use the other adding an user ID to it?

That choice is up to you.  Personally, if you have different passphrases
for each key as a security precaution  then it is wise to keep the two
keys.  On the other hand if you are using the same passphrase for both
keys then I would revoke one and add a UID to the other.

One of the nice things is that you can revoke UID's and sub keys as
needed while keeping the original public key for years.

- -- 
 Rev. LeRoy D. Cressy  mailto:[email protected]   /\_/\
                       http://lrcressy.com        ( o.o )
                                                   > ^ <
                       Cell Phone:  267-307-3527

Open PGP Key:     C34B77CC
gpg fingerprint:  8AD5 35EF 1FDF F1A7 E483  8CCE A50D 4E81 C34B 77CC

For info on enigmail:    http://enigmail.mozdev.org/
For info on gpg:         http://www.gnupg.org/

Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me. (John 14:6)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQ+tE9AAoJEI9ujBCAoueIAoEP/2YMkgtMAXPzAjyPSeUPZNbu
b89XtH0pMDdlEApThIfmk8zgeJvJdE66B5HCwbEOPNJBdSjYXLW92/H57Uw1ytJ5
WTszBxr31yFiwZK47kkkM2ZGRejSz2Ut38OZt3MUTk1NSZNFtpyxpsdrtRTCGS22
5CEMXsLtqzg1ZsJRkHKnzjnoroqtZyO9m3ajRDRZsOvKvWZ1GAZ0/7n8YKmwbijf
AbW6g6/Nknv0ClLgp3dI3yZD5cuWPzcCV14/mxR89/za9iyIjmWaZG9uac4hIte5
Pe+c4XaK5+S+fePNaiVh5nU7/N/KmULt6BDAh3CjhA099XswveJUDDoVjtk01FDS
aNOkSh9kvBss7ZslyWmBCEJnPPzdBa1itQWnYpo6ZgTB3T2nGxE5bmRXXBhImMYb
t1aPN7qydLm1a2z6Rd+t9WvoaspwRSPv2FAlaj1W6mFWWqYcmbX9/Rl43woPKP1y
3g4C2bPxRnISV/hjh0wgtsCgZMt4peyFdaOQF0AS/GJbi7eS7R/QCtZUK6ut21ru
M9EkcsbpAShpSh/+yuTs+nHTa+O/B80OEgqKwFbZdX2EEs5/Y+ymTemNchKXIUhx
3r8b9o1z7/ZFvg031TvTVqwpum6xahaLqUk/GpJrCVG92HyxNm9v93EX5sm0klVH
By0zz4Kfg1DZQRV4GPcy
=1VaG
-----END PGP SIGNATURE-----

_______________________________________________
enigmail-users mailing list
[email protected]
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to