disables MD5 on FIPS builds and adds WP_ALLOW_NON_FIPS flag

[BridgerVoss]

MD5 was getting enabled on FIPS builds which shouldn't be happening. Added WP_ALLOW_NON_FIPS flag to allow usage of DES3 or MD5 if they are enabled in the FIPS build.

[padelsbach]

Looks fine to me. Will let @ColtonWilley chime in

[ColtonWilley]

I am not so sure about this one. In general wolfProvider is not the one who determines algo support, it relies on the wolfssl includes to dictate which algos are enabled.

There are no other switches in settings.h on FIPS, despite many of those algos also not being included in the FIPS module. At a minimum it makes the code inconsistent, 3DES would also fall into this same category.

We should either not enforce, or enforce in a robust and consistent way. Let me think some more and consult with Kaleb on this.

[BridgerVoss]

I am not so sure about this one. In general wolfProvider is not the one who determines algo support, it relies on the wolfssl includes to dictate which algos are enabled.

There are no other switches in settings.h on FIPS, despite many of those algos also not being included in the FIPS module. At a minimum it makes the code inconsistent, 3DES would also fall into this same category.

We should either not enforce, or enforce in a robust and consistent way. Let me think some more and consult with Kaleb on this.

@ColtonWilley in the XXX-fips-test directory MD5 is enabled by default. Would updating this to disabled by default be better? 3DES is disabled by defualt here.

[BridgerVoss]

retest this please Jenkins