Mailing List Archive: GnuPG: users

I am sure I did not forget my passphrase

Index | Next | Previous | View Threaded

marelovic at gmail

Nov 8, 2009, 7:24 AM

Post #1 of 4 (782 views)
Permalink

I am sure I did not forget my passphrase

What I know is simple. I created a key today and tried it signing one file
and it worked. Now, few hours later, I cannot do anything, and a message is
wrong passphrase. I checked mod.time of secret keyring and it looks like was
not modified in meanwhile.

I am really confused, sure not have modified my passphrase, nor forget it,
but it simply does not work anymore.

Is there a way to check if secret key info was modified?

kloecker at kde

Nov 8, 2009, 9:21 AM

Post #2 of 4 (741 views)
Permalink

Re: I am sure I did not forget my passphrase [In reply to]

On Sunday 08 November 2009, Marko Randjelovic wrote:
> What I know is simple. I created a key today and tried it signing one
> file and it worked. Now, few hours later, I cannot do anything, and a
> message is wrong passphrase. I checked mod.time of secret keyring and
> it looks like was not modified in meanwhile.
>
> I am really confused, sure not have modified my passphrase, nor
> forget it, but it simply does not work anymore.
>
> Is there a way to check if secret key info was modified?

Do you use multiple keyboard layouts? If yes, then maybe you used
another keyboard layout when you created the key.

Regards,
Ingo

Attachments:

signature.asc (0.19 KB)

marelovic at gmail

Nov 8, 2009, 10:01 AM

Post #3 of 4 (745 views)
Permalink

Re: I am sure I did not forget my passphrase [In reply to]

I made sure, both when creating keys and trying to use it, to be US keyboard
and CAPS LOCK off. After failures, I tried to turn on CAPS and change layout
with no success.

But I found errors in /var/log/messages regarding sda/hda. sda is HDD and
hda is DVD.

Nov 8 14:12:18 main kernel: [ 5.798351] sda:hda: packet command error:
tatus=0x51 { DriveReady SeekComplete Error }
Nov 8 14:44:00 main kernel: [ 6.384317] sda:hda: packet command error:
tatus=0x51 { DriveReady SeekComplete Error }

Second error is probably after the key got corrupted. Is there significant
probability the key got corrupted since it is only one error?

2009/11/8 Ingo Klöcker <kloecker [at] kde>

> On Sunday 08 November 2009, Marko Randjelovic wrote:
> > What I know is simple. I created a key today and tried it signing one
> > file and it worked. Now, few hours later, I cannot do anything, and a
> > message is wrong passphrase. I checked mod.time of secret keyring and
> > it looks like was not modified in meanwhile.
> >
> > I am really confused, sure not have modified my passphrase, nor
> > forget it, but it simply does not work anymore.
> >
> > Is there a way to check if secret key info was modified?
>
> Do you use multiple keyboard layouts? If yes, then maybe you used
> another keyboard layout when you created the key.
>
>
> Regards,
> Ingo
>
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users [at] gnupg
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
>
>

mephisto at fastmail

Nov 8, 2009, 7:40 PM

Post #4 of 4 (738 views)
Permalink

Re: I am sure I did not forget my passphrase [In reply to]

On Sun, Nov 08, 2009 at 04:24:01PM +0100 Marko Randjelovic wrote:
>
> Is there a way to check if secret key info was modified?

Check the time/date of the latest self-signature on the key.

However, if the key data was unintentionally modified outside of gpg,
such as through data corruption, then there is likely no way to recover
from it (unless you have a backup stored somewhere).

--
"Le hasard favorise l'esprit préparé."
--Louis Pasteur

_______________________________________________
Gnupg-users mailing list
Gnupg-users [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads