Now we just need to remove your toe. :)
On Apr 17, 2007, at 3:04 PM, Thomas Sowa wrote:
Hi,
i just created a new key, the revocation and tatood the passphrase
on my left
toe :-=
Thanks for help, i figured that the situation looks bad, but hoped
thare could
be done something. If it were,
Hi,
i just created a new key, the revocation and tatood the passphrase on my left
toe :-=
Thanks for help, i figured that the situation looks bad, but hoped thare could
be done something. If it were, however, it would go at cost of security, so
it's all good.
Take care and watch out for your pas
* Thomas Sowa <[EMAIL PROTECTED]> wrote:
> - i definitely can't find the passphrase
Have a look at http://vanheusden.com/nasty/
HTH
--
left blank, right bald
pgpvNLbhhsNSQ.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnup
On Tue, Apr 17, 2007 at 11:59:01PM -0500, Robert J. Hansen wrote:
> > I have read what everybody has said on the subject and one
> > thing needs to be said again. THE DEFAULT EXPIRE FOR A NEW
> > KEY NEEDS TO BE FOR TWO YEARS FROM DATE OF KEY CREATION!
>
> That's making some really big assumption
> I have read what everybody has said on the subject and one
> thing needs to be said again. THE DEFAULT EXPIRE FOR A NEW
> KEY NEEDS TO BE FOR TWO YEARS FROM DATE OF KEY CREATION!
That's making some really big assumptions about the security policy
of the person making the key.
There are also
Thomas Sowa <[EMAIL PROTECTED]> wrote:
I have read what everybody has said on the subject and one
thing needs to be said again. THE DEFAULT EXPIRE FOR A NEW
KEY NEEDS TO BE FOR TWO YEARS FROM DATE OF KEY CREATION!
If they want to change it after they have used them for a
while and like what the
Sven Radde wrote:
> If yes, you're quite screwed as it will stay there forever: New contacts
> will not know which key to choose when they look your name up on the
> keyservers. People might be smart enough to use the newer of the two
> keys. If you don't rely so much on the keyservers to distribut
Hi!
Thomas Sowa schrieb:
> - i can't revoke it --> no passphrase :-(
> - i still need the email adresses with the useless keys
> - i definitely can't find the passphrase
Well, the severity of the problem depends on whether your "forgotten"
keys are available on the public keyservers.
If not, you
John W. Moore III wrote the following on 4/17/07 3:51 PM:
[...]
>
> If You are unable to Revoke the former Key then by all means; Generate a
> New Key (and create a standby Revoke cert) and Publish this Key *AND*
> notify every critical correspondent of the new Key! Still, those folks
> who Sear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> - i can't revoke it --> no passphrase :-(
> - i still need the email adresses with the useless keys
> - i definitely can't find the passphrase
OK, Stupid Response Question First:
Did You have the common sense to generate a Revocation Certificate
Hi,
a while ago I was experimenting with gpg and mutt, made some keys and
uploaded them. Then there was little time to play with it so I forgot
about it for a while and kept using my old mailer without the keys.
Now I just found the time again to set it all up like it should, and
realized that I
* [EMAIL PROTECTED] wrote:
> Does anyone know of a perl script or some other utility that could
> bruteforce the rest of it? I'd rather not have to revoke this key.
Have a look at http://www.vanheusden.com/nasty/
--
left blank, right bald
pgp0zxmmzKivj.pgp
Description: PGP signature
It appears I've forgotten my passphrase. I've still got the secret key, the
revocation certificate and I remember the first 5 characters of the passphrase.
I know the rest is just alphanumeric upper and lowercase. Does anyone know of
a perl script or some other utility that could bruteforce t
13 matches
Mail list logo
