From: David Howells <dhowells@redhat.com> To: Dave Jiang <dave.jiang@intel.com> Cc: alison.schofield@intel.com, keescook@chromium.org, linux-nvdimm@lists.01.org, ebiggers3@gmail.com, dhowells@redhat.com, keyrings@vger.kernel.org Subject: Re: [PATCH v8 02/12] libnvdimm: create keyring to store security keys Date: Mon, 24 Sep 2018 22:02:12 +0100 [thread overview] Message-ID: <29481.1537822932@warthog.procyon.org.uk> (raw) In-Reply-To: <153549644916.4089.12258485183075906901.stgit@djiang5-desk3.ch.intel.com> Dave Jiang <dave.jiang@intel.com> wrote: > + GLOBAL_ROOT_UID, GLOBAL_ROOT_GID, &init_cred, Hmmm... I wonder if current_cred() would suffice since you must be called from something that has the ability to load modules. Further, I wonder if module loading should be wrapped in an override with init_cred in the core. > + (KEY_USR_ALL & ~KEY_USR_SETATTR), Did you really want to give the user write access, btw? David _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com> To: Dave Jiang <dave.jiang@intel.com> Cc: alison.schofield@intel.com, keescook@chromium.org, linux-nvdimm@lists.01.org, ebiggers3@gmail.com, dhowells@redhat.com, keyrings@vger.kernel.org Subject: Re: [PATCH v8 02/12] libnvdimm: create keyring to store security keys Date: Mon, 24 Sep 2018 21:02:12 +0000 [thread overview] Message-ID: <29481.1537822932@warthog.procyon.org.uk> (raw) In-Reply-To: <153549644916.4089.12258485183075906901.stgit@djiang5-desk3.ch.intel.com> Dave Jiang <dave.jiang@intel.com> wrote: > + GLOBAL_ROOT_UID, GLOBAL_ROOT_GID, &init_cred, Hmmm... I wonder if current_cred() would suffice since you must be called from something that has the ability to load modules. Further, I wonder if module loading should be wrapped in an override with init_cred in the core. > + (KEY_USR_ALL & ~KEY_USR_SETATTR), Did you really want to give the user write access, btw? David
next prev parent reply other threads:[~2018-09-24 21:02 UTC|newest] Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-08-28 22:47 [PATCH v8 00/12] Adding security support for nvdimm Dave Jiang 2018-08-28 22:47 ` Dave Jiang 2018-08-28 22:47 ` [PATCH v8 01/12] nfit: add support for Intel DSM 1.7 commands Dave Jiang 2018-08-28 22:47 ` Dave Jiang 2018-08-28 22:47 ` [PATCH v8 02/12] libnvdimm: create keyring to store security keys Dave Jiang 2018-08-28 22:47 ` Dave Jiang 2018-09-22 0:19 ` Dan Williams 2018-09-22 0:19 ` Dan Williams 2018-09-24 21:04 ` David Howells 2018-09-24 21:04 ` David Howells 2018-09-24 21:12 ` Dave Jiang 2018-09-24 21:12 ` Dave Jiang 2018-08-28 22:47 ` [PATCH v8 03/12] nfit/libnvdimm: store dimm id as a member to struct nvdimm Dave Jiang 2018-08-28 22:47 ` Dave Jiang 2018-08-28 22:47 ` [PATCH v8 04/12] keys: export lookup_user_key to external users Dave Jiang 2018-08-28 22:47 ` Dave Jiang 2018-09-21 21:59 ` Dan Williams 2018-09-21 21:59 ` Dan Williams 2018-09-21 22:02 ` Dave Jiang 2018-09-21 22:02 ` Dave Jiang 2018-09-21 23:05 ` David Howells 2018-09-21 23:05 ` David Howells 2018-08-28 22:47 ` [PATCH v8 05/12] nfit/libnvdimm: add unlock of nvdimm support for Intel DIMMs Dave Jiang 2018-08-28 22:47 ` Dave Jiang 2018-09-23 0:10 ` Dan Williams 2018-09-23 0:10 ` Dan Williams 2018-08-28 22:47 ` [PATCH v8 06/12] nfit/libnvdimm: add set passphrase support for Intel nvdimms Dave Jiang 2018-08-28 22:47 ` [PATCH v8 07/12] nfit/libnvdimm: add disable passphrase support to Intel nvdimm Dave Jiang 2018-08-28 22:47 ` Dave Jiang 2018-08-28 22:48 ` [PATCH v8 08/12] nfit/libnvdimm: add freeze security " Dave Jiang 2018-08-28 22:48 ` Dave Jiang 2018-08-28 22:48 ` [PATCH v8 09/12] nfit/libnvdimm: add support for issue secure erase DSM " Dave Jiang 2018-08-28 22:48 ` Dave Jiang 2018-08-28 22:48 ` [PATCH v8 10/12] nfit_test: add context to dimm_dev for nfit_test Dave Jiang 2018-08-28 22:48 ` Dave Jiang 2018-08-28 22:48 ` [PATCH v8 11/12] nfit_test: add test support for Intel nvdimm security DSMs Dave Jiang 2018-08-28 22:48 ` Dave Jiang 2018-08-28 22:48 ` [PATCH v8 12/12] libnvdimm: add documentation for nvdimm security support Dave Jiang 2018-08-28 22:48 ` Dave Jiang 2018-09-21 23:07 ` [PATCH v8 02/12] libnvdimm: create keyring to store security keys David Howells 2018-09-21 23:07 ` David Howells 2018-09-21 23:20 ` [PATCH v8 05/12] nfit/libnvdimm: add unlock of nvdimm support for Intel DIMMs David Howells 2018-09-21 23:20 ` David Howells 2018-09-21 23:27 ` Dave Jiang 2018-09-21 23:27 ` Dave Jiang 2018-09-21 23:51 ` Dan Williams 2018-09-21 23:51 ` Dan Williams 2018-09-21 23:57 ` [PATCH v8 06/12] nfit/libnvdimm: add set passphrase support for Intel nvdimms David Howells 2018-09-21 23:57 ` David Howells 2018-09-22 0:25 ` Dave Jiang 2018-09-22 0:25 ` Dave Jiang 2018-09-22 1:26 ` Dan Williams 2018-09-22 1:26 ` Dan Williams 2018-09-22 0:01 ` [PATCH v8 04/12] keys: export lookup_user_key to external users David Howells 2018-09-22 0:01 ` David Howells 2018-09-24 21:02 ` David Howells [this message] 2018-09-24 21:02 ` [PATCH v8 02/12] libnvdimm: create keyring to store security keys David Howells 2018-09-24 21:15 ` Dave Jiang 2018-09-24 21:15 ` Dave Jiang
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=29481.1537822932@warthog.procyon.org.uk \ --to=dhowells@redhat.com \ --cc=alison.schofield@intel.com \ --cc=dave.jiang@intel.com \ --cc=ebiggers3@gmail.com \ --cc=keescook@chromium.org \ --cc=keyrings@vger.kernel.org \ --cc=linux-nvdimm@lists.01.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.