FIPS cryptography compatible deployments

[shapiromatron]

Enable options to deploy application with FIPS mode enabled on RHEL8 (tldr; no md5 or insecure cryptographic hashing for security uses)

• Update webpack for fips compliance
• Add monkeypatch for django 3.2; this should be fixed with django 4.1 - details on monkeypatch

Bonus - add environment variables for "staging" environment settings

To enable:

export HAWC_FEATURE_FLAGS='{"FIPS_MODE":true}'

You should see a FIPS monkeypatch enabled... (using print b/c logging isn't enabled yet), when starting a dev server:

~/dev/hawc  fips ► source venv/bin/activate && manage runserver
FIPS monkeypatch enabled...
Performing system checks...
System check identified no issues (0 silenced).
September 01, 2022 - 23:15:45
Django version 3.2.15, using settings 'hawc.main.settings.dev'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

[rabstejnek]

Looks good! For some reason it's being applied twice on my dev environment, but judging from the code it shouldn't cause any problems.

[shapiromatron]

Looks good! For some reason it's being applied twice on my dev environment, but judging from the code it shouldn't cause any problems.

Good find; that looks like can occur with django runserver. https://stackoverflow.com/questions/33814615/

I fixed with an enviro variable, which only persists for this processes runtime environment.