linux-kernel - Re: git email From: parsing (was Re: [GIT PULL] Staging/IIO driver patches for 4.11-rc1)

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: <20170223075859.g6ert55bvbe44dxc@localhost>
Date:   Thu, 23 Feb 2017 08:59:23 +0100
From:   Simon Sandström <simon@...anor.nu>
To:     Jeff King <peff@...f.net>, Greg KH <gregkh@...uxfoundation.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>, git@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Driver Project <devel@...uxdriverproject.org>
Subject: Re: git email From: parsing (was Re: [GIT PULL] Staging/IIO driver
 patches for 4.11-rc1)

On Thu, Feb 23, 2017 at 01:17:02AM -0500, Jeff King wrote:
> On Thu, Feb 23, 2017 at 07:04:44AM +0100, Greg KH wrote:
> 
> > 
> > I don't know what happened, I used git for this, I don't use quilt for
> > "normal" patches accepted into my trees anymore, only for stable kernel
> > work.
> > 
> > So either the mail is malformed, or git couldn't figure it out, I've
> > attached the original message below, and cc:ed the git mailing list.
> > 
> > Also, Simon emailed me after this was committed saying something went
> > wrong, but I couldn't go back and rebase my tree.  Simon, did you ever
> > figure out if something was odd on your end?
> > 
> > Git developers, any ideas?
> 
> The problem isn't on the applying end, but rather on the generating end.
> The From header in the attached mbox is:
> 
>   From: =?us-ascii?B?PT9VVEYtOD9xP1NpbW9uPTIwU2FuZHN0cj1DMz1CNm0/PQ==?= <simon@...anor.nu>
> 
> If you de-base64 that, you get:
> 
>   =?UTF-8?q?Simon=20Sandstr=C3=B6m?=
> 
> So something double-encoded it before it got to your mbox.
> 
> -Peff

Hi,

Yes, Mutt on my end caused this. I used Mutt 1.5.23, and I either had
it misconfigured or it simply can't handle files that contains encoded
From:/Subject:-fields when you run it with mutt -H <file>.

I upgraded to Mutt 1.7.1 which solved the problem.

- Simon