Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Fri, 3 Jan 2014 01:16:25 +0100
From: Frank Dittrich <>
Subject: Re: Some bleeding-jumbo formats with SEGV and ABRT

On 01/03/2014 12:53 AM, magnum wrote:
> On 2014-01-03 00:44, Frank Dittrich wrote:
>> Am I missing something? How do I attach a file when reporting GitHub
>> issues?
> For large-ish things you can use gist and link to it. For just a couple
> lines of crash-hashes you'd just post them inline (preferrably
> surrounded by ``` which will make them show "preformatted").

I wasn't sure how whether or not extra long lines (e.g. LUKS format
hashes) will survive.

> Or post to this list just like you did, and then open an issue that
> points to the mail archive of that post.

But the mail archive's won't help.

The plain text file fail_clipperz attached to my mail

Message-ID: <BLU0-SMTP1730A86A68283B01D59F9D5FDC80@....gbl>

ended up mangled in different ways here (@ in mail address replaced):

and here (lines wrapped and mail addresses mangled):

How can I be sure that the issues I report can be reproduced with these
mangled versions of my files.

And the file attached to my earlier mail ends up here:

In this case, at least the contents is the same I posted, you just have
to rename the file after downloading it.
But who knows whether or not an attached .tgz file might be mangled as
well, depending on the contents? I don't

Creating GitHub issues as a reminder is OK. But in the end, you'll need
the real john-dev mail, not some web based mailing list archive.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.