linux-kernel - Re: LKML admins (syzbot emails are not delivered)

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: <20180116231313.GL8249@thunk.org>
Date:   Tue, 16 Jan 2018 18:13:13 -0500
From:   Theodore Ts'o <tytso@....edu>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     "Eric W. Biederman" <ebiederm@...ssion.com>,
        Pavel Machek <pavel@....cz>, Mike Galbraith <efault@....de>,
        LKML <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        syzkaller <syzkaller@...glegroups.com>
Subject: Re: LKML admins (syzbot emails are not delivered)

On Tue, Jan 16, 2018 at 09:31:26AM +0100, Dmitry Vyukov wrote:
> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o <tytso@....edu> wrote:
> > I just checked a recent report from the Syzbot, and it's not fixed.
> > The raw.log file still uses a Content-Type of
> > Application/Octet-stream.  Worse the reproducer C source file has a
> > content type of Application/Octet-stream instead of the much more sane
> > Application/text.  <Face palm>
> 
> 
> I will look into using a different mailing system which allows more
> control over email contents.
> A quick fix for raw.log will be to rename it to raw.log.txt. Not sure
> if text/plain repro.c.txt is better than application/octet-stream
> repro.c...

My personal opinion is that if there is no way to force the content
type except by using magic extensions --- which is super-surprising to
me; that seems like a broken API and a feature request bug should be
filed against the relevant API --- using repro.c.txt would be the best
of bad alternatives.  Someone is going to have to exit to a shell to
compile the repro, and renaming the filename isn't a big deal.  The
Mail User Agent I use (mutt) allows me to specify the directory to
save the file, and gives me the opportunity to edit the filename,
before I save it.  So at least for me, it really isn't a big deal for
you to use repro.c.txt.

Cheers,

					- Ted