-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Afzal, Naeem M escribió:
> How can I remove this restriction where I don't have to provide passphrase
> and public key itself is good enough?
>
> Thanks
> naeem
I forgot a very important thing: after changing you passphrase,
probably you will ha
need to revoke it and make a new one...
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>> On Behalf Of Faramir
>> Sent: Saturday, June 28, 2008 11:08 AM
>> To: gnupg-users@gnupg.org
>> Subject: Re: why we need passphrase
>>
&
nupg-users@gnupg.org
>Subject: Re: why we need passphrase
>
> Because the key itself is protected by a passphrase. You CAN remove
>that protection, and you can even generate keys without passphrase.. but
>the idea is, if you have to go to the bathroom, and someone else tries
>to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Afzal, Naeem M escribió:
> Hi,
>
> In order to understand GnuPG, I tried to create private keys on two ubuntu
> systems. Here are my steps and I would ask my question at the end as I need
> to show what I did.
>
> 1. System A: Created private and
Hi,
In order to understand GnuPG, I tried to create private keys on two ubuntu
systems. Here are my steps and I would ask my question at the end as I need to
show what I did.
1. System A: Created private and public key by using 'gpg --gen-key' and then
'gpg --export --armor -out userA.a
