Robert Collins added the comment: A few thoughts;
usedforsecurity=xxx seems awkward: I wouldn't want, as a user of hashlib, to have to put that in literally every use I make of it. If I understand the situation correctly, the goal is for both linters, and at runtime, identification of the intended purpose of a call to md5 - e.g. whether there are security implications in its use (as far as FIPS is concerned). Perhaps having two separate implementations of the interfaces, one general purpose and one FIPS would be decent. e.g. from hashlib.fips import sha1 etc etc and hashlib.fips simply wouldn't contain md5. Then the md5 thats in hashlib is by definition not FIPS ready and any code using it should be fixed. ---------- nosy: +rbcollins _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9216> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
