Kmail plugin progress

Robin Lynn Frank rlfrank@paradigm-omega.com
Sun Jul 20 20:17:02 2003


--Boundary-02=_mztG/cRcms+WDBq
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Sunday 20 July 2003 10:34 am, John B  wrote:
> On Sunday 20 July 2003 00:00, Todd wrote:
> > Robin Lynn Frank wrote:
> > > I guess it just took me by surprise that anyone would consider cachei=
ng
> > > passphrases.
> >
> > You can change that if you like, AFAIK.  Put
> >
> >     default-cache-ttl 0
> >
> > into ~/.gnupg/gpg-agent.conf.  I don't use KMail or gpg-agent so I can't
> > tell you for sure that this works, but it should.  I'm sure a friend of
> > mine set this when he started using KMail's crypto plugins and decided =
he
> > didn't want his passphrase cached.
>
>   I don't understand the problem. My kmail, in the settings for crypto, I
> have the 'cache passphrase' unchecked, and it doesn't matter how quickly I
> make one email and sign and send it and do a second within 6-7 seconds...I
> *always* get asked for the passphrase...as I expect and want, which means
> it's working correctly.
>   I've got gpg-agent commented out, and both crypt-plugins working/active
> also just fine.
>
>   John

I, to, have the cache passphrase checkbox unchecked.  That is why I was=20
surprised that I could occasionally, send signed messages without  having t=
o=20
enter the passphrase.

Now I have 2 questions:
How does the plugin work with gpog-agent commented out???
Does your certificate manager function.  Mine always crashes.
=2D-=20
Robin Lynn Frank | Director of Operations | Paradigm-Omega, LLC

Whom the gods would destroy, they first make mad.
Whom the gods would make mad, they first give computers.

--Boundary-02=_mztG/cRcms+WDBq
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/GtzmzXwq4t8X1KoRAjQHAJ9eJTiKZJ8SVWio7jLKZFRJzf5alQCfRICC
RJWEyd5RV/MWJIq8cfmbzJc=
=4N5l
-----END PGP SIGNATURE-----

--Boundary-02=_mztG/cRcms+WDBq--