News for hackers. Stuff that matters.
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by thomasfoster96 on Friday February 27, 2015 @05:24AM (#9118117)
Once Let's Ecrypt [0] launches, I suppose most web developers won't have any more excuses not to use HTTPS. It'll be free, pretty easy and quick time wise, plus it'll give you an SEO boost.

Browser vendors are certainly doing the right thing by making http be marked as non-secure, and not implementing unencrypted http/2 and not allowing non-HTTPS access to powerful api are completely reasonable steps to take.

[0] https://letsencrypt.org

Re:Blink - Intent to deprecate: Insecure usage of powerful f... by psykovsky on Friday February 27, 2015 @05:44AM (#9118177)
If everybody gets an SEO boost, there is no boost. :)
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by solaris999 on Friday February 27, 2015 @06:14AM (#9118259)
If you want to be pessimistic about it, anyone who doesn't adopt will get an SEO drop
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by hucker on Friday February 27, 2015 @06:13AM (#9118250)
Well, then there's a SEO penalty for not using it...
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by Aldo_MX on Friday February 27, 2015 @06:48AM (#9118356)
Except that not everybody will do it since day 1
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by protomyth on Friday February 27, 2015 @12:16PM (#9119970)
What is the value proposition of a certificate from an automated provider? What is the verification? If someone wants to get a certificate for a domain that has ebay or paypal as part of the domain then spoofs those sites, will the automated provide flag this or are the users going to see the nice lock in their address bar? Why bother and not just allow all self signed certificates?
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by goodnights on Friday February 27, 2015 @12:25PM (#9120029)
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by protomyth on Friday February 27, 2015 @01:08PM (#9120296)
Ok, so how does that keep a site like paypall.com (or any example of a common off-by-one-letter domain) from getting a certificate?
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by Eridrus on Friday February 27, 2015 @02:23PM (#9120737)
Nothing currently stops paypall.com getting a certificate and the technology is not meant to do that.

EV-SSL is kind of meant to deal with that if you want to pay the fees.

But this seems more in line with a movement towards HTTPS by default and marking HTTP as insecure.

Re:Blink - Intent to deprecate: Insecure usage of powerful f... by protomyth on Friday February 27, 2015 @03:09PM (#9121023)
I'm pretty sure the certificate companies when doing their verification stop obvious attempts at scams.

So, all this is to get an encrypted connection?

Re:Blink - Intent to deprecate: Insecure usage of powerful f... by runeks on Saturday February 28, 2015 @06:39AM (#9123434)
> So, all this is to get an encrypted connection?

This strikes me as odd too.

What's the difference between an automated SSL certificate generator and just having the browser accept self-signed certificates?

openssl is also an automated SSL certificate generator, but it only produces self-signed certificates. So why not just accept self-signed certs?

Re:Blink - Intent to deprecate: Insecure usage of powerful f... by johnsoft on Saturday February 28, 2015 @09:16AM (#9123705)
The difference is in the certificate chain. One of the conditions for being a CA is verifying domain ownership before signing a certificate. In return for this, browsers will trust their cert. As long as a CA keeps this promise, they get to keep their cert and use it to sign certs for others. If they break this promise, their cert will be revoked and browsers will start showing warnings on sites that used them as a CA.

A green padlock indicates this additional level of trust, i.e. authenticity (verified through any method any trusted CA may choose), which a self-signed cert can't provide.

Re:Blink - Intent to deprecate: Insecure usage of powerful f... by RyanMcGreal on Friday February 27, 2015 @07:26AM (#9118455)
How will Let's Encrypt be different/better than a StartSSL Free certificate?
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by organsnyder on Friday February 27, 2015 @07:40AM (#9118499)
I used to use StartSSL, but abandoned it for a few reasons:

1. Their user interface is slow and clunky. Acquiring/renewing certificates is a PITA.

2. For organizations, they require both extended personal validation and organizational validation. In addition to being fairly expensive ($100 annually, each), they require you to send images of a bunch of sensitive personal documents (passport, credit card, etc.). While you can often slip by and get certs without them realizing you're getting them for an organization, once they've noticed and flagged your account, each cert requires manual review.

3. Their website hasn't been updated in a number of years. They do not give the impression of being a healthy company.

Re:Blink - Intent to deprecate: Insecure usage of powerful f... by icebraining on Friday February 27, 2015 @07:52AM (#9118552)
Free certificate revocations. StartSSL was crucified for charging $25 for revocations, and not waiving the fee during Heartbleed.
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by AlyssaRowan on Friday February 27, 2015 @08:02AM (#9118583)
This, 100%. They also plan to adopt Certificate Transparency, I believe. And it'll hopefully be trivial to set up, once the scripting is all finished.

No excuses, people. Give it a few years and we'll be seriously talking about turning http: off, or at least putting security warnings on it, denying cookies and scripting, etc.

You don't still use telnet, do you?

Re:Blink - Intent to deprecate: Insecure usage of powerful f... by thomasfoster96 on Friday February 27, 2015 @08:04AM (#9118588)
By the looks of the Github account, Let's Encrypt will let me programmatically get a certificate for free when I run non start in my node app, or easily set up HTTPS on my Apache web server, among other things. All for free with minimal work.
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by tlarkworthy on Friday February 27, 2015 @11:53AM (#9119845)
Its two commands for free static https hosting on Firebase

https://www.firebase.com/docs/hosting/command-line-tool.html

Re:Blink - Intent to deprecate: Insecure usage of powerful f... by r1ch on Friday February 27, 2015 @02:31PM (#9120783)
Until ad networks make a serious effort to enable https on their networks and CDNs, I can't run https on any of my sites. Mixed content security means no http ads and thus no revenue.
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by TazeTSchnitzel on Friday February 27, 2015 @06:45AM (#9118354)
What about HTTPS for local testing, though?
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by thomasfoster96 on Friday February 27, 2015 @06:54AM (#9118372)
Reading through the W3C draft linked to in the announcement, localhost over HTTP will be considered probably secure.
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by TazeTSchnitzel on Friday February 27, 2015 @07:01AM (#9118393)
Make sense: if you can run a web server, you don't need the browser's help to do a phishing attack.
Re:Blink - Intent to deprecate: Insecure usage of powerful f... by organsnyder on Friday February 27, 2015 @07:44AM (#9118519)
Not necessarily. Any user could run a web server on an unprivileged port. While this is a far-fetched scenario—it requires the attacker having access to a different user's account on the machine, but not the victim's (if they had access to the victim's account, they wouldn't need to take these measures)—it is possible.

The only solution is to restrict privileged status to privileged ports. However, that would also limit the usefulness of the exception, since dev servers usually run on unprivileged ports (that could be changed, of course).

Re:Blink - Intent to deprecate: Insecure usage of powerful f... by thomasfoster96 on Friday February 27, 2015 @08:01AM (#9118579)
I might suppose that web browser developers might be of the view that if someone has been able to run a web server on your computer (even under a different user account) and done so with malicious intentions, your security problems are beyond the control of a web browser. With that sort of access, the attacker might as well have made off with all of your HTTPS-only cookies and browser history, changed your DNS settings, etc.