OpenVZ Forum - RDF feed
type: channel
items: [PATCH] IA64,sparc: local DoS with corrupted ELFs
items: Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs

[PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: Linus, this patch is already commited into -stable 2.6.17.y tree. http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2 .6.17.y.git;a=commit;h=8833ebaa3f4325820fe3338ccf6fae04f6669254 I only incorporated a small compilation fix from Fernando Vazquez <fernando@oss.ntt.co.jp>. please, commit it into next 2.6.18-rcX. local DoS with corrupted ELFs This patch prevents cross-region mappings on IA64 and SPARC which could lead to system crash. davem@ confirmed: "This looks fine to me." :) Signed-Off-By: Pavel Emelianov <xemul@openvz.org> Signed-Off-By: Kirill Korotaev <dev@openvz.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> --- diff --git a/arch/ia64/kernel/sys_ia64.c b/arch/ia64/kernel/sys_ia64.c index 40722d8..9ef62a3 100644 --- a/arch/ia64/kernel/sys_ia64.c +++ b/arch/ia64/kernel/sys_ia64.c @@ -163,10 +163,25 @@ sys_pipe (void) return retval; } +int ia64_mmap_check(unsigned long addr, unsigned long len, + unsigned long flags) +{ + unsigned long roff; + + /* + * Don't permit mappings into unmapped space, the virtual page table + * of a region, or across a region boundary. Note: RGN_MAP_LIMIT is + * equal to 2^n-PAGE_SIZE (for some integer n <= 61) and len > 0. + */ + roff = REGION_OFFSET(addr); + if ((len > RGN_MAP_LIMIT) || (roff > (RGN_MAP_LIMIT - len))) + return -EINVAL; + return 0; +} + static inline unsigned long do_mmap2 (unsigned long addr, unsigned long len, int prot, int flags, int fd, unsigned long pgoff) { - unsigned long roff; struct file *file = NULL; flags &= ~(MAP_EXECUTABLE | MAP_DENYWRITE); @@ -188,17 +203,6 @@ do_mmap2 (unsigned long addr, unsigned l goto out; } - /* - * Don't permit mappings into unmapped space, the virtual page table of a region, - * or across a region boundary. Note: RGN_MAP_LIMIT is equal to 2^n-PAGE_SIZE - * (for some integer n <= 61) and len > 0. - */ - roff = REGION_OFFSET(addr); - if ((len > RGN_MAP_LIMIT) || (roff > (RGN_MAP_LIMIT - len))) { - addr = -EINVAL; - goto out; - } - down_write(&current->mm->mmap_sem)…
creator: Kirill Korotaev
date: 2006-09-04T12:14:20-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Mon, Sep 04, 2006 at 04:17:00PM +0400, Kirill Korotaev wrote: > --- a/include/asm-generic/mman.h > +++ b/include/asm-generic/mman.h > @@ -39,4 +39,10 @@ #define MADV_DOFORK 11 /* do inherit ac > #define MAP_ANON MAP_ANONYMOUS > #define MAP_FILE 0 > > +#ifdef __KERNEL__ > +#ifndef arch_mmap_check > +#define arch_mmap_check(addr, len, flags) (0) > +#endif > +#endif > + > #endif This breaks all arches that don't use asm-generic/mman.h, and that you didn't add arch_mmap_check to asm/mman.h for.
creator: Kyle McMartin
date: 2006-09-05T11:39:39-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: Andrew, Kyle, > On Mon, Sep 04, 2006 at 04:17:00PM +0400, Kirill Korotaev wrote: > >>--- a/include/asm-generic/mman.h >>+++ b/include/asm-generic/mman.h >>@@ -39,4 +39,10 @@ #define MADV_DOFORK 11 /* do inherit ac >>#define MAP_ANON MAP_ANONYMOUS >>#define MAP_FILE 0 >> >>+#ifdef __KERNEL__ >>+#ifndef arch_mmap_check >>+#define arch_mmap_check(addr, len, flags) (0) >>+#endif >>+#endif >>+ >>#endif > > > This breaks all arches that don't use asm-generic/mman.h, and that you > didn't add arch_mmap_check to asm/mman.h for. oops... You are right. is define #define arch_mmap_check(addr, len, flags) (0) ok for you in such mman.h headers which do not include asm-generic/mman.h? If yes, the following patch should help. Though I didn't get the idea of include/asm-um/mman.h: #include "asm/arch/mman.h" This patch adds define of arch_mmap_check() to archs which do not include include/asm-generic/mman.h --- diff --git a/include/asm-alpha/mman.h b/include/asm-alpha/mman.h index 5f24c75..51cf354 100644 --- a/include/asm-alpha/mman.h +++ b/include/asm-alpha/mman.h @@ -52,4 +52,10 @@ #define MADV_DOFORK 11 /* do inherit ac #define MAP_ANON MAP_ANONYMOUS #define MAP_FILE 0 +#ifdef __KERNEL__ +#ifndef arch_mmap_check +#define arch_mmap_check(addr, len, flags) (0) +#endif +#endif + #endif /* __ALPHA_MMAN_H__ */ diff --git a/include/asm-mips/mman.h b/include/asm-mips/mman.h index 046cf68..f19e858 100644 --- a/include/asm-mips/mman.h +++ b/include/asm-mips/mman.h @@ -75,4 +75,10 @@ #define MADV_DOFORK 11 /* do inherit ac #define MAP_ANON MAP_ANONYMOUS #define MAP_FILE 0 +#ifdef __KERNEL__ +#ifndef arch_mmap_check +#define arch_mmap_check(addr, len, flags) (0) +#endif +#endif + #endif /* _ASM_MMAN_H */ diff --git a/include/asm-parisc/mman.h b/include/asm-parisc/mman.h index 0ef15ee..9829b31 100644 --- a/include/asm-parisc/mman.h +++ b/include/asm-parisc/mman.h @@ -59,4 +59,10 @@ #define MAP_ANON MAP_ANONYMOUS #define MAP_FILE 0 #define MAP_VARIABLE 0 +#ifdef __KERNEL__ +#ifndef arch_mmap_…
creator: dev
date: 2006-09-05T13:06:57-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Mon, 4 Sep 2006, Kirill Korotaev wrote: > > this patch is already commited into -stable 2.6.17.y tree. I don't like it. Apparently the patch was bad, and broken on MIPS and parisc, and it was applied to the stable tree without being in the standard tree. If MIPS and parisc don't matter for the stable tree (very possible - there are no big commercial distributions for them), then dammit, neither should ia64 and sparc (there are no big commercial distros for them either). Either way, it seems this didn't happen the way it should have. The proper fix would _seem_ to have the whole #ifndef arch_mmap_check #define arch_mmap_check(addr, len, flags) (0) #endif in the only file that actually _uses_ this, namely mm/mmap.c. Rather than pollute lots of architecture-specific files with this macro that nobody really is interested in except for ia64 and sparc. Linus
creator: Linus Torvalds
date: 2006-09-06T18:24:05-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Wed, Sep 06, 2006 at 11:24:05AM -0700, Linus Torvalds wrote: > If MIPS and parisc don't matter for the stable tree (very possible - there > are no big commercial distributions for them), then dammit, neither should > ia64 and sparc (there are no big commercial distros for them either). Erm, RHEL and SLES both support ia64.
creator: Matthew Wilcox
date: 2006-09-06T18:27:33-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Wed, 2006-09-06 at 12:27 -0600, Matthew Wilcox wrote: > On Wed, Sep 06, 2006 at 11:24:05AM -0700, Linus Torvalds wrote: > > If MIPS and parisc don't matter for the stable tree (very possible - there > > are no big commercial distributions for them), then dammit, neither should > > ia64 and sparc (there are no big commercial distros for them either). > > Erm, RHEL and SLES both support ia64. but neither use -stable.
creator: Arjan van de Ven
date: 2006-09-06T19:06:19-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Mon, 4 Sep 2006, Kirill Korotaev wrote: > > +#ifdef __KERNEL__ > +#define arch_mmap_check ia64_mmap_check > +#ifndef __ASSEMBLY__ > +int ia64_mmap_check(unsigned long addr, unsigned long len, > + unsigned long flags); > +#endif > +#endif Btw, is there some reason for the __ASSEMBLY__ check? I'm not seeing any kernel users that could care, a quick git grep 'mman\.h' -- '*.[sS]' doesn't trigger anything, and the other header files that include this seem to all either be mman.h themselves, or have things like structure declarations etc that wouldn't work for any non-C source anyway. But maybe I missed some. I'd rather not have more of those '#ifndef __ASSEMBLY__' than necessary. Linus
creator: Linus Torvalds
date: 2006-09-06T20:20:59-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Wed, Sep 06, 2006 at 01:20:59PM -0700, Linus Torvalds wrote: > Btw, is there some reason for the __ASSEMBLY__ check? On ia64 entry.S includes asm/pgtable.h, which includes asm/mman.h -Tony
creator: tony.luck
date: 2006-09-06T21:27:54-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Wed, 2006-09-06 at 13:20 -0700, Linus Torvalds wrote: > > On Mon, 4 Sep 2006, Kirill Korotaev wrote: > > > > +#ifdef __KERNEL__ > > +#define arch_mmap_check ia64_mmap_check > > +#ifndef __ASSEMBLY__ > > +int ia64_mmap_check(unsigned long addr, unsigned long len, > > + unsigned long flags); > > +#endif > > +#endif > > Btw, is there some reason for the __ASSEMBLY__ check? > > I'm not seeing any kernel users that could care, a quick > > git grep 'mman\.h' -- '*.[sS]' > > doesn't trigger anything, and the other header files that include this > seem to all either be mman.h themselves, or have things like structure > declarations etc that wouldn't work for any non-C source anyway. > > But maybe I missed some. > > I'd rather not have more of those '#ifndef __ASSEMBLY__' than necessary The problem is that "asm/mman.h" is being included from entry.S indirectly through "asm/pgtable.h" (see code snips below). * arch/ia64/kernel/entry.S: ... #include <asm/pgtable.h> ... * include/asm-ia64/pgtable.h: ... #include <asm/mman.h> ... * include/asm-ia64/mman.h ... #ifdef __KERNEL__ #define arch_mmap_check ia64_map_check_rgn int ia64_map_check_rgn(unsigned long addr, unsigned long len, unsigned long flags); #endif ... Without this fix compilation is broken: gcc -Wp,-MD,arch/ia64/kernel/.entry.o.d -nostdinc -isystem /usr/lib/gcc/ia64-linux-gnu/4.1.2/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -DHAVE_WORKING_TEXT_ALIGN -DHAVE_MODEL_SMALL_ATTRIBUTE -DHAVE_SERIALIZE_DIRECTIVE -D__ASSEMBLY__ -mconstant-gp -c -o arch/ia64/kernel/entry.o arch/ia64/kernel/entry.S include/asm/mman.h: Assembler messages: include/asm/mman.h:13: Error: Unknown opcode `int ia64_map_check_rgn(unsigned long addr,unsigned long len,' include/asm/mman.h:14: Error: Unknown opcode `unsigned long flags)' make[1]: *** [arch/ia64/kernel/entry.o] Error 1 make: *** [arch/ia64/kernel] Error 2 Regards, Fernando
creator: fernando
date: 2006-09-06T23:23:11-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: > On Mon, 4 Sep 2006, Kirill Korotaev wrote: >>this patch is already commited into -stable 2.6.17.y tree. > > > I don't like it. Apparently the patch was bad, and broken on MIPS and > parisc, and it was applied to the stable tree without being in the > standard tree. it is locally exploitable DoS IMHO. I'm not sure what is the policy about security fixes, since Tony Luck didn't show much interest in this fix and I kept pushing it myself. Probably I should have published an exploit to make it moving direct way :) And I really sorry for patch sent being broken a bit :/ > If MIPS and parisc don't matter for the stable tree (very possible - there > are no big commercial distributions for them), then dammit, neither should > ia64 and sparc (there are no big commercial distros for them either). > Either way, it seems this didn't happen the way it should have. > > The proper fix would _seem_ to have the whole > > #ifndef arch_mmap_check > #define arch_mmap_check(addr, len, flags) (0) > #endif > > in the only file that actually _uses_ this, namely mm/mmap.c. Rather than > pollute lots of architecture-specific files with this macro that nobody > really is interested in except for ia64 and sparc. Does the patch below looks better? (compile tested on IA64) --- diff --git a/arch/ia64/kernel/sys_ia64.c b/arch/ia64/kernel/sys_ia64.c index 40722d8..5b190c9 100644 --- a/arch/ia64/kernel/sys_ia64.c +++ b/arch/ia64/kernel/sys_ia64.c @@ -163,10 +163,25 @@ sys_pipe (void) return retval; } +int ia64_mmap_check(unsigned long addr, unsigned long len, + unsigned long flags) +{ + unsigned long roff; + + /* + * Don't permit mappings into unmapped space, the virtual page table + * of a region, or across a region boundary. Note: RGN_MAP_LIMIT is + * equal to 2^n-PAGE_SIZE (for some integer n <= 61) and len > 0. + */ + roff = REGION_OFFSET(addr); + if ((len > RGN_MAP_LIMIT) || (roff > (RGN_MAP_LIMIT - len))) + return -EINVAL; + return 0; +} + static inline unsigned long do_mmap2 (unsigned long …
creator: Kirill Korotaev
date: 2006-09-07T10:14:02-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Thu, 7 Sep 2006, Kirill Korotaev wrote: > > Does the patch below looks better? Yes. Apart from the whitespace corruption, that is. I don't know how to get mozilla to not screw up whitespace. Linus
creator: Linus Torvalds
date: 2006-09-07T15:17:04-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Thu, Sep 07, 2006 at 08:17:04AM -0700, Linus Torvalds wrote: > > > On Thu, 7 Sep 2006, Kirill Korotaev wrote: > > > > Does the patch below looks better? > > Yes. > > Apart from the whitespace corruption, that is. > > I don't know how to get mozilla to not screw up whitespace. maybe by using it to download mutt or something saner ? :-) More seriously, while we don't like email attachments because they make it impossible to comment on a patch, maybe we should encourage people with broken mailers to post small patches in both forms : - pure text for human review (spaces are not much of a problem here) - MIME to apply the patch. At least when the do so, they should insist on it at the top of the patch, or even manually mangle the patch header so that GIT (or any other tool) does not use it. > Linus Regards Willy
creator: Willy Tarreau
date: 2006-09-07T20:07:14-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Thu, 7 Sep 2006 22:07:14 +0200 Willy Tarreau <w@1wt.eu> wrote: > On Thu, Sep 07, 2006 at 08:17:04AM -0700, Linus Torvalds wrote: > > > > > > On Thu, 7 Sep 2006, Kirill Korotaev wrote: > > > > > > Does the patch below looks better? > > > > Yes. > > > > Apart from the whitespace corruption, that is. > > > > I don't know how to get mozilla to not screw up whitespace. Me either. I've had a bug report in the mozilla system for maybe four years concerning space-stuffing. Occasionally it comes to life but afaict nothing ever changes. I expect it'd be pretty easy to undo the space-stuffing in git. In extremis I just do s/^ /^ / and it works. An automated solution would need to recognise the appropriate headers (Format=Flowed, iirc). > maybe by using it to download mutt or something saner ? :-) > > More seriously, while we don't like email attachments because they make > it impossible to comment on a patch, maybe we should encourage people > with broken mailers to post small patches in both forms : > - pure text for human review (spaces are not much of a problem here) > - MIME to apply the patch. argh. That means that email contains two copies of the patch. So it applies with `patch --dry-run' then causes havoc with `patch'
creator: Andrew Morton
date: 2006-09-07T23:42:07-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Thu, Sep 07, 2006 at 04:42:07PM -0700, Andrew Morton wrote: > On Thu, 7 Sep 2006 22:07:14 +0200 > Willy Tarreau <w@1wt.eu> wrote: > > > On Thu, Sep 07, 2006 at 08:17:04AM -0700, Linus Torvalds wrote: > > > > > > > > > On Thu, 7 Sep 2006, Kirill Korotaev wrote: > > > > > > > > Does the patch below looks better? > > > > > > Yes. > > > > > > Apart from the whitespace corruption, that is. > > > > > > I don't know how to get mozilla to not screw up whitespace. > > Me either. I've had a bug report in the mozilla system for maybe four > years concerning space-stuffing. Occasionally it comes to life but afaict > nothing ever changes. > > I expect it'd be pretty easy to undo the space-stuffing in git. Perhaps, but it should not be up to the versionning system to decide to change the contents of the patches which get merged. Otherwise, we will not be able to trust it as much as today. > In extremis I just do s/^ /^ / and it works. An automated solution would > need to recognise the appropriate headers (Format=Flowed, iirc). perhaps for this case, but then what will prevent us from trying to implement dirtier features such as line un-wrapping ? > > maybe by using it to download mutt or something saner ? :-) > > > > More seriously, while we don't like email attachments because they make > > it impossible to comment on a patch, maybe we should encourage people > > with broken mailers to post small patches in both forms : > > - pure text for human review (spaces are not much of a problem here) > > - MIME to apply the patch. > > argh. That means that email contains two copies of the patch. So it > applies with `patch --dry-run' then causes havoc with `patch' except if the text version is mangled in order not to be detected as a patch. I suspect that inserting a space in front of "---" is enough for patch not to find it. Don't get me wrong, I know this is dirty. But as long as some people will use broken mailers, we'll get broken patches. Some people occasionnaly switch to attac…
creator: Willy Tarreau
date: 2006-09-08T04:34:12-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: >>>>> "Arjan" == Arjan van de Ven <arjan@infradead.org> writes: Arjan> On Wed, 2006-09-06 at 12:27 -0600, Matthew Wilcox wrote: >> On Wed, Sep 06, 2006 at 11:24:05AM -0700, Linus Torvalds wrote: > >> If MIPS and parisc don't matter for the stable tree (very possible >> - there > are no big commercial distributions for them), then >> dammit, neither should > ia64 and sparc (there are no big >> commercial distros for them either). >> >> Erm, RHEL and SLES both support ia64. Arjan> but neither use -stable. And getting a patch into -stable tends to be a really good argument for a backport into the next vendor kernel :) Cheers, Jes
creator: Jes Sorensen
date: 2006-09-08T09:12:21-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: Linus Torvalds wrote: >>Does the patch below looks better? > > > Yes. > > Apart from the whitespace corruption, that is. > > I don't know how to get mozilla to not screw up whitespace. What is funny is that mozilla doesn't screw up whitespaces. 2 people checked that patch from the email applies to the kernel. 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? Thanks, Kirill
creator: dev
date: 2006-09-08T15:12:31-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: 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). Linus
creator: Linus Torvalds
date: 2006-09-08T15:35:03-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: 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
creator: Dave Jones
date: 2006-09-08T15:49:45-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: 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). Oh, I finally found how to tune Mozilla and fix it: One need to edit defaults/pref/mailnews.js file to have: pref("mailnews.send_plaintext_flowed", false); // RFC 2646======= pref("mailnews.display.disable_format_flowed_support", true); This makes Mozilla to send emails w/o "format=flowed". Thanks a lot for your patience :) Kirill
creator: dev
date: 2006-09-08T16:06:06-00:00

Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
type: item
description: On Fri, 08 Sep 2006 20:09:22 +0400 Kirill Korotaev wrote: > 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). > Oh, I finally found how to tune Mozilla and fix it: > > One need to edit defaults/pref/mailnews.js file to have: > pref("mailnews.send_plaintext_flowed", false); // RFC 2646======= > pref("mailnews.display.disable_format_flowed_support", true); > > This makes Mozilla to send emails w/o "format=flowed". > > Thanks a lot for your patience :) Here is some (similar) info for thunderbird: http://mbligh.org/linuxdocs/Email/Clients/Thunderbird --- ~Randy
creator: rdunlap
date: 2006-09-13T15:45:20-00:00