kernel-hardening mailing list

Follow @Openwall on Twitter for new release announcements and other news

kernel-hardening mailing list

	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2023	35	6
2022	18	8	9	2	3	7	5			3	13	8
2021	93	161	244	118	49	53	12	44	20	49	58	11
2020	106	380	316	347	217	285	318	204	360	237	161	137
2019	254	356	92	351	159	301	354	157	139	231	245	88
2018	493	506	786	332	302	229	160	150	100	262	195	244
2017	358	642	364	408	549	685	342	443	323	380	464	244
2016	371	158	158	222	207	464	379	350	213	459	218	439
2015					3	1	4				205	184
2014	2			6	4
2013	5	10	8	168	1	1		22	25	155		6
2012	30	224	176	84	39	12	18	30	7	13		8
2011						187	185	149	131	8	66	38

Recent messages:

2023/02/01 #6: Re: Linux guest kernel threat model for Confidential Computing (Christophe de Dinechin <dinechin@...hat.com>)
2023/02/01 #5: Re: Linux guest kernel threat model for Confidential Computing ("Michael S. Tsirkin" <mst@...hat.com>)
2023/02/01 #4: Re: Linux guest kernel threat model for Confidential Computing (Christophe de Dinechin Dupont de Dinechin <cdupontd@...hat.com>)
2023/02/01 #3: Re: Linux guest kernel threat model for Confidential Computing (Christophe de Dinechin Dupont de Dinechin <cdupontd@...hat.com>)
2023/02/01 #2: Re: Linux guest kernel threat model for Confidential Computing ("Michael S. Tsirkin" <mst@...hat.com>)
2023/02/01 #1: Re: Linux guest kernel threat model for Confidential Computing (Christophe de Dinechin <dinechin@...hat.com>)
2023/01/31 #6: Re: Linux guest kernel threat model for Confidential Computing (James Bottomley <jejb@...ux.ibm.com>)
2023/01/31 #5: Re: Linux guest kernel threat model for Confidential Computing ("Michael S. Tsirkin" <mst@...hat.com>)
2023/01/31 #4: Re: Linux guest kernel threat model for Confidential Computing (Christophe de Dinechin <dinechin@...hat.com>)
2023/01/31 #3: RE: Linux guest kernel threat model for Confidential Computing ("Reshetova, Elena" <elena.reshetova@...el.com>)
2023/01/31 #2: Re: Linux guest kernel threat model for Confidential Computing (James Bottomley <jejb@...ux.ibm.com>)
2023/01/31 #1: RE: Linux guest kernel threat model for Confidential Computing ("Reshetova, Elena" <elena.reshetova@...el.com>)
2023/01/30 #2: Re: Linux guest kernel threat model for Confidential Computing (James Bottomley <jejb@...ux.ibm.com>)
2023/01/30 #1: RE: Linux guest kernel threat model for Confidential Computing ("Reshetova, Elena" <elena.reshetova@...el.com>)
2023/01/27 #10: Re: Linux guest kernel threat model for Confidential Computing (Carlos Bilbao <carlos.bilbao@....com>)
2023/01/27 #9: Re: Linux guest kernel threat model for Confidential Computing (James Bottomley <jejb@...ux.ibm.com>)
2023/01/27 #8: Re: [PATCH] fs: Use CHECK_DATA_CORRUPTION() when kernel bugs are detected (Kees Cook <keescook@...omium.org>)
2023/01/27 #7: Re: Linux guest kernel threat model for Confidential Computing ("Theodore Ts'o" <tytso@....edu>)
2023/01/27 #6: Re: Linux guest kernel threat model for Confidential Computing ("Michael S. Tsirkin" <mst@...hat.com>)
2023/01/27 #5: RE: Linux guest kernel threat model for Confidential Computing ("Reshetova, Elena" <elena.reshetova@...el.com>)
2023/01/27 #4: Re: [PATCH] fs: Use CHECK_DATA_CORRUPTION() when kernel bugs are detected (Christian Brauner <brauner@...nel.org>)
2023/01/27 #3: Re: Linux guest kernel threat model for Confidential Computing ("Michael S. Tsirkin" <mst@...hat.com>)
2023/01/27 #2: Re: Linux guest kernel threat model for Confidential Computing (Jörg Rödel <joro@...tes.org>)
2023/01/27 #1: RE: Linux guest kernel threat model for Confidential Computing ("Reshetova, Elena" <elena.reshetova@...el.com>)
2023/01/26 #12: Re: Linux guest kernel threat model for Confidential Computing ("Dr. David Alan Gilbert" <dgilbert@...hat.com>)
2023/01/26 #11: Re: Linux guest kernel threat model for Confidential Computing (Leon Romanovsky <leon@...nel.org>)
2023/01/26 #10: RE: Linux guest kernel threat model for Confidential Computing ("Reshetova, Elena" <elena.reshetova@...el.com>)
2023/01/26 #9: Re: [PATCH] fs: Use CHECK_DATA_CORRUPTION() when kernel bugs are detected (Kees Cook <keescook@...omium.org>)
2023/01/26 #8: Re: Linux guest kernel threat model for Confidential Computing ("Michael S. Tsirkin" <mst@...hat.com>)
2023/01/26 #7: Re: Linux guest kernel threat model for Confidential Computing ("Dr. David Alan Gilbert" <dgilbert@...hat.com>)
2023/01/26 #6: Re: Linux guest kernel threat model for Confidential Computing (Leon Romanovsky <leon@...nel.org>)
2023/01/26 #5: Re: Linux guest kernel threat model for Confidential Computing (Leon Romanovsky <leon@...nel.org>)
2023/01/26 #4: Re: Linux guest kernel threat model for Confidential Computing (Leon Romanovsky <leon@...nel.org>)
2023/01/26 #3: RE: Linux guest kernel threat model for Confidential Computing ("Reshetova, Elena" <elena.reshetova@...el.com>)
2023/01/26 #2: RE: Linux guest kernel threat model for Confidential Computing ("Reshetova, Elena" <elena.reshetova@...el.com>)
2023/01/26 #1: RE: Linux guest kernel threat model for Confidential Computing ("Reshetova, Elena" <elena.reshetova@...el.com>)
2023/01/25 #2: Re: Linux guest kernel threat model for Confidential Computing ("Theodore Ts'o" <tytso@....edu>)
2023/01/25 #1: RE: Linux guest kernel threat model for Confidential Computing ("Reshetova, Elena" <elena.reshetova@...el.com>)
2023/01/24 #1: Re: [PATCH] fs: Use CHECK_DATA_CORRUPTION() when kernel bugs are detected (Christian Brauner <brauner@...nel.org>)
2023/01/20 #1: [ANNOUNCE] Linux Security Summit North Americ (LSS-NA) CfP (James Morris <jmorris@...ei.org>)
2023/01/16 #1: [PATCH] fs: Use CHECK_DATA_CORRUPTION() when kernel bugs are detected (Jann Horn <jannh@...gle.com>)
2022/12/18 #1: Isolating abstract sockets (Stefan Bavendiek <stefan.bavendiek@...lbox.org>)
2022/12/06 #1: Re: Reducing runtime complexity (Luis Chamberlain <mcgrof@...nel.org>)
2022/12/03 #1: Re: Reducing runtime complexity (Stefan Bavendiek <stefan.bavendiek@...lbox.org>)
2022/12/02 #2: Re: Reducing runtime complexity (Kees Cook <keescook@...omium.org>)
2022/12/02 #1: Re: Reducing runtime complexity (Stefan Bavendiek <stefan.bavendiek@...lbox.org>)
2022/12/01 #3: Re: Reducing runtime complexity (Kees Cook <keescook@...omium.org>)
2022/12/01 #2: Re: Reducing runtime complexity (Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>)
2022/12/01 #1: Reducing runtime complexity (Stefan Bavendiek <stefan.bavendiek@...lbox.org>)
2022/11/09 #4: Re: [PATCH] exit: Put an upper limit on how often we can oops (Solar Designer <solar@...nwall.com>)
2022/11/09 #3: Re: [PATCH] exit: Put an upper limit on how often we can oops (Seth Jenkins <sethjenkins@...gle.com>)
2022/11/09 #2: Re: [PATCH] exit: Put an upper limit on how often we can oops (Jann Horn <jannh@...gle.com>)
2022/11/09 #1: RE: [PATCH] exit: Put an upper limit on how often we can oops (David Laight <David.Laight@...LAB.COM>)
2022/11/08 #5: Re: [PATCH] exit: Put an upper limit on how often we can oops (Kees Cook <keescook@...omium.org>)
2022/11/08 #4: Re: [PATCH] exit: Put an upper limit on how often we can oops (Kees Cook <keescook@...omium.org>)
2022/11/08 #3: Re: [PATCH] exit: Put an upper limit on how often we can oops (Kees Cook <keescook@...omium.org>)
2022/11/08 #2: Re: [PATCH] exit: Put an upper limit on how often we can oops (Jann Horn <jannh@...gle.com>)
2022/11/08 #1: RE: [PATCH] exit: Put an upper limit on how often we can oops (David Laight <David.Laight@...LAB.COM>)
2022/11/07 #4: Re: [PATCH] exit: Put an upper limit on how often we can oops (Jann Horn <jannh@...gle.com>)
2022/11/07 #3: Re: [PATCH] exit: Put an upper limit on how often we can oops (Solar Designer <solar@...nwall.com>)
2022/11/07 #2: Re: [PATCH] exit: Put an upper limit on how often we can oops (Linus Torvalds <torvalds@...uxfoundation.org>)
2022/11/07 #1: [PATCH] exit: Put an upper limit on how often we can oops (Jann Horn <jannh@...gle.com>)
2022/10/11 #1: Re: [Self-introduction] - Paulo Almeida (Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@...il.com>)
2022/10/10 #1: Re: [Self-introduction] - Paulo Almeida (Kees Cook <keescook@...omium.org>)
2022/10/09 #1: [Self-introduction] - Paulo Almeida (Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@...il.com>)
2022/07/27 #5: Re: [PATCH] Introduce the pkill_on_warn boot parameter (Alexey Khoroshilov <khoroshilov@...ras.ru>)
2022/07/27 #4: Re: [PATCH] Introduce the pkill_on_warn boot parameter (Alexey Khoroshilov <khoroshilov@...ras.ru>)
2022/07/27 #3: Re: [PATCH] Introduce the pkill_on_warn boot parameter (Linus Torvalds <torvalds@...ux-foundation.org>)
2022/07/27 #2: Re: [PATCH] Introduce the pkill_on_warn boot parameter (Jann Horn <jannh@...gle.com>)
2022/07/27 #1: Re: [PATCH] Introduce the pkill_on_warn boot parameter (Alexey Khoroshilov <khoroshilov@...ras.ru>)
2022/06/29 #5: Re: [PATCH] stack: Declare {randomize_,}kstack_offset to fix Sparse warnings (Gong Ruiqi <gongruiqi1@...wei.com>)
2022/06/29 #4: Re: [PATCH v2] stack: Declare {randomize_,}kstack_offset to fix Sparse warnings (Christophe Leroy <christophe.leroy@...roup.eu>)
2022/06/29 #3: [PATCH v2] stack: Declare {randomize_,}kstack_offset to fix Sparse warnings ("GONG, Ruiqi" <gongruiqi1@...wei.com>)
2022/06/29 #2: Re: [PATCH] stack: Declare {randomize_,}kstack_offset to fix Sparse warnings (Christophe Leroy <christophe.leroy@...roup.eu>)
2022/06/29 #1: [PATCH] stack: Declare {randomize_,}kstack_offset to fix Sparse warnings ("GONG, Ruiqi" <gongruiqi1@...wei.com>)
2022/06/01 #2: Re: Possibility of merge of disable icotl TIOCSTI patch (Levente Polyak <levente@...entepolyak.net>)
2022/06/01 #1: Re: Possibility of merge of disable icotl TIOCSTI patch (Yann Droneaud <ydroneaud@...eya.com>)
2022/05/18 #1: [ANNOUNCE][CFP] Linux Security Summit Europe 2022 ("Reshetova, Elena" <elena.reshetova@...el.com>)
2022/05/09 #1: Re: [PATCH] Decouple slub_debug= from no_hash_pointers again (Stephen Boyd <swboyd@...omium.org>)
2022/05/08 #1: [PATCH] Decouple slub_debug= from no_hash_pointers again (Peter Gerber <peter@...itrary.ch>)
2022/04/13 #1: Re: Kernel Self Protection Project: slub_debug=ZF (Kees Cook <keescook@...omium.org>)
2022/04/10 #1: Kernel Self Protection Project: slub_debug=ZF (Peter Gerber <peter@...tirary.ch>)
2022/03/26 #1: Re: OOB accesses in ax88179_rx_fixup() (in USB network card driver) - variants (Marcin Kozlowski <marcinguy@...il.com>)
2022/03/24 #3: Re: Large post detailing recent Linux RNG improvements ("Jason A. Donenfeld" <Jason@...c4.com>)
2022/03/24 #2: Re: Large post detailing recent Linux RNG improvements (Sandy Harris <sandyinchina@...il.com>)
2022/03/24 #1: Re: Large post detailing recent Linux RNG improvements (Sandy Harris <sandyinchina@...il.com>)
2022/03/21 #1: OOB accesses in ax88179_rx_fixup() (in USB network card driver) - variants (Marcin Kozlowski <marcinguy@...il.com>)
2022/03/19 #1: CVE Proofs of Concept (Derrick McKee <derrick.mckee@...il.com>)
2022/03/18 #2: Re: [ANNOUNCE][CFP] Linux Security Summit North America 2022 (James Morris <jmorris@...ei.org>)
2022/03/18 #1: Large post detailing recent Linux RNG improvements ("Jason A. Donenfeld" <Jason@...c4.com>)
2022/03/09 #1: Re: [PATCH] powerpc/32: Stop printing the virtual memory layout (Christophe Leroy <christophe.leroy@...roup.eu>)
2022/02/07 #1: [ANNOUNCE][CFP] Linux Security Summit North America 2022 (James Morris <jmorris@...ei.org>)
2022/02/06 #1: Re: [PATCH] Add ability to disallow idmapped mounts (Christian Brauner <brauner@...nel.org>)
2022/02/05 #2: Re: [PATCH] Add ability to disallow idmapped mounts (James Bottomley <James.Bottomley@...senPartnership.com>)
2022/02/05 #1: Re: [PATCH] Add ability to disallow idmapped mounts ("Anton V. Boyarshinov" <boyarsh@...linux.org>)
2022/02/04 #4: Re: [PATCH] Add ability to disallow idmapped mounts (Christian Brauner <brauner@...nel.org>)
2022/02/04 #3: Re: [PATCH] Add ability to disallow idmapped mounts ("Anton V. Boyarshinov" <boyarsh@...linux.org>)
2022/02/04 #2: Re: [PATCH] Add ability to disallow idmapped mounts (Christian Brauner <brauner@...nel.org>)
2022/02/04 #1: [PATCH] Add ability to disallow idmapped mounts ("Anton V. Boyarshinov" <boyarsh@...linux.org>)
2022/01/14 #3: Re: [PATCH v3 1/3] x86: Implement arch_prctl(ARCH_VSYSCALL_CONTROL) to disable vsyscall (Florian Weimer <fweimer@...hat.com>)

21638 messages

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.