News for hackers. Stuff that matters.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by tptacek on Wednesday December 02, 2015 @01:29PM (#10664803)
That's another arms race Chrome will lose, because the market for the kinds of enterprise configuration management and "host protection" tools that could override this policy exists and is very lucrative. Chrome would simply be begging enterprise security companies to release products to fuck up their browser.

I disagree with you.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by bcoates on Wednesday December 02, 2015 @02:04PM (#10665050)
Chrome already has an "enterprise" version, moving a less braindead corporate monitoring system then MITM certs into it would probably be a good thing.

It would also be a good way for them to start pushing a "two party consent" model for private wiretapping -- It's illegal for my employer to record my office phone because it's a violation of the other party's rights. Facebook has as much a stake in not letting employers monitor employee's social media use as the employees do.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by cwyers on Wednesday December 02, 2015 @01:43PM (#10664891)
Or someone just forks Chromium and releases Chromium For Enterprise.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by tptacek on Wednesday December 02, 2015 @01:54PM (#10664963)
Which again helps nobody, because forks of Chromium will inevitably lag on security fixes.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by kibwen on Wednesday December 02, 2015 @03:00PM (#10665411)
At my last job, my manager tasked me with finding a way to defeat Chrome's update mechanism for all of our employees because a new version had introduced a bug that broke our internal web applications. I disregarded his plan and just introduced a workaround for the bug, but the point remains that enterprise customers already consider it a value-add to freeze their software in time for perpetuity. Hell, my workstation was running XP until I needled IT to grant me a "premature" upgrade to Win 7.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by tptacek on Wednesday December 02, 2015 @03:11PM (#10665472)
Sorry, I meant that from the perspective of the Chromium team.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by kibwen on Wednesday December 02, 2015 @03:31PM (#10665581)
Indeed, I agree with the policy that if someone can control what's installed locally, they've already won.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by davidu on Wednesday December 02, 2015 @01:34PM (#10664837)
Part of me hopes you are right, because I don't like seeing Chrome/Google throw it's muscle around.

Part of me hopes you are wrong, because I think encryption and security don't need to be opposing forces and MITM isn't required for strong security (though maybe for good GRC and audit).

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by teacup50 on Wednesday December 02, 2015 @01:42PM (#10664885)
Key pinning you can't override locally is DRM.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by davidu on Thursday December 03, 2015 @09:36AM (#10669738)
That's a super interesting way of framing the conversation.