6 views
-/https://github.com/berriai/litellm/issues/27284
GitHub · issue

#27284 FIPS compliance of hash algo scrypt

  • State: open
  • Author: @aayush-malviya-acquia

**Summary** - After the supply chain attack, among the security measures taken, one was to use scrypt for internal user password hashing. - In a FIPS-enforced environment, the underlying OpenSSL provider refuses to execute scrypt, causing internal-user creation and username/password login to fail at runtime with errors like: `ValueError: [digital envelope routines] unsupported`

**Affected Versions** - Latest releases, including v1.83.14-stable have this issue.

**Reproduction** - Run LiteLLM on FIPS enforced hosts. - The issue can be observed while onboarding new internal users, or logging in with existing internal users. - Admin login works without any issue.

**Expected Behavior** - LiteLLM should support a FIPS-compliant password hashing scheme so that the proxy can be deployed in FIPS-enforced environments without runtime errors.

**Proposed Solution** - Use `hashlib.pbkdf2_hmac` instead of `hashlib.scrypt`

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 · 31d18h40m24s ago — entered · #import:https:::github.com:berriai:litellm post #2209
The left issue is harder because it requires a security-sensitive hashing change, compatibility with existing credentials, migration or fallback behavior, and validation across FIPS and non-FIPS environments. The right issue is comparatively localized to usage-field translation and billing metadata tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search