-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
but there's one difference. keys with and without "comment" are treated
as different keys, so that you have to accept the "new" key.
sort of strange ...
Do I understand you correctly that it would be good to ignore comments
when replacing keys (I mean,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thank you for the investigation, Vagrant and Wolfgang!
On 11-01-2005 08:47, Wolfgang Schweer wrote:
> but there's one difference. keys with and without "comment" are treated
> as different keys, so that you have to accept the "new" key.
> sort of st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
still, the last part of each public key (i'm not sure if it is required
or optional) is usually the user and host machine the key was generated
on... but everything after the @ sign disappears with this patch.
i think it's optional.
appears so.
hopefull
> >still, the last part of each public key (i'm not sure if it is required
> >or optional) is usually the user and host machine the key was generated
> >on... but everything after the @ sign disappears with this patch.
>
> i think it's optional.
appears so.
> >hopefully it's still a valid known_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
still, the last part of each public key (i'm not sure if it is required
or optional) is usually the user and host machine the key was generated
on... but everything after the @ sign disappears with this patch.
i think it's optional.
hopefully it's still
Package: lessdisks
Version: 0.5.3cvs.20040906-10
Followup-For: Bug #289759
well, i don't even know perl, but i think i figured this out.
strangely enough, the format of a public dsa key starts with "ssh-dss",
not "ssh-dsa".
patch attached, for better or worse.
still, the last part of each publi
6 matches
Mail list logo
