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 7:12:50 PM UTC-4, Andrew DiPrinzio wrote:
>
> I am having the same
I am having the same problem. Anyone have a solution other than patch
hashlib?
On Wednesday, May 31, 2017 at 4:08:54 PM UTC-4, Adam Johnson wrote:
>
> After googling a bit I found this CPython ticket:
> https://bugs.python.org/issue9216 . It turns out that the block is in
> OpenSSL and not
After googling a bit I found this CPython ticket:
https://bugs.python.org/issue9216 . It turns out that the block is in
OpenSSL and not really python land. They didn't find a solution to it in
the standard library on that ticket, but I think it should be pretty easy
to monkey patch in a pure
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'm running into issues when trying to migrate my models in an environment
that is running FIPS restrictions regarding MD5. Here is the stack trace:
Operations to perform:
> Apply all migrations: admin, auth, contenttypes, dashboard,
> kombu_transport_django, sessions
> Running migrations:
>
