Re: bug(?): large message / pgpenvelope

[Frank T. <ft...@ui...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Johan Lundberg, at 22:25 +0200 on Sat, 30 Sep 2000, wrote:

> Thank you for the quick response... While I have your attention. I have a
> harder question, namely: How come pgpenvelope_decrypt takes so long time to
> check signatures? An example:

Because of the modules being loaded each time pgpenvelope is started,
unfortunately.  This can be helped by using the procmail filter described
in the documentation; with this, one can verify messages once when they
arrive in your mailbox, instead of each time they are read by pgpenvelope.
Another solution is to try using Pine's pipe (|) command to send the
message to pgpenvelope_decrypt when needed, instead of having it filtered
every time automatically.

> Maybe you define some functions and/or load some librarys that is not
> always used, 'just in case'. Is there any room for improvement?

There is always room for improvement :)  One solution which I like is to
have a pgpenvelope daemon running alonside the Pine process, and the
program called by Pine be very small and concise, passing on all the work
to it's big-bro (the one running outside of Pine).

- -- 
Frank Tobin		http://www.uiuc.edu/~ftobin/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (FreeBSD)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iEYEARECAAYFAjnWTZcACgkQVv/RCiYMT6OZvACeMeuRbC4vnmglrZMYEzGKeAT2
+84AoK6RrLd2OqS7+qq3eo3o4zJ6qB3B
=X7Zc
-----END PGP SIGNATURE-----