linux-ext4 - Backport Ext4 Crypto Patches from 4.4 to 4.1

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>] [day] [month] [year] [list]

Message-ID: <CADGQwwN6aw4H7WaTbKs17j9z_G3GzXZ+UF0NBKp8id-xWfXbxg@mail.gmail.com>
Date:	Fri, 5 Feb 2016 13:05:10 +0100
From:	Johannes Stuettgen <johannes.stuettgen@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: Backport Ext4 Crypto Patches from 4.4 to 4.1

Hello,

I recently stumbled over the "ext4 changes for 4.4" pull request [1]
on lkml and gladly appreciate the work being done there. Especially
the fixes for ext4 crypto are interesting to me, as I'm planning to
use it for an upcoming product. Unfortunately, that product is fixed
to using kernel 4.1, and there is not much I can do about that. Are
there plans to backport the fixes for ext4 crypto from 4.4 to 4.1?
Since they fix some quite severe problems, they are basically a must
for users of ext4 crypto (to quote Theodore Ts'o: "Anyone wishing to
use the encryption feature should backport all of the ext4 crypto
patches up to 4.4 to get fixes to a memory leak and file system
corruption bug.").

Thanks in advance and best regards,

Johannes

[1] https://lkml.org/lkml/2015/11/6/417
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html