[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Larry Hastings added the comment: I should clarify, I don't speak for 2.7. The rules there are a little different and it's up to Benjamin to decide. But please don't add new features to 3.4 and 3.5. -- ___ Python tracker

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

STINNER Victor added the comment: I agree with Larry. If this feature is super useful, we can consider adding it to stable versions later. -- ___ Python tracker ___ _

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Larry Hastings added the comment: Describing this as a "security sensitive issue" is being facile. It's more appropriate to describe this as a "new feature", aka, something that does not go in after x.y.0 final. Please only check this in to "default", aka 3.6. -- ___

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Jesús Cea Avión added the comment: SHA-3 is released. http://www.nist.gov/manuscript-publication-search.cfm?pub_id=919061 Should we add it to Python 2.7.11, 3.4.4, 3.5.1 or just for 18 months away Python 3.6?. Since this is a security sensitive issue, I would vote for adding it to the maintai

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Roundup Robot added the comment: New changeset 21257f916668 by Ned Deily in branch '3.4': Issue #16113: Also remove test_case_sha3_224_huge https://hg.python.org/cpython/rev/21257f916668 New changeset bd97eab25c70 by Ned Deily in branch 'default': Issue #16113: Also remove test_case_sha3_224_hug

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Martin v. Löwis added the comment: Thanks for the report. Restored in 8a3718f31188 -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

STINNER Victor added the comment: @Martin: It looks like the _overlapped module is not more compiled on Windows. http://buildbot.python.org/all/builders/x86%20Windows%20Server%202008%20%5BSB%5D%203.x/builds/2032/steps/test/logs/stdio test test_asyncio crashed -- Traceback (most recent call last

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Martin v. Löwis added the comment: I have now removed the aha code. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Roundup Robot added the comment: New changeset 52350d325b41 by Martin v. Löwis in branch 'default': * Issue #16113: Remove sha3 module again. http://hg.python.org/cpython/rev/52350d325b41 -- ___ Python tracker

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Martin v. Löwis added the comment: I just looked at the hash-forum archives (*) http://cio.nist.gov/esd/emaildir/lists/hash-forum/msg02809.html which says that they plan to publish the draft "soon after Christmas". They also indicate how the padding open issue might get resolved (append f

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Gregory P. Smith added the comment: Given the likely delay in the standard Martin cites, I've change my mind: agreed. Go ahead and remove it for 3.4. We'll have an official sha3 in Python 3.5. Early adopters can live with PyPI. -- ___ Python track

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

STINNER Victor added the comment: OpenSSL doesn't implement SHA-3 yet, it's strange to have SHA-3 in Python but not in OpenSSL. If the standard is still a draft, I agree to remove the code right now. -- ___ Python tracker

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Antoine Pitrou added the comment: I agree with Martin that it should be removed right now. It's not really reasonable to call something SHA-3 if it's not SHA-3, even in beta versions. -- ___ Python tracker ___

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Martin v. Löwis added the comment: Ok, this this remains a release blocker. I'm still +1 for removing it, and I'm -0 for removing it just before the release candidate. AFAICT, there is *zero* (.1) chance that it actually becomes a NIST standard before the Python release is made. Accord

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Christian Heimes added the comment: I have created a backport of the sha3 for Python 2.6 to 3.3 about an year ago. It's on PyPI: https://pypi.python.org/pypi/pysha3 . I'm planing to update the code with SHAKE256 and SHAKE512 support soonish, too. I have very high confidence that NIST is neithe

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Gregory P. Smith added the comment: I would not bother pulling this out until the week before RC1 if the standard has not yet been declared final. Otherwise, -1 on keeping it under another name. The only hashes we bundle should be standard ones as those are the only ones people will want to u

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Antoine Pitrou added the comment: Either that, or we call it something else than "sha3"? -- ___ Python tracker ___ ___ Python-bugs-lis

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

STINNER Victor added the comment: Will it be possible/easy to maintain a sha3 module on PyPI? It would be nice to have to for Python 2.6-3.4. @Christian: Are you interested to do that? -- nosy: +haypo ___ Python tracker

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Martin v. Löwis added the comment: I'm going to remove sha3 from the trunk tomorrow unless I hear otherwise. Python shouldn't implement something called "sha3" until SHA-3 actually is a standard. According to the current NIST timeline, the comment period on the draft FIPS should have ended by

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Christian Heimes added the comment: New information on NIST's hash forum strongly suggest that NIST is going to standardize SHA-3 according to the original proposal with c=2n and Sakura padding as well as two SHAKEs with variable length output. SHA3-224 with c=448 SHA3-256 with c=512 SHA3-384

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Changes by Michele Orrù : -- nosy: -maker ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Mark Lawrence added the comment: This strikes me as a rather unusual case. How about discuss it on python-dev, come to an agreement and document the process for this type of issue somewhere for future reference? Or is that simply OTT? -- nosy: +BreamoreBoy __

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Antoine Pitrou added the comment: > I'm prepared to pull the plug if there is any doubt about the final version > of SHA-3 before beta 2 is released on Jan 5th. Shouldn't it be removed before beta1? The usual rule of feature freeze applies here. -- ___

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Changes by Tim Peters : -- priority: normal -> release blocker title: Add SHA-3 (Keccak) support -> SHA-3 (Keccak) support may need to be removed before 3.4 ___ Python tracker _