linux-kernel - Re: [PATCH 0/4] BFS backport to 2.6.27

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 05 Oct 2009 16:20:29 -0400
From:	Valdis.Kletnieks@...edu
To:	David Newall <davidn@...idnewall.com>
Cc:	"Jayson R. King" <dev@...sonking.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Con Kolivas <kernel@...ivas.org>
Subject: Re: [PATCH 0/4] BFS backport to 2.6.27

On Tue, 06 Oct 2009 03:34:48 +1030, David Newall said:

> Yes, I was trying for irony.  Mime has been around for many decades and
> anybody claiming that they can't cope with them is probably very stupid
> or lying to make some strange point.  Anyway, I'm not trying to change
> the policy, but was only have a snide dig, en passant, at the crufty,
> old, has-been attitude that it represents.

The problem is that with most MUAs, if you do a 'reply and quote text',
it only operates correctly on the first/main body part - doing a 'reply and
quote' to an *attachment* is usually a lot harder, and doing a 'reply and
quote text from both main body and attachment' is usually convoluted enough
that 'Just Hit Delete' becomes tempting...

I've submitted my share of one-liner patches, and they've all been
PGP-signed, so they show up as MIME multiparts - and yet I've never ONCE
been asked to change it.  I have to conclude that it's because although it's
a multipart, it's a multipart that DTRT when a maintainer hits 'reply' -
and that production MUAs still DTWT when dealing with replying to the
attachments rather than the main body....

Content of type "application/pgp-signature" skipped