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: <CAHk-=wjjfZSxaivGyE0A3S2ZHCi=BVGdwG4++QVS80OTshBR1Q@mail.gmail.com>
Date:   Thu, 9 May 2019 13:02:37 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     James Morris <jmorris@...ei.org>
Cc:     Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        LSM List <linux-security-module@...r.kernel.org>
Subject: Re: [GIT PULL] Security subsystem: Smack updates for v5.2

On Thu, May 9, 2019 at 10:28 AM James Morris <jmorris@...ei.org> wrote:
>
> From Casey: "There's one bug fix for IPv6 handling and two memory use
> improvements."
>
> Plus a couple of further bugfixes.

I'm going to stop pulling these silly security subsystem "contains
just about as many merges as regular commits" branches starting next
merge window.

Security subsystem guys: just send your pull requests to me directly.
The history is illegible with the completely random pulls in the
middle, and I'm having a hard time editing sane merge messages with
quotes from submaintainers mixed up with other quotes.

This subsystem isn't working. I'm already taking SElinux, audit and
apparmor updates directly from the submaintainers, I'd ratehr just
take the smack updates and the TPM ones that way too. Because this is
just adding confusion as things are now.

I've pulled this, just to not cause extra confusion this merge window,
so this is just a heads-up for the future.

               Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ