Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
None
-
Any system using GSS and a linux kernel 4.6 and above.
-
9223372036854775807
Description
Currently the GSS code for Lustre directly uses the linux crypto API. This code uses struct crypto_hash which has now been removed in newer kernels for struct crypto_ahash. Libcfs crypto API has moved to this new kernel API but it doesn't have support for the algos that GSS wants to use. So the first question to ask is does GSS move to libcfs crypto API and we expand support in the libcfs crypto API to AES and DEC or do we ignore libcfs crypto API and just use the linux crypto api directly and use the newer ahash api.
Attachments
Issue Links
- is related to
-
LU-9073 SSK: lgss_sk generates keys with invalid HMAC and Crypto algorithms
- Resolved
-
LU-9245 lgss_sk may unsafely overwrite nodemap and fsname fields in keys
- Resolved
-
LU-9430 logic errors in lgss_sk code
- Resolved
- is related to
-
LU-9795 SSK test failures in many suites when SHARED_KEY is enabled
- Reopened
-
LU-11635 GSS build for client-only
- Resolved
-
LU-3289 IU Shared Secret Key authentication and encryption
- Resolved
-
LU-8560 Support for linux 4.6 kernels
- Resolved