3 ms·
Awesome! Can we get a fix for Logjam yet? It was first reported on May 20 [0], presumably Google knew about it earlier (I know Firefox was given advance notice
by ikeboy 11y ago
Awesome!
Can we get a fix for Logjam yet? It was first reported on May 20 [0], presumably Google knew about it earlier (I know Firefox was given advance notice [1]), yet the latest stable releases of chrome on both mobile and desktop are still vulnerable.
Firefox fixed it on Jul 2 [2], Apple fixed it on June 30 [3]. Can someone explain to me why Google hasn't released a fix to something that affected 10% of popular websites on disclosure day [0]?
[0] https://weakdh.org/ https://weakdh.org/
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1138554 https://bugzilla.mozilla.org/show_bug.cgi?id=1138554
[2] https://www.mozilla.org/en-US/security/advisories/mfsa2015-70/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-7...
[3] https://support.apple.com/en-us/HT204941 https://support.apple.com/en-us/HT204941
- RobAtticus 11y ago[0] says I'm not vulnerable and I'm using Chrome 46 on Windows, so I guess it's on its way. (Chrome 44 on Android still vulnerable.)
- ikeboy 11y ago46 is not stable (the current stable release is 44, see http://googlechromereleases.blogspot.com/ http://googlechromereleases.blogspot.com/). Also, if you want Chrome Beta on android you can go here: https://play.google.com/store/apps/details?id=com.chrome.beta https://play.google.com/store/apps/details?id=com.chrome.bet...