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  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]
Date:   Thu, 1 Apr 2021 16:13:21 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     Al Viro <viro@...iv.linux.org.uk>
Cc:     Roy Yang <royyang@...gle.com>, keescook@...omium.org,
        akpm@...ux-foundation.org, alex.popov@...ux.com,
        ard.biesheuvel@...aro.org, catalin.marinas@....com, corbet@....net,
        david@...hat.com, elena.reshetova@...el.com, glider@...gle.com,
        jannh@...gle.com, kernel-hardening@...ts.openwall.com,
        linux-arm-kernel@...ts.infradead.org,
        linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, luto@...nel.org, mark.rutland@....com,
        peterz@...radead.org, rdunlap@...radead.org, rppt@...ux.ibm.com,
        tglx@...utronix.de, vbabka@...e.cz, will@...nel.org, x86@...nel.org
Subject: Re: [PATCH] Where we are for this patch?

On Thu, Apr 01, 2021 at 07:48:30PM +0000, Al Viro wrote:
> On Thu, Apr 01, 2021 at 12:17:44PM -0700, Roy Yang wrote:
> > Both Android and Chrome OS really want this feature; For Container-Optimized OS, we have customers
> > interested in the defense too.
> > 
> > Thank you very much.
> > 
> > Change-Id: I1eb1b726007aa8f9c374b934cc1c690fb4924aa3
> 
> 	You forgot to tell what patch you are refering to.  Your
> Change-Id (whatever the hell that is) doesn't help at all.  Don't
> assume that keys in your internal database make sense for the
> rest of the world, especially when they appear to contain a hash
> of something...

The Change-Id fails to have any direct search hits at lore.kernel.org.
However, it turn up Roy's original patch, and clicking on the
message-Id in the "In-Reply-Field", it apperas Roy was replying to
this message:

https://lore.kernel.org/lkml/20210330205750.428816-1-keescook@chromium.org/

which is the head of this patch series:

Subject: [PATCH v8 0/6] Optionally randomize kernel stack offset each syscall

That being said, it would have been better if the original subject
line had been preserved, and it's yet another example of how the
lore.kernel.org URL is infinitely better than the Change-Id.  :-)

		       		  	      - Ted

Powered by blists - more mailing lists