[
https://issues.apache.org/jira/browse/ZOOKEEPER-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290668#comment-17290668
]
Joh commented on ZOOKEEPER-3696:
--------------------------------
I’m lost maybe you can call me 214-850-9503 I am a victim of identity theft and
worried and should prob ask if I need to buy a new phone or something
On Feb 24, 2021, at 3:29 AM, Mate Szalay-Beko (Jira) <[email protected]> wrote:
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289806#comment-17289806
]
Mate Szalay-Beko commented on ZOOKEEPER-3696:
---------------------------------------------
sorry [~joeknowzU], I don't understand your question.
These are automatic messages about the closing of the pull request after
merging it, and also about resolving the Jira ticket.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
> Support alternative algorithms for ACL digest
> ---------------------------------------------
>
> Key: ZOOKEEPER-3696
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3696
> Project: ZooKeeper
> Issue Type: Task
> Components: security
> Reporter: Patrick D. Hunt
> Assignee: Ling Mao
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 3.7.0
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> DigestAuthenticationProvider is using SHA1 which is known to be broken, eg
> recently:
> https://shattered.io/
> https://sha-mbles.github.io/
> etc...
> We should mark DigestAuthenticationProvider as deprecated at a minimum,
> perhaps even just remove it asap. The docs should also reflect this (ie don't
> use)
> We could replace DigestAuthenticationProvider with
> DigestAuthenticationProvider3 or similar (use SHA3, not SHA2 if we do so) Or
> perhaps a version that allows the user to select? Regardless, would be good
> to give a simple option to the end user.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
