linux-kernel - Re: [GIT PULL] integrity subsystem fixes for v5.7

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: <1589824719.5111.126.camel@linux.ibm.com>
Date:   Mon, 18 May 2020 13:58:39 -0400
From:   Mimi Zohar <zohar@...ux.ibm.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     linux-integrity <linux-integrity@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] integrity subsystem fixes for v5.7

On Mon, 2020-05-18 at 10:47 -0700, Linus Torvalds wrote:
> On Mon, May 18, 2020 at 8:49 AM Mimi Zohar <zohar@...ux.ibm.com> wrote:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity.fixes
> 
> No such head.
> 
> It looks like the plain 'fixes' branch has the same commit ID, but
> there's no next-integrity.fixes.

Ugh, that's the name of my local branch.  The remote branch is "fixes"
as you figured out.

> 
> Btw, any chance you could start using signed tags? I've been
> encouraging people to do that even on kernel.org, and we've got fairly
> high coverage these days..

Sure, will figure out how in time for the next open window, if that is
Ok.

Mimi