-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
-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?
The public key is never protected by the passphrase ( *as far as I
know* I may be wrong), so anyway it s
How can I remove this restriction where I don't have to provide passphrase and
public key itself is good enough?
Thanks
naeem
>-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
>S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Well, as far as I know, it adds support for s/MIME... and if I am not
wrong, that would mean certificates like the ones issued by CAcert,
Comodo, et all... But, is GnuPG capable of generating those
certificates? Or we will still require OpenSSL or eq
-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
