News for hackers. Stuff that matters.
Re:Launching in 2015: A Certificate Authority to Encrypt the... by dragonwriter on Tuesday November 18, 2014 @05:03PM (#8626665)
> Tell me how the logic works here (for an average user).

"Neutral Chrome" is the default state of the web -- the site doesn't assert that it should be trusted, and it shouldn't be, and that's the default state people should have in approaching the web.

"Cool Green" is "the site asserts that it has a particular identity and that communication with that identified site is private, and it passes the tests built into the browser's security model to verify all that."

"Evil Red" is "the site asserts that it has a particular identity and that communication with that identified site is private, but it fails the tests built into the browser's security model to verify all that."

Seems to me to be perfectly logical, even if we might prefer a better security model for making and verifying the claims at issue.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by sarciszewski on Tuesday November 18, 2014 @08:16PM (#8627595)
Plaintext is zero security.

Self-signed is a low probability of security.

Signed is a high probability of security.

This continuum makes more sense than the current state of affairs.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by pestaa on Wednesday November 19, 2014 @03:42AM (#8628909)
If someone forwards plaintext, it's called a proxy.

If someone forwards encrypted content on behalf of my server, it's called man-in-the-middle attack, and they should not be capable of doing it without the huge red flags.

Re:Launching in 2015: A Certificate Authority to Encrypt the... by vsl on Wednesday November 19, 2014 @05:32AM (#8629215)
Self-signed is a significant probability of man-in-the-middle attack.