Shared Secret Key Authentication And Encryption: Difference between revisions
Jump to navigation
Jump to search
KenRawlings (talk | contribs) (adding opensfs contract resources section) |
Elliswilson (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{| class='wikitable' | |||
|- | |||
!This page collects background and original design references for Shared-Secret Key (SSK) security. For current setup instructions, see [[Lustre Kerberos SSK Authentication]] and the ''Configuring Shared-Secret Key (SSK) Security'' chapter of the [https://doc.lustre.org/lustre_manual.xhtml Lustre Operations Manual]. | |||
|} | |||
=== Introduction === | === Introduction === | ||
Shared Key offers | Shared Key, added in Lustre 2.9 ([https://jira.whamcloud.com/browse/LU-3289 LU-3289]), offers: | ||
* Isolation | * Isolation (all SSK flavors) | ||
** Prevents clients from mounting without the shared key | ** Prevents clients from mounting without the shared key | ||
** | ** Binds a key to a nodemap, so it is accepted only from that nodemap's NID ranges (with [[UID/GID_Mapping|UID/GID Mapping]]) | ||
* Message Integrity | * Message Integrity (<code>ska</code>, <code>ski</code>, <code>skpi</code>) | ||
** Prevents man-in-the-middle attacks | ** Prevents man-in-the-middle attacks | ||
** | ** Ensures RPCs cannot be altered without detection. <code>ska</code> covers only non-bulk RPCs; <code>ski</code> and <code>skpi</code> also cover bulk data. | ||
* Privacy | * Privacy (<code>skpi</code> only) | ||
** Prevents eavesdropping | ** Prevents eavesdropping | ||
** | ** Encrypts RPCs and bulk data | ||
* Ability to choose security flavors between OSS, MDS, MGS, and client nodes, as site policy dictates | * Ability to choose security flavors between OSS, MDS, MGS, and client nodes, as site policy dictates | ||
== Resources == | == Resources == | ||
* [https://jira. | * [https://jira.whamcloud.com/browse/LU-3289 IU Shared Secret Key authentication and encryption (LU-3289)] | ||
* | * The original OpenSFS Contract SFS-DEV-002 design documents (Shared Key Scope, Architecture, High Level Design, RPC Diagram, and Kerberos Setup Guide) were previously hosted on wiki.opensfs.org but are no longer available online. | ||
* For current setup instructions, see [[Lustre Kerberos SSK Authentication]]. For the reference, see the ''Configuring Shared-Secret Key (SSK) Security'' chapter of the [https://doc.lustre.org/lustre_manual.xhtml Lustre Operations Manual]. | |||
* | |||
== Presentations == | == Presentations == | ||
| Line 31: | Line 32: | ||
[[Category:Features]] | [[Category:Features]] | ||
[[Category:Security]] | |||
Latest revision as of 08:13, 12 October 2026
| This page collects background and original design references for Shared-Secret Key (SSK) security. For current setup instructions, see Lustre Kerberos SSK Authentication and the Configuring Shared-Secret Key (SSK) Security chapter of the Lustre Operations Manual. |
|---|
Introduction
Shared Key, added in Lustre 2.9 (LU-3289), offers:
- Isolation (all SSK flavors)
- Prevents clients from mounting without the shared key
- Binds a key to a nodemap, so it is accepted only from that nodemap's NID ranges (with UID/GID Mapping)
- Message Integrity (
ska,ski,skpi)- Prevents man-in-the-middle attacks
- Ensures RPCs cannot be altered without detection.
skacovers only non-bulk RPCs;skiandskpialso cover bulk data.
- Privacy (
skpionly)- Prevents eavesdropping
- Encrypts RPCs and bulk data
- Ability to choose security flavors between OSS, MDS, MGS, and client nodes, as site policy dictates
Resources
- IU Shared Secret Key authentication and encryption (LU-3289)
- The original OpenSFS Contract SFS-DEV-002 design documents (Shared Key Scope, Architecture, High Level Design, RPC Diagram, and Kerberos Setup Guide) were previously hosted on wiki.opensfs.org but are no longer available online.
- For current setup instructions, see Lustre Kerberos SSK Authentication. For the reference, see the Configuring Shared-Secret Key (SSK) Security chapter of the Lustre Operations Manual.