linux-kernel - Re: formail doing weird things (was: [ 01/37] Remove easily user-triggerable BUG from generic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120718175847.GA5666@mobil.systemanalysen.net>
Date:	Wed, 18 Jul 2012 19:58:47 +0200
From:	Roland Eggner <edvx1@...temanalysen.net>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: formail doing weird things (was: [ 01/37] Remove easily
 user-triggerable BUG from generic_setlease)

On 2012-07-17 Tuesday at 17:14 -0700 Greg KH wrote:
> On Tue, Jul 17, 2012 at 05:02:38PM -0700, Greg Kroah-Hartman wrote:
> > From: Greg KH <gregkh@...uxfoundation.org>
> > 
> > 3.4-stable review patch.  If anyone has any objections, please let me know.
> > 
> > ------------------
> 
> Argh, I give up, I just can't get message threading working properly
> these days.  These are the 3.4 patches, in response to the 3.0 patches,
> and it took 2 tries to send them out due to formail doing wierd things.

A few months ago I could fix my “formail troubles” by removing option “-d” from 
formail calls in my scripts.  formail manpage conceals nasty consequences of “do 
not require strict mbox format”:  nearly any “from” nearby an empty line and 
probably other things will trigger message splitting.

Maybe this helps you or somebody else.

Sorry for being slightly OT, and many thanks for your great maintainance work on 
stable kernel releases.

-- 
Roland Eggner

Content of type "application/pgp-signature" skipped