Searched hist:"037 c8489ade669e0f09ad40d5b91e5e1159a14b1" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/nvdimm/ |
| H A D | security.c | diff 037c8489ade669e0f09ad40d5b91e5e1159a14b1 Wed Mar 27 13:10:44 CDT 2019 Dave Jiang <dave.jiang@intel.com> libnvdimm/security: provide fix for secure-erase to use zero-key
Add a zero key in order to standardize hardware that want a key of 0's to
be passed. Some platforms defaults to a zero-key with security enabled
rather than allow the OS to enable the security. The zero key would allow
us to manage those platform as well. This also adds a fix to secure erase
so it can use the zero key to do crypto erase. Some other security commands
already use zero keys. This introduces a standard zero-key to allow
unification of semantics cross nvdimm security commands.
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| /openbmc/linux/tools/testing/nvdimm/test/ |
| H A D | nfit.c | diff 037c8489ade669e0f09ad40d5b91e5e1159a14b1 Wed Mar 27 13:10:44 CDT 2019 Dave Jiang <dave.jiang@intel.com> libnvdimm/security: provide fix for secure-erase to use zero-key
Add a zero key in order to standardize hardware that want a key of 0's to
be passed. Some platforms defaults to a zero-key with security enabled
rather than allow the OS to enable the security. The zero key would allow
us to manage those platform as well. This also adds a fix to secure erase
so it can use the zero key to do crypto erase. Some other security commands
already use zero keys. This introduces a standard zero-key to allow
unification of semantics cross nvdimm security commands.
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|