From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kirill Korotaev <dev@sw.ru>, Kirill Korotaev <dev@openvz.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Fernando Vazquez <fernando@oss.ntt.co.jp>,
"David S. Miller" <davem@davemloft.net>,
tony.luck@intel.com, linux-ia64@vger.kernel.org,
stable@kernel.org, xemul@openvz.org, devel@openvz.org
Subject: Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
Date: Fri, 8 Sep 2006 11:49:45 -0400 [thread overview]
Message-ID: <20060908154945.GI28592@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609080831530.27779@g5.osdl.org>
On Fri, Sep 08, 2006 at 08:35:03AM -0700, Linus Torvalds wrote:
>
>
> On Fri, 8 Sep 2006, Kirill Korotaev wrote:
> >
> > I even checked the email myself and the only difference between "good"
> > patches and mine is that mine has "format=flowed" in
> > Content-Type: text/plain; charset=us-ascii; format=flowed
> >
> > It looks like some mailers replace TABs with spaces when format=flowed
> > is specified. So are you sure that the problem is in mozilla?
>
> Hey, what do you know? Good call. I can actually just "S"ave the message
> to a file, and it is a perfectly fine patch. But when I view it in my mail
> reader, your "format=flowed" means that it _shows_ it as being corrupted
> (ie word wrapping and missing spaces at the beginning of lines).
>
> Will apply, thanks. It would be better if your mailer didn't lie about the
> format though (treating the text as "flowed" definitely isn't right, and
> some mail gateways might actually find it meaningful, for all I know).
I got bitten by this myself a while ago. Since then I added this
hack to my .procmailrc
:0fw
| /usr/bin/perl -pe 's/^(Content-Type: .*)format=flowed/\1format=flawed/'
now I see patches as they were intended..
Dave
next prev parent reply other threads:[~2006-09-08 15:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 12:17 [PATCH] IA64,sparc: local DoS with corrupted ELFs Kirill Korotaev
2006-09-05 11:39 ` Kyle McMartin
2006-09-05 13:08 ` Kirill Korotaev
2006-09-06 18:24 ` Linus Torvalds
2006-09-06 18:27 ` Matthew Wilcox
2006-09-06 18:45 ` [stable] " Greg KH
2006-09-06 19:12 ` Matthew Wilcox
2006-09-06 19:17 ` Christoph Lameter
2006-09-06 19:25 ` Greg KH
2006-09-06 20:27 ` Willy Tarreau
2006-09-07 13:11 ` Marcel Holtmann
2006-09-07 15:37 ` Greg KH
2006-09-08 9:11 ` Jes Sorensen
2006-09-06 19:06 ` Arjan van de Ven
2006-09-08 9:12 ` Jes Sorensen
2006-09-07 10:17 ` Kirill Korotaev
2006-09-07 15:17 ` Linus Torvalds
2006-09-07 20:07 ` Willy Tarreau
2006-09-07 23:42 ` Andrew Morton
2006-09-08 4:34 ` Willy Tarreau
2006-09-08 15:15 ` Kirill Korotaev
2006-09-08 15:35 ` Linus Torvalds
2006-09-08 15:49 ` Dave Jones [this message]
2006-09-08 16:09 ` Kirill Korotaev
2006-09-13 15:46 ` Randy.Dunlap
2006-09-06 20:20 ` Linus Torvalds
2006-09-06 21:27 ` Luck, Tony
2006-09-06 23:23 ` Fernando Luis Vázquez Cao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060908154945.GI28592@redhat.com \
--to=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvz.org \
--cc=dev@sw.ru \
--cc=devel@openvz.org \
--cc=fernando@oss.ntt.co.jp \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@osdl.org \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox