3 ms·
This is how the web's re-incarnation could begin. Imagine: • 2020: Websites are too complex. The security implications are too high. Let's run all of that code
by Wowfunhappy 6y ago
This is how the web's re-incarnation could begin. Imagine:
• 2020: Websites are too complex. The security implications are too high. Let's run all of that code remotely, and send only draw commands to the user.
• 2025: Hey, developers, want your website to be faster and more efficient? Here's an API for performing certain operations directly on the user's machine. Don't worry, we've implemented everything in a limited and security-conscious way. Pinky promise the standard won't grow out of control over time.
• 2040: Neo-websites are too complex. Let's run all of that code remotely...
I'm not sure if I actually believe this will happen. But, consider how we got here: websites originally relied on server-side rendering, and gradually shifted to client-side rendering over time. Now, Cloudflare is offering a way to force all of that code back on to a server...
- ignoramous 6y agoWhat Cloudflare's announced is more than just DOM reconstruction, though. They sound very different to the likes of Opera Mini Turbo or Amazon Silk's Cloud Browser or Chrome's Fly Wheel...[0] In Cloudflare's case, the rendering happens on the server and only rasterization commands are sent to the clients similar to AWS NICE [1]. As a security product (if you trust Cloudflare), browser isolation sounds super tempting on-paper. As they mention in the blogspot, an ashtonishing 70% of the exploits are through various forms of Phishing and other attacks in the browser. DNS based blocklists (and Google SafeBrowsing) which form a viable defence against Phising can only protect you from so much [2]. So, my point is, regardless of the thin-client / thick-client cycle, there's a real value to this product. It isn't for everyone but there's no denying its utility, especially when you consider the fact that most SaaS tools are browser-friendly. I have also been following MightyApp.com that is trying to do something similar but for consumers and with focus on productivity. It is interesting to see how this would play out. If there's a huge market for this, Google is sure to pounce on it too, and then things will get real interesting... as if AMP, WebComponents [2] and Privacy Sandbox [3] weren't already enough. [0] https://news.ycombinator.com/item?id=19774768 https://news.ycombinator.com/item?id=19774768 [1] https://aws.amazon.com/hpc/dcv/ https://aws.amazon.com/hpc/dcv/ [2] https://blogs.akamai.com/2018/01/a-death-match-of-domain-generation-algorithms.html https://blogs.akamai.com/2018/01/a-death-match-of-domain-gen... [3] https://news.ycombinator.com/item?id=24390324 https://news.ycombinator.com/item?id=24390324 [4] https://news.ycombinator.com/item?id=20767891 https://news.ycombinator.com/item?id=20767891
- lucideer 6y ago> very different to the likes of Opera Mini [...] In Cloudflare's case, the rendering happens on the server and only rasterization commands are sent to the clients. Literally exactly what Opera Mini has done since circa 2005[0]. The main difference here is that Opera Mini progressed to the gp's "2025" scenario quite some time ago by adding limited support for events alongside OBML's rasterization commands. [0] https://github.com/grawity/obml-parser/blob/master/obml.md https://github.com/grawity/obml-parser/blob/master/obml.md
- resfirestar 6y ago> an ashtonishing 70% of the exploits are through various forms of Phishing and other attacks in the browser Credential phishing doesn’t care where your browser is running, as I frequently have to remind IT teams who think their web proxy logs can identify 100% of victims of a phishing attack (there are almost always a few people who clicked on their phone). RBI of this type is specifically to mitigate vulnerabilities in the browser engine, the type of 0-day where you just click on the wrong thing and get owned. While these are a real threat, they are nowhere near 70%, more like less than 1% (and see my other comment about how the 70% number is just made up). > [2] https://blogs.akamai.com/2018/01/a-death-match-of-domain-gen https://blogs.akamai.com/2018/01/a-death-match-of-domain-gen... Domain generation algorithms are used for malware command and control, not in the browser/phishing stage of an attack. An actual reason DNS blacklists aren’t perfect for this purpose is that attackers host malware distribution and phishing pages on legitimate services like Google Docs and Sharepoint.
- ignoramous 6y agoI should have been clearer: Domain generation algorithms render solutions like Google SafeBrowsing vulnerable. Sure, these are only used by botnets today, but before we know it, it'd be put to use by adware and spyware too.
- resfirestar 6y agoDGAs aren't a solution to the "my phishing page is blocked by safebrowsing/some other blacklist" problem. You can't send someone an email with a "link" that generates URLs until one of them isn't blocked: hyperlinks aren't programmable in that sense. You can send them a link to a page that does that, sure, but that doesn't stop them from blacklisting the redirector page. How would someone running a phishing campaign actually use a DGA?
- nabla9 6y ago> 2020: Websites are too complex. The security implications are too high. Let's run all of that code remotely, and send only draw commands to the user. Everything old is new again. 1984: X Window System. Architecture-independent system for remote graphical user interfaces and input device capabilities. X provides the basic framework, or primitives, for building such GUI environments: drawing and moving windows on the display and interacting with a mouse, keyboard or touchscreen. Unlike most earlier display protocols, X is specifically designed to be used over network connections rather than on an integral or attached display device. X features network transparency, which means an X program running on a computer somewhere on a network (such as the Internet) can display its user interface on an X server running on some other computer on the network. The X server is typically the provider of graphics resources and keyboard/mouse events to X clients, meaning that the X server is usually running on the computer in front of a human user, while the X client applications run anywhere on the network and communicate with the user's computer to request the rendering of graphics content and receive events from input devices including keyboards and mice. source: https://en.wikipedia.org/wiki/X_Window_System https://en.wikipedia.org/wiki/X_Window_System
- jfengel 6y agoThis is more limited than X, since it's designed just to speak HTML. (Though I suppose that HTML5 supports Canvas which could, potentially, be used much like X Windows... but I don't see that becoming the main way people write applications.)