decrypt-save, decode-save & pgp exit modes
The basic problem here is that PGP's exit statuses are chronically
unreliable. I've now added a test to pgp_decrypt_part that raises
an error (i.e., returns NULL) when PGP's output is empty.
Any other thoughts?
(BTW, I'm less concerned about decode-save, since that one is a
"best effort" kind of function anyway -- it maps everything to
text/plain and hence is guaranteed to use data.)
--
Thomas Roessler · Personal soap box at <http://log.does-not-exist.org/>.
On 2005-01-26 23:17:48 +0900, TAKAHASHI Tamotsu wrote:
> From: TAKAHASHI Tamotsu <ttakah@xxxxxxxxxxxxxxxxx>
> To: mutt-dev@xxxxxxxx
> Date: Wed, 26 Jan 2005 23:17:48 +0900
> Subject: Re: Mutt Next Generation
> Mail-Followup-To: mutt-dev@xxxxxxxx
> X-Spam-Level:
>
> On Wed, Jan 26, 2005 at 01:21:31PM +0100, Christoph Berg wrote:
> (URL modified by tamo)
> > * including patches
> > There are tons of mutt patches out there. See for example the list
> > posted on mutt-dev recently:
> > http://www.df7cb.de/mutt/message/20041221.091949.42f233d6.en.html
> >
> > Adding (some of) those should be postponed to 1.7, imho.
> > Which to include should be discussed on mutt-dev.
>
> Decrypt-save was partly fixed, but the fix was said to be insufficient.
> ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=275188&msg=36 )
>
> Decode-save has to be fixed or disabled before releasing a new version.
> But my patch was too complicated to take it easily.
> ( http://www.df7cb.de/mutt/message/20041223.112018.3f5be531.en.html )
>
> These bugs can cause severe problems.
> IMO, decrypt-save and decode-save should be disabled, and
> decrypt-copy and decode-copy should say
> "Copied. But it isn't certain. Please check!"
> after copying. This behaviour doesn't require rocket science.
>
> --
> tamo
>
>