David Shaw dshaw at jabberwocky.com
Fri Mar 2 13:58:08 CET 2007 wrote:
>Only the old PGP 2.x (V3) RSA keys cannot carry subkeys.
and all v3 rsa keys are both sign and encrypt,
but, if anyone prefers not to have subkeys,
gnupg allows v4 rsa keys to be generate as a single key
with both sign an
Hello Timo !
Timo Schulz <[EMAIL PROTECTED]> wrote:
>>> Thanx, I missed that. So this is one of the "sign only"
>>> keys and to enable encryption, one would add an encryption
>>> only subkey?
>>
>> Not on that one, it's a RSA key.
> But if I see it correctly, it's _no_ v3 key so you can
> a
On Fri, Mar 02, 2007 at 11:05:48AM +0100, Laurent Jumet wrote:
>
> Hello Olaf !
>
> Olaf Gellert <[EMAIL PROTECTED]> wrote:
>
> >> pub 2048R/CC21E10F created: 2006-11-21 expires: never usage: SC
> >>
> >> This is the information given in --edit-key. And the usage
> >> is the solution fo
Laurent Jumet wrote:
>> Thanx, I missed that. So this is one of the "sign only"
>> keys and to enable encryption, one would add an encryption
>> only subkey?
>
> Not on that one, it's a RSA key.
But if I see it correctly, it's _no_ v3 key so you can
add a subkey to this key even if it is RSA
Hello Olaf !
Olaf Gellert <[EMAIL PROTECTED]> wrote:
>> pub 2048R/CC21E10F created: 2006-11-21 expires: never usage: SC
>>
>> This is the information given in --edit-key. And the usage
>> is the solution for your problem.
>> It has *no* capability to encrypt data.
> Thanx, I missed tha
Olaf Gellert wrote:
> keys and to enable encryption, one would add an encryption
> only subkey?
IIRC, it is not possible to change the capabilities of an
existing key with GPG. Somebody might correct me if I'm wrong.
And yes, the only way to encrypt to this key is to add an
encryption subkey to
Timo Schulz wrote:
> pub 2048R/CC21E10F created: 2006-11-21 expires: never usage: SC
>
> This is the information given in --edit-key. And the usage
> is the solution for your problem.
> It has *no* capability to encrypt data.
Thanx, I missed that. So this is one of the "sign only"
keys
Olaf Gellert wrote:
> 0xCC21E10F. The key is self-signed, gpg --check-sigs
> does not complain, but still when I try to encrypt
> I get:
>
> gpg: 0xCC21E10F: skipped: unusable public key
pub 2048R/CC21E10F created: 2006-11-21 expires: never usage: SC
This is the information given in --
Hi all,
I keep getting an error trying to encrypt to the key
0xCC21E10F. The key is self-signed, gpg --check-sigs
does not complain, but still when I try to encrypt
I get:
gpg: 0xCC21E10F: skipped: unusable public key
I am using gpg 1.4.5 on a Linux box (SuSE 10.2).
Could this be a matter of alg
