As Brian mentioned, the problem is with some older storage arrays that are supported by the driver but require MD5 hashes as part of their authentication handshake. These arrays reached end-of-support this year so they won't be getting firmware updates to fix this.
I would not want to unilaterally drop support for these older arrays from the driver--the weakness in MD5 is not a problem here--but I think it would be fine to publish a release note advising that they are deprecated and will be dropped in a future release to see if we get any feedback.
As Brian mentioned, the problem is with some older storage arrays that are supported by the driver but require MD5 hashes as part of their authentication handshake. These arrays reached end-of-support this year so they won't be getting firmware updates to fix this.
I would not want to unilaterally drop support for these older arrays from the driver--the weakness in MD5 is not a problem here--but I think it would be fine to publish a release note advising that they are deprecated and will be dropped in a future release to see if we get any feedback.
Brian, is there a formal policy to guide us here?
Chris