New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add SHA256/384/512 to lib #41582
Comments
According to Anyway, there are various free implementations of the I think it's reasonable to put these all into the Note that sha512 and sha384 are the same algorithm, |
Logged In: YES This is, of course, an RFE -- request for enhancement -- and If you really want this to happen, I suspect you know the |
Logged In: YES
|
Logged In: YES Oops, correction to previous, US court ruling was from 9th |
Logged In: YES Addendum: Note that this RFE is an enhancement request for I don't think any harm will be done if this stays open for a |
Logged In: YES Yes, feature request = RFE. However, this somehow got into My FYI legal issue summary was based on a PyDev thread Yes, Sha module should be maintained by one person. Hope There is also a current PyDev thread about sha?, md5, ssl, |
Logged In: YES I couldn't find the "Contributions" section of Python.org; I did find PEP-241 says public domain is a legitimate choice I think the Linuxjournal article you refer to might be This tracker item clearly says "Feature request" in the |
Logged In: YES Here is the top of this page: I found the explanation: on When you click Bugs, Feature Request shows up under Yes, that is the lawyer and article. Yes, I noticed the Contributor agreements: your link is to a 3 1/2 year old |
Logged In: YES Addition to the previous: current does not necessarily mean |
Logged In: YES Well, I don't see an obvious way to reclassify this item. I sent an email to the lawyer and haven't gotten a response |
Logged In: YES Ok, next time.... |
Logged In: YES "Break" is a bit of an over-statement. |
Logged In: YES This should be addressed by the addition of the hashlib |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: