### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

I am trying to revive the discussion on [this](https://github.com/BerriAI/litellm/issues/16789) feature request that is closed as stale. From [this](https://github.com/BerriAI/litellm/issues/16789#issuecomment-3549996032) comment my understading was this feature may be considered. Was the decision made not to consider this requirement. Thank you.

Original feature request:

LiteLLM proxy is using pynacl which is bound to libsodium library, which is not FIPS certified, so pynacl is not FIPS compliant. This prevents LiteLLM proxy from being used in environment that needs to be certified for FIPS compliance.

This feature request is to use FIPS certified cryptography module. Thank you.

### Motivation, pitch

I am trying to use LiteLLM proxy in a FIPS compliant environment and I cannot adopt LiteLLM proxy as pynacl is not FIPS certified. This issue will prevent adoption of LiteLLM proxy in all the environment that requires FIPS compliance.

### What part of LiteLLM is this about?

Proxy

### LiteLLM is hiring a founding backend engineer, are you int…