On Friday 25 May 2007 05:09, engage wrote:
> On Thursday 24 May 2007 11:54, Ingo Klöcker wrote:
> > On Thursday 24 May 2007 01:21, engage wrote:
> > > I wasn't prompted for a passphrase!
> > >
> > > gnupg2-1.9.22-2.2mdv2007.0
> > > gnupg-1.4.7-0.2mdv2007.0
> > > kdepim-kmail-3.5.4-12mdv2007.0
> >
>
On Thursday 24 May 2007 11:54, Ingo Klöcker wrote:
> On Thursday 24 May 2007 01:21, engage wrote:
> > I wasn't prompted for a passphrase!
> >
> > gnupg2-1.9.22-2.2mdv2007.0
> > gnupg-1.4.7-0.2mdv2007.0
> > kdepim-kmail-3.5.4-12mdv2007.0
>
> That's just a wild guess, but the usual reason for this be
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
engage wrote:
> I wasn't prompted for a passphrase!
Perhaps the message was only ASCII-armored.
- --
Windows NT 5.1.2600 | Thunderbird 2.0.0.0 | Enigmail 0.95.0 | GPG 1.4.7
Key ID: 0x60A78FCB - available on major keyservers and upon request
Fing
On Thursday 24 May 2007 01:21, engage wrote:
> I wasn't prompted for a passphrase!
>
> gnupg2-1.9.22-2.2mdv2007.0
> gnupg-1.4.7-0.2mdv2007.0
> kdepim-kmail-3.5.4-12mdv2007.0
That's just a wild guess, but the usual reason for this behavior is that
gpg-agent is not setup correctly. I suggest you re
> I wasn't prompted for a passphrase!
Without more information, it's impossible to tell you anything
useful. We need to know a lot more than this.
--
Robert J. Hansen <[EMAIL PROTECTED]>
"Most people are never thought about after they're gone. 'I wonder
where Rob got the plutonium?' is bett
I wasn't prompted for a passphrase!
gnupg2-1.9.22-2.2mdv2007.0
gnupg-1.4.7-0.2mdv2007.0
kdepim-kmail-3.5.4-12mdv2007.0
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
