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
| ||
|
Date: Thu, 25 Aug 2022 11:19:14 +0200 From: Roberto Sassu <roberto.sassu@...weicloud.com> To: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org, martin.lau@...ux.dev, song@...nel.org, yhs@...com, john.fastabend@...il.com, kpsingh@...nel.org, sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org, mykolal@...com, corbet@....net, dhowells@...hat.com, jarkko@...nel.org, rostedt@...dmis.org, mingo@...hat.com, paul@...l-moore.com, jmorris@...ei.org, serge@...lyn.com, shuah@...nel.org Cc: bpf@...r.kernel.org, linux-doc@...r.kernel.org, keyrings@...r.kernel.org, linux-security-module@...r.kernel.org, linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org, deso@...teo.net, Roberto Sassu <roberto.sassu@...wei.com> Subject: Re: [PATCH v13 00/10] bpf: Add kfuncs for PKCS#7 signature verification On Tue, 2022-08-23 at 17:00 +0200, Roberto Sassu wrote: > From: Roberto Sassu <roberto.sassu@...wei.com> > > One of the desirable features in security is the ability to restrict > import > of data to a given system based on data authenticity. If data import > can be > restricted, it would be possible to enforce a system-wide policy > based on > the signing keys the system owner trusts. Hi is there anything else I need to do, other than rebasing the patches to the latest eBPF code? Thanks Roberto
Powered by blists - more mailing lists