litellm - 💡(How to fix) Fix FIPS compliance of hash algo scrypt [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#27284Fetched 2026-05-07 03:33:23
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
RAW_BUFFERClick to expand / collapse

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

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING