6 ms·
Blink - Intent to deprecate: Insecure usage of powerful features
- thomasfoster96 12y agoOnce 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 https://letsencrypt.org
- psykovsky 12y agoIf everybody gets an SEO boost, there is no boost. :)
- hucker 12y agoWell, then there's a SEO penalty for not using it...
- solaris999 12y agoIf you want to be pessimistic about it, anyone who doesn't adopt will get an SEO drop
- Aldo_MX 12y agoExcept that not everybody will do it since day 1
- TazeTSchnitzel 12y agoWhat about HTTPS for local testing, though?
- thomasfoster96 12y agoReading through the W3C draft linked to in the announcement, localhost over HTTP will be considered probably secure.
- TazeTSchnitzel 12y agoMake sense: if you can run a web server, you don't need the browser's help to do a phishing attack.
- organsnyder 12y agoNot 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).
- thomasfoster96 12y agoI 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.
- RyanMcGreal 12y agoHow will Let's Encrypt be different/better than a StartSSL Free certificate?
- organsnyder 12y agoI 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.
- icebraining 12y agoFree certificate revocations. StartSSL was crucified for charging $25 for revocations, and not waiving the fee during Heartbleed.
- AlyssaRowan 12y agoThis, 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?
- thomasfoster96 12y agoBy 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.
- tlarkworthy 12y agoIts two commands for free static https hosting on Firebase https://www.firebase.com/docs/hosting/command-line-tool.html https://www.firebase.com/docs/hosting/command-line-tool.html
- protomyth 12y agoWhat 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?
- goodnights 12y agohttps://letsencrypt.org/howitworks/technology/ https://letsencrypt.org/howitworks/technology/
- protomyth 12y agoOk, 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?
- Eridrus 12y agoNothing 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.
- protomyth 12y agoI'm pretty sure the certificate companies when doing their verification stop obvious attempts at scams. So, all this is to get an encrypted connection?
- runeks 12y ago> 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?
- r1ch 12y agoUntil 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.
- jbb555 12y agoBasically they are destroying the simplicity of the internet in order to push their own agenda. I'd get annoyed about it, but it's not going to be long before it all collapses under it's own weight and something new and lightweight turns up to take over from what http used to be good for.
- fpgeek 12y agoDid you even look at the kinds of attacks that motivate these restrictions before concluding that there was a nefarious agenda at work? I took a look at a Fullscreen API attack ( http://feross.org/html5-fullscreen-api-attack/ http://feross.org/html5-fullscreen-api-attack/ ) and found it pretty creepy even though I knew exactly what to expect and what to look for. Tighter controls over that sort of thing seem like a great idea to me.
- ldng 12y agoMaybe I'm dense but I don't see how requiring HTTPS would solve phishing attacks. To me it falls in the social engineering realm, people clicking link in their mail thay really should not. Having an extra 's' in the URL will not change that. Am I missing the point ?
- TazeTSchnitzel 12y ago1) You need to have been approved by a CA to get a TLS certificate 2) If HTTPS is required, MITMing can't be used to take advantage of permissions you've granted to existing sites
- ldng 12y ago1) Expensive for no good reason for 80% of sites out there 2) We agree it is useful in some case. That what makes it hard to go against, because it seems a reasonable objective. The problem is where do you put the limit. I don't "fullscreen" my bank account. To me, forbidding fullscreen on HTTP is quite over the top but fits Google agenda of HTTPSing All The Things.
- hayksaakian 12y agoI wonder how many "internet of things" things will stop working due to these changes.
- sleepychu 12y agoAren't IOT typically servers not clients? I can't imagine their pages require access to powerful APIs.
- revelation 12y agoThe word has been mangled to the point of no recognition, but for low power applications you would want the IOT device to be a client pushing when changes occur.
- jpgvm 12y agoThough only tangentially related I do wish EME had been properly shot in the head. It's just another Flash that hides behind being "html5" (as if they makes it all ok). At the end of the day it's proprietary code executing on my machine that I have little or no control over. It's not just a security risk, it's also a stability concern and generally a terrible idea. Copyright enforcement should be left to law, content companies shouldn't be trying their hand at it. Who knows, maybe if their content didn't come wrapped in utter crap people might actually part with money for it.
- eeZi 12y agoAt least it's properly sandboxed.
- vertex-four 12y ago> Copyright enforcement should be left to law You would prefer that all copyright violation is a criminal matter rather than a civil one?
- organsnyder 12y ago"Law" isn't limited to criminal cases. Nothing in the poster's statement precluded a lawsuit from being an enforcement mechanism.
- unreal37 12y agoBut that's the way it currently is. And so little 12-year-old Janie gets a $3,000 "demand to pay" letter for downloading a Britney Spears song with the threat of a lawsuit that will take her family's house away if she refuses. Maybe having a somewhat impartial legal entity in between is more protection for the consumer.
- kevincennis 12y agoI view EME as sort of a necessary evil. There was never any chance that large content companies were going to be okay with serving unencrypted media over HTTP. So the choices were: 1. No major film or television content on the web 2. The survival of Flash/Silverlight 3. EME I'm not crazy about any of those choices, but #3 seems the most reasonable.
- revelation 12y agoBizarre. HTTPS isn't a guarantee that a site is not malicious. Its not like I could go to a CA and ask them who they signed that cert for and take on any kind of legal responsiveness. Such is the state of the CA system that they will give a cert to anyone with access to a domains MX and some bitcoins. Instead of this, maybe require there's a user mouse event on the call stack for things like fullscreen.
- air 12y agoThe intent is to prevent man in the middle -attackers from getting access to those features.
- arcatek 12y agoWhy would they need the fullscreen access? I could see the interest for cookies or local storage, but fullscreen?
- carbocation 12y agoSo they can pretend to be your entire browser.
- Danilka 12y agoWhat is going to be the protocol for development environment? Should one deal with ssl just to quickly test out the code? What if a service streams video, which requires full screen feature? It takes quite a bit more compute power to pack it into encrypted connection, and what if the video is not of any value as a secure content. Why should people be forced to encrypt and decrypt spending extra power (battery, in case of portable devices) on it? SSL does not guarantee the security de-facto. Also, there is plenty of personal data that is being passed through a non-encrypted connection, which is way more valuable. If this is an attempt to increase amount of secure connections, it is a very inconvenient one. Why not keep giving bonus point for using it (like SEO higher ranking) rather than making pure HTTP not usable.
- icebraining 12y agoWhat if a service streams video, which requires full screen feature? It takes quite a bit more compute power to pack it into encrypted connection, and what if the video is not of any value as a secure content. Why should people be forced to encrypt and decrypt spending extra power (battery, in case of portable devices) on it? Because otherwise a MITM can abuse the fullscreen feature. SSL is a way of ensuring content integrity, not just privacy. I do think we should have a way of signing content without mandating encryption for these use cases, but until we do, HTTPS is the only choice.
- userbinator 12y agoI do think we should have a way of signing content without mandating encryption for these use cases SSL has it, it's just usually disabled by default - null encryption with non-null MAC.
- pornel 12y agoDevTools can whitelist dev domains: https://w3c.github.io/webappsec/specs/powerfulfeatures/#development-environments https://w3c.github.io/webappsec/specs/powerfulfeatures/#deve... > What if a service streams video; […] spending extra power (battery, in case of portable devices) Then they'll encrypt, because it's cheap. YouTube could do it. Only Netflix is making a fuss because they want to legitimize their DRM as a security layer. It's not 1995 any more. Today even low-end cell phones are orders of magnitude faster than CPUs were when SSL was slow. We've got fast ciphers and hardware-accelerated decoding. https://istlsfastyet.com/ https://istlsfastyet.com/ > SSL does not guarantee the security de-facto. The problem is that HTTP is de-facto guaranteeing insecurity. • HTTPS is the new HTTP. • HTTPS+HSTS+preloaded pinning is the new HTTPS.
- bd 12y agoUhm, I strongly disagree with making fullscreen https only feature. For WebGL and WebVR community this would be a big step backwards, making browser applications again second class citizen vs native apps. And it's not like there aren't already strong enough protections in place. Try for example visiting this mock attack site: http://feross.org/html5-fullscreen-api-attack/ http://feross.org/html5-fullscreen-api-attack/ In every browser I tried it was already obviously fake. It doesn't work already with current security tech: 1) browsers ask for fullscreen permission (with big unmissable dialogs) 2) emulated fake layout is very different from real layout (missing all per-user specific browser settings, e.g. bookmarks or extension buttons or any theme customizations, also font rendering looks different) 3) emulated fake browser UI doesn't respond to interactions in the same way as native UI
- shangxiao 12y agoThe point of that article was that people don't notice subtle changes, especially when their not tech savvy/tired after a long day of work/whatever. Also someone pointed out in the comments that some people tend to ignore changes and click on whatever to get to their destination.
- JustGotHere 12y agoAnd article is ignoring that the site can then add https and do that fullscreen attack anyway. A better solution would be to keep showing a message telling you it has gone fullscreen like browsers currently do.
- bd 12y agoYes, that's true. But for people who don't notice changes there isn't much help anyways. Even much more primitive phishing will still work on them (just think about those "you have virus / clean your computer" ads from past, with images looking like Windows pop-ups, or remember how those "Nigerian prince" scams intentionally use broken English to selectively address more gullible folks). These new proposed security measures will not help those people much, they can still be phished from within browser tab content rectangle. Instead these changes will just basically kill whole class of web applications for a benefit of small subset of population phishable enough with fullscreen attacks but immune to content rectangle attacks. ----- BTW recent Lenovo Superfish fiasco has shown us that in fact you can't even trust native browser security UI elements. Those real UI green locks on https pages can be as misleading as those JS/HTML generated ones. I would much more prefer browsers to secure me from known rogue certificates attacks than from hypothetical hard-to-pull-off fullscreen phishing attacks.
- silon3 12y agoIs http://localhost http://localhost / 127.0.0.1 considered secure?
- thomasfoster96 12y agoFrom what I can gather, yes to the former, probably to the latter.