Re: Django db backend not FIPS compliant

All, I have submitted a ticket where i propose the use of the "usedforsecurity=False" flag. Please take a look and comment if you have any thoughts. https://code.djangoproject.com/ticket/28401 On Sunday, July 16, 2017 at 11:22:45 AM UTC-4, Andrew DiPrinzio wrote: > > I am having the same pr

Re: Django db backend not FIPS compliant

I am having the same problem. Anyone have a solution other than patch hashlib? On Wednesday, May 31, 2017 at 9:36:20 AM UTC-4, Tim Graham wrote: > > django-developers discussion: > https://groups.google.com/d/msg/django-developers/dlUIPzQgnpM/Mtl7CQbPAQAJ > > On Tuesday, May 30, 2017 at 5:06:23

Re: Django db backend not FIPS compliant

django-developers discussion: https://groups.google.com/d/msg/django-developers/dlUIPzQgnpM/Mtl7CQbPAQAJ On Tuesday, May 30, 2017 at 5:06:23 PM UTC-4, Tim Graham wrote: > > This usage generates a short, unique identifier for a database index name. > The usage of md5 here isn't security sensitiv

Re: Django db backend not FIPS compliant

This usage generates a short, unique identifier for a database index name. The usage of md5 here isn't security sensitive. Changing it to some other hash could be backwards incompatible because Django would no longer know the names of indexes in existing projects. There are other usages of md5 i