Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-21051

Set proper permissions on SSK keys

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Medium Medium
    • Lustre 2.18.0
    • Lustre 2.18.0
    • 3
    • 9223372036854775807

      When an SSK key is loaded into the keyring, either with lgss_sk -l or through the skpath mount option, sk_load_key() explicitly sets permissions on the new key. The client mount does the same when it renames the key per client in gss_rename_sk_key(). The mask used today is broader than what the SSK code needs.

      SSK keys are owned by root, and every consumer of them runs as root:

      • the lgss_keyring upcall for SSK contexts, which are root-only
      • lsvcgssd
      • lgss_sk
      • the client mount

      User permissions are therefore enough. The permissions set on these keys should be reduced to just those.

            sebastien Sebastien Buisson
            sebastien Sebastien Buisson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: