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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 7 Jan 2020 08:50:50 +0000
From:   "Kim, David" <david.kim@...pher.com>
To:     Greg KH <gregkh@...uxfoundation.org>
CC:     "arnd@...db.de" <arnd@...db.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Magee, Tim" <tim.magee@...pher.com>
Subject: RE: [PATCH v2] drivers: misc: Add support for nCipher HSM devices


> >
> > This is the driver for nCipher’s Solo and Solo XC hardware security modules.
> > These modules implement a proprietary command set (the ’nCore API’) to
> > perform cryptographic operations - key generation, signature, and so
> > on. HSM commands and their replies are passed in a serialised binary
> > format over the PCIe bus via a shared memory region. Multiple commands
> > may be in-flight at any one time - command processing is
> > multi-threaded and asynchronous. A write operation may, therefore,
> > deliver multiple commands, and multiple replies may be retrieved in one
> read operation.
> 
> If this is "just" a crypto accelerator, why isn't this driver using the existing in-
> kernel hardware crypto api?  What is lacking from it that you need here?

Hi Greg,

A cryptographic accelerator uses key material which is stored on, and managed by, the host machine. Hardware security modules, such as nCipher’s Solo products, retain key material (i.e. secrets) within the secure boundary of the device, and implement various forms of access control to restrict use of that key material.

nCipher's product range started, in the early 1990s, as cryptographic accelerators.  The series of hardware security modules served by this driver still does do cryptography but their main function is the generation, management and use of keys within a secure boundary.

The driver doesn't do any cryptography. It provides the link between the userspace software and the HSM's firmware. Cryptography is done within the HSM's secure boundary.

Regards
Dave

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ