Skip to content

[Feat]: FIPS approved crypto #3445

Description

@TylerGillson

Is your feature request related to a problem? Please describe.

Deploying zot with GODEBUG=fips140=only produces the following panic:

panic: crypto/sha1: use of SHA-1 is not allowed in FIPS 140-only mode

goroutine 1 [running]:
crypto/sha1.(*digest).checkSum(0xb0?)
    crypto/sha1/sha1.go:165 +0x17c
crypto/sha1.(*digest).Sum(0x40000d62a0, {0x0, 0x0, 0x0})
    crypto/sha1/sha1.go:159 +0x70
github.com/go-redsync/redsync/v4/redis.NewScript(0x1, {0xaaaae472a43d, 0xa1})
    github.com/go-redsync/redsync/v4@v4.13.0/redis/redis.go:43 +0x104
github.com/go-redsync/redsync/v4.init()
    github.com/go-redsync/redsync/v4@v4.13.0/mutex.go:234 +0x2c

Describe the solution you'd like

Explore alternatives to github.com/go-redsync/redsync/v4 or make upstream changes to said dependency.

Describe alternatives you've considered

Updating github.com/go-redsync/redsync/v4 directly. If you'd prefer, I'd be happy to open an issue there and close this one.

Additional context

go-redsync/redsync#194

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or requestrm-externalRoadmap item submitted by non-maintainers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions