6 ms·
It's been said multiple times and often dismissed, but it's becoming more evident that sharing the same hardware with untrusted code is not a good idea at all.
by userbinator 9y ago
It's been said multiple times and often dismissed, but it's becoming more evident that sharing the same hardware with untrusted code is not a good idea at all. Once again the biggest effect is on shared hosting/cloud services, while users of single-user personal computers and self-hosted services are quite immune by default... IMHO giving people more reasons not to run their code on and trust some server located remotely is a good thing.
The researchers looked only at Intel processors, using the attacks to leak information protected using Intel's SGX (Software Guard Extensions), a feature found on certain chips to carve out small sections of encrypted code and data such that even the operating system (or virtualization software) cannot access it.
Perhaps the other good thing to come of this. Fuck that DRM shit.
- giancarlostoro 9y ago> IMHO giving people more reasons not to run their code on and trust some server located remotely is a good thing. Or consider a colocation friendly host / dedicated hosting only. Of course this doesn't mean you have any guarantees there wont be any bad state actors on the premise at any moment (if this is a concern), but it beats sharing a machine with some skiddies.
- sametmax 9y agoIMO any actor capable of leveraging successfully a branch prediction bug should not labeled a script kid anymore.
- reacweb 9y agoIMHO, bare metal is the best solution for security. I love the C1 server of scaleway for small sites. No need of nginx or apache, just a single node process (and maybe a watchdog).
- danpalmer 9y agoIt is still very much best practice to run nginx/apache in front of a Node application. Node is optimised for the inward-looking functionality (i.e. your app) whereas the focus of nginx/apache is the outward looking functionality and leaving a small attack vector and handling bad clients.
- reacweb 9y agoYes, I agree with the best practice in general, but this may not apply when the memory is very small (2Go). The speed improvement achieved by reducing memory footprint is a clear benefit. The benefit of a better mitigation of bad clients performed by nginx is less clear for me (I welcome any argument to change my mind). The surface attack seems similar (one port).
- danpalmer 9y agoNginx will generally be pretty low memory. I know on our web servers we've bumped all the cache sizes quite significantly (10-100x the default) because it's optimised for much smaller machines than we use. Also, the attack surface is less about the port, and more about the protocol. A Node HTTP interface is going to prioritise being correct as much as possible, because you're coding to the API. Nginx on the other hand will often by default (or at least with configuration) give a much more restricted implementation because it knows that there are bad people out there on the web. To take a totally made up example that may or may not actually be the case, but should make the point... you can upload files in web forms with multipart/form-data - I would expect Node to either not have a limit, or have a very high limit, so that you can set it up how you want. Nginx on the other hand has a default of something like 2MB, which is maybe a bit low for apps that need file upload, but will crucially prevent certain kinds of denial of service attacks. There are many similar areas of attack, abusing edge cases of the HTTP spec that Nginx will handle well out of the box. Not to mention the HTTPS support being probably much more complete in Nginx (in terms of cipher suites and browser compatibility).
- anon1385 9y ago>users of single-user personal computers and self-hosted services are quite immune by default Well, except for people using web browsers…
- andy_ppp 9y agoYes was going to say exactly this; how dangerous is Javascript, Image Decoding and Web Assembly in this new world?
- simias 9y agoJavascript and Web Assembly are only dangerous because of this insane policy on the web that everything is whitelisted by default. Fortunately there are extensions to change that behavior but most people won't bother with them, leading web developers to assume that JS is enabled and the site breaking if it's not. In our rush to get rid of Flash on the web we turned the web into Flash. At least it's an open standard now, I suppose. Images and other codecs might also be an issue but it seems like a more complicated attack vector and one that could be mitigated more effectively.
- arghwhat 9y agoOr use applications they probably didn't do a full audit of...
- tomp 9y ago> while users of single-user personal computers You mean, unless you browse the web and enable javascript... Also, which code do you "trust"? Computer games? Phone apps? The OS?
- admax88q 9y ago> You mean, unless you browse the web and enable javascript... Even then, if you're only hitting Gmail, Facebook and reddit, hackernews maybe a few news sites, you're gonna be fine most of the time. Yeah sometimes malware gets distributed via ad networks, so you're even better to use an ad blocker. It's not like the average user spends a lot of time on random sketchy sites, most of their time is on the big companies sites.
- sdenton4 9y agoVisit hacker news, but don't follow any of the links...
- TeMPOraL 9y ago> It's not like the average user spends a lot of time on random sketchy sites, most of their time is on the big companies sites. You need to meet more average users then :). Plenty of sketchy sites are just one Google search away. The most common ways I've seen people end up in such places are free video streaming, browser games and (obviously) porn.
- coliveira 9y agoIn other words, we should get rid of the Internet and use only a handful of sites owned by large companies plus a few highly trusted sites. This seems to be the end of the Internet as we know.
- wslh 9y agoThere are vectors of attack everywhere and we can quickly go back to the discussion about how to build the most secure computer (e.g. unplugged and in a remote place). The industry has the capability to build more secure stuff, we should not block virtualization features just because there are bugs out there.
- zaarn 9y agoUnplugged in a remote place? You could still get in a car and drive there! The only safe computer is a computer that has been submerged in liquid lead, cooled, poured into a solid 6m by 6m by 6m concrete cube, placed into the deepest edge of a saltmine and finally detonating a charge and collapsing a mounting over the computer. That computer will be reasonably out of reach for everyone. It's also quite useless.
- TeMPOraL 9y agoIt could be a scientific instrument, measuring e.g. thermal gradients deep underground, and communicating them to the surface with soundwaves. And then someone will find a vulnerability in the thermocouple data processing code and will pwn the box by cunningly heating and cooling the surface above (possibly with low-yield nuclear warheads).
- IncRnd 9y agoAh yes, like the environmental attack of a hair dryer used to bias a hardware-based RNG's external entropy.
- jssmith 9y agoThis view on sharing hardware seems too pessimistic to me. Strong isolation should be achievable when it is the design objective and and priority. On the end-user/device side, JavaScript has proven that sharing hardware with untrusted code is just too valuable to give up, and a similar dynamic continues to play out in the cloud. I'm also happy whenever a headline brings attention to these types of problems because I believe we can fix them.
- phkahler 9y ago>> This view on sharing hardware seems too pessimistic to me. Strong isolation should be achievable when it is the design objective and and priority. I think it's spot-on. Isolation has never been the top priority. Regardless of the priority, if one simply views all "untrusted code" as "code created by my enemy" the solution becomes clear - don't run it. >> JavaScript has proven that sharing hardware with untrusted code is just too valuable to give up... This is something I strongly disagree with. Javascript has become a common way to handle things but it's not the only way. In my opinion it's the lazy way - most people want to just use what's there and common rather than solve a few problems. >> I'm also happy whenever a headline brings attention to these types of problems because I believe we can fix them. One thing I'm seeing is that CPUs with speculative execution have lower performance/watt and performance/area. So in the cloud space it seem like just going to simpler CPU cores may be a solution (risc-v Esperanto Minions for example). Obviously that's not a solution where single thread performance is critical.
- spookthesunset 9y ago> IMHO giving people more reasons not to run their code on and trust some server located remotely is a good thing. This seems like an odd thing to say. There are plenty of very good reasons to not run your own hardware.... lower cost, uptime, ability to scale with demand all comes to mind. Cloud providers will figure out how to mitigate threats like this...
- RyJones 9y agoIntel's block chain implementation [0] also uses SGX. It isn't all DRM. [0] https://sawtooth.hyperledger.org/docs/core/releases/1.0/sysadmin_guide/configure_sgx.html https://sawtooth.hyperledger.org/docs/core/releases/1.0/sysa...
- userbinator 9y agoThere's a great amount of irony in using a feature which only the CPU manufacturer has control over, in a distributed peer-to-peer system.