[jira] [Commented] (ZOOKEEPER-3696) deprecate DigestAuthenticationProvider which uses broken SHA1

["Enrico Olivelli (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062490#comment-17062490 ] 

Enrico Olivelli commented on ZOOKEEPER-3696:
--------------------------------------------

[~phunt] are you going to work on this issue ?
I see you tagged it for 3.5.8, 3.6.1 and 3.7.0

I would go only for 3.7.0 and only if someone is interested in working on it

I think that this topic is important but we can't drop something on a point release.


> deprecate DigestAuthenticationProvider which uses broken SHA1
> -------------------------------------------------------------
>
>                 Key: ZOOKEEPER-3696
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3696
>             Project: ZooKeeper
>          Issue Type: Task
>          Components: security
>            Reporter: Patrick D. Hunt
>            Priority: Blocker
>             Fix For: 3.7.0, 3.6.1, 3.5.8
>
>
> 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)