News for hackers. Stuff that matters.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by Darthy on Saturday January 06, 2018 @08:06AM (#16085105)
The Meltdown attack requires an attacker to have a piece of code executed on your server. Epic's servers are used for login, where people send you data, and for game logic, where people also just send you data like "player x moved his avatar here, player y shoots etc". If all the server does is execute the code which Epic wrote themselves and already trust, why would it need to apply the Meltdown patch?
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by progval on Saturday January 06, 2018 @08:24AM (#16085148)
It makes sense if you don't want a remote code execution in one of your app to provide a full root shell.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by jameshart on Saturday January 06, 2018 @10:54AM (#16085743)
If you're talking about a game server like this, though, where you don't have sandboxes running client-originated code, just processes running your own software, any remote code execution vulnerability is already going to be in a position to do incredible damage. There are almost certainly going to be other privilege escalations available to you once you've buffer-overflowed or whatever to dupe the server into running code you control in process - and honestly, once you own the main process on a server like this you can probably do enough damage from in there without even needing to escalate.

I think the frightening thing about meltdown/spectre is the ability for code to escape otherwise solid sandboxes - including VMs, as well as javascript runtimes. It's a change in the threat landscape for systems which expect to run remote code but believe they can do so safely.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by etatoby on Saturday January 06, 2018 @12:16PM (#16086219)
Can any of this be exploited from Javascript? That would be a humongous can of worms.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by ufo on Saturday January 06, 2018 @12:55PM (#16086496)
Yes. This is why webbrowsers are releasing mitigations such as reducing timer precision and disabling the shared buffer api.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by omni on Saturday January 06, 2018 @08:37AM (#16085183)
This is the correct, non-snarky answer. It's a known privilege escalation attack, turns a bad day (someone got a non-root account on my server) into a worse one (root account).
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by Darthy on Saturday January 06, 2018 @08:44AM (#16085203)
Thank you for the explanation, and especially for being non-snarky, which unfortunately seems to be getting rarer and rarer on this forum.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by LV-426 on Saturday January 06, 2018 @09:18AM (#16085337)
> which unfortunately seems to be getting rarer and rarer on this forum.

If this isn't unnecessarily "snarky" itself, then what is it?

snarky: (of a person, words, or a mood) sharply critical; cutting; snide.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by hungerstrike on Saturday January 06, 2018 @09:43AM (#16085453)
That wasn't snarky because it was only mildly critical. Since it was mild, it also wasn't cutting. Lastly, it was not derogatory or mocking in an indirect way and so it was not snide either.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by LV-426 on Saturday January 06, 2018 @10:40AM (#16085675)
Replying here, since the other post I replied to disappeared:

Despite the avalanche of downvotes burying my posts, not even one person can actually answer the question I asked:

The poster could have simply stopped typing after "Thank you for the explanation". He chose to unnecessarily add something more.

So, for everyone who disagrees with me: if what he said wasn't itself "snarky", what was it?

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by throwanem on Saturday January 06, 2018 @11:01AM (#16085782)
> if what he said wasn't itself "snarky", what was it?

A complaint that Hacker News is a less agreeable place than it used to be. Whether that's true or not, don't you think you might find a more effective way of counter-arguing than by being as disagreeable as you can possibly manage without outright swearing in your responses?

I get that you're sure that you're right. That's great! That's a source of strong motivation to pursue an argument. But it suffices really nothing just to say "I'm right", and much less just to say "you're wrong". If you're interested in convincing people that the argument you're advancing is a more accurate model of reality than those with which it's contending, then you have to do just that - convince people, by answering their points with compelling counterarguments of your own.

And if you want to shape the discussion such that it's possible for you to convince anyone of anything, then you must above all treat your interlocutors with impeccable respect, no matter how wrong you may think - or know! - they are. To do otherwise only hardens them against whatever you may have to say, and the outcome you thus produce is even less favorable than that of simply declining to engage in the first place. Conversely, treating those around you with respect tends very strongly to elicit respect toward you from them, in turn. That's how you earn the fair hearing you need to make arguments that might convince, and thus give yourself a place to start.

Perhaps that sounds like a normative, rather than a positive, statement. I've seen people react badly in the past, and sling accusations of "tone policing" and all manner of other offenses against some apparently very abstract conception of discursive mores which may hold sway in occasional quarters but is very far from predominating. I'm not telling you how you should behave in the sort of discourse where "tone policing" is a meaningful phrase - indeed I'm not telling you how you should behave at all. What I'm telling you is that, whatever places you may have been where you found unstinting contempt for your interlocutors to serve your turn, none of those places is here.

That's why hectoring people, as I have observed you fairly consistently to do here, doesn't convince people of your points. At most it convinces them to stop trying to talk with you. Perhaps that's the result you're trying to produce, in which case keep doing what you're doing! But if you're not trying to develop for yourself a reputation here of being someone best avoided, then you may wish to revise your style of argumentation somewhat.

Now before you get too cross with me saying this as I have, consider: We spoke briefly the other day on the subject of complaining about downvotes and why it is not helpful. You seem genuinely upset to accrue them so easily, and I treated that dismay perhaps more cavalierly than was justified. I'm sorry for that; to try to make up for it, I thought I'd explain why it is they keep happening and what you can do to change that.

You clearly expect respectful engagement from others, and there's nothing wrong with that. But when you refuse to engage respectfully with others, who quite reasonably expect the same, it isn't really a surprise when people choose to answer that disrespect by downvoting and moving on, rather than by eliciting your further contempt through an attempt to engage with you.

The good news is that you have in your hands the power to change this state of affairs! The style of your discourse is entirely within your control. Show respect to those around you, and you'll find those around you show you respect in return. You can totally do that! You can totally make that happen. I hope you'll choose to do so.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by musage on Saturday January 06, 2018 @04:38PM (#16087607)
I just threw up into my mouth a little.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by LV-426 on Saturday January 06, 2018 @02:00PM (#16086853)
> A complaint that Hacker News is a less agreeable place than it used to be.

Which makes the place no more agreeable.

> Whether that's true or not... <huge snip>

This is amazing.

I ask a question, and the only "answer" is simply an excuse to segue into a weird, patronizing, passive-aggressive wall of text that has zero to do with what I actually posted, and is nothing but a personal attack dressed up as a lecture on politeness. Amazing.

I guess you don't reach 10k karma on a throwaway by not having a gallery to play to.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by LV-426 on Saturday January 06, 2018 @10:01AM (#16085524)
I disagree. Aside from the sarcastic "buffer overflow" comment, his comment was far more snide than any of the replies he seemed to be complaining about.

Since you take a different view though, as I asked in my post, if it's not "snarky" then what was it?

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by akira2501 on Saturday January 06, 2018 @08:10AM (#16085117)
> why would it need to apply the Meltdown patch?

They're using a "monolithic" cloud provider and don't have a choice in their current deployment?

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by drawnwren on Saturday January 06, 2018 @08:13AM (#16085126)
This is a horrible approach to security. If you only secure against attacks you expect, you're gonna have a bad time.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by toomuchtodo on Saturday January 06, 2018 @10:42AM (#16085685)
Security is about risk mitigation. You cannot derisk entirely, so you make tradeoffs. Without knowing all of the parameters, it’s disingenuous to say it’s a horrible approach to security.

The most secure computer is powered off, enclosed in concrete 6 feet below the surface of the earth. It is not very useful though.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by userbinator on Saturday January 06, 2018 @12:10PM (#16086167)
Very much this. In the real world, basically no one will make their house entirely bulletproof and never go outside just because of the possibility that someone could shoot them. Everyone knows that could happen, but is fine with the risk.

"100% secure" is unattainable, and to attempt to achieve it to the exclusion of all other concerns is probably a very bad idea.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by em3rgent0rdr on Monday January 08, 2018 @11:02PM (#16103499)
Reminds me of Battlestar Galactica. The humans were so (wisely) fearful of the Cylons that their ship computers were not networked in anyway. For their risk/reward trade-off curve, the benefit from having computer networks were not worth the risk of the Cylons being able to compromise the entire ship. All communication was either verbal or done via fax printed to paper and so had to go through human intermediaries.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by toomuchtodo on Wednesday January 10, 2018 @08:48PM (#16120878)
Good catch!
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by merb on Saturday January 06, 2018 @11:29AM (#16085912)
if you do not apply spectre/meltdown migtation on non virtualized hardware which only you control you are safe. of course a malicious process could do harm without them, but a malicious process probably can be as harmful, even if you have the patches applied. basically we need these patches since on the internet a ton of stuff lives on virtualized hardware and there you can actually be harmful to other vms or even the host itself. basically spectre/meltdown needs to be applied in hosted environments and on clients. on everything else it's way less scary than on those two environments.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by msbarnett on Saturday January 06, 2018 @03:49PM (#16087372)
Do you also run all processes on your server as root?

If you’re not going to apply patches that close privilege escalation bugs, you might as well. You’re putting all your security eggs in one basket.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by merb on Saturday January 06, 2018 @06:57PM (#16088204)
Well a lot of processes run as Root anyway. Also if possible i run as few processes as possible
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by pixl97 on Saturday January 06, 2018 @08:54PM (#16088625)
>Well a lot of processes run as Root anyway.

Then you didn't listen to DJB like 15 years ago. Moreso, your processes shouldn't be running under the same username. Principle of least user authorization people.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by merb on Monday January 08, 2018 @05:54PM (#16101637)
please just install a linux distribution and run ps aux. a ton of stuff just runs as root. either because there is no other way or because it's a bad default.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by msbarnett on Monday January 08, 2018 @10:02PM (#16103225)
Yeah it’s your job as a Unix dev or admin to not stick with crummy but convenient defaults, kid. Nothing exposed to the web or touching anything exposed to the web should be running as root. Each thing should be running under its own, very limited, user and group. If something gets hacked, you want it to be as least privileged as possible.

We know how Unix works. We’re telling you because you clearly are out of your depth. If you don’t understand that you have no business maintaining anything on the internet.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by PascLeRasc on Saturday January 06, 2018 @04:06PM (#16087459)
On the other hand, if you aren't affected by what a successful attacker can do, you're in a good place.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by cookiecaper on Saturday January 06, 2018 @12:11PM (#16086176)
Some things are just not applicable. There's no point adding another padlock to the outside wall of Fort Knox. If untrusted users don't send instructions to the same physical CPU that you're using, Meltdown/Spectre are not relevant.

I also think that we need more information before we really see the long-term performance impact here. First, the patches will likely be optimized over time. Second, I am not sure that PTI needs to be run within guest kernels if the host already has the mitigation (effectively creating a double-hit from PTI in both the guest and host kernel), or that even if PTI is needed in both kernels now, that it will be needed long-term. We also need to figure out what type of Spectre mitigations need to be performed within the guest if the host system has the new microcode that selectively disables branch prediction.

The short answer is that it's going to take another 4-6 weeks before even the kernel devs have a firm grasp of what's useful/necessary to mitigate this and for things to settle into place, as Greg K-H blogged about earlier. At that point, we should have a more realistic perspective on the long-term performance impact.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by sigmar on Saturday January 06, 2018 @01:12PM (#16086599)
>There's no point adding another padlock to the outside wall of Fort Knox.

Strongly disagree. No single defense measure is infallible and defense in depth has proven one of the most important topics in computer security.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by pixl97 on Saturday January 06, 2018 @08:56PM (#16088631)
In the past if you had a RCE that only got user level access and that user was very locked down there was only a limited amount of damage they could have done. Now with meltdown, every RCE is a full information loss at system level exploit.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by mrweasel on Saturday January 06, 2018 @10:40AM (#16085673)
Perhaps they don't, but eventually the patches become part of the mainline kernels, and then they will run with the patch applied.

Regardless of what some of my customers believe patches are rarely hand picked and then applied. All security patches are applied, always, kernel patches even more so. They are rolled out with the tools provided by the operating system, be it Windows, Redhat, Ubuntu, OpenBSD, Solaris or whatever, and they don't make assumptions about your use case, they just apply all security patches.

Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by Pxtl on Saturday January 06, 2018 @09:06AM (#16085292)
I assume their servers will he running untrusted Unreal Engine games, maybe even community-developed mods, some of which may have attacks in the script of the game.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by em3rgent0rdr on Monday January 08, 2018 @10:58PM (#16103480)
Your argument also applied to other circumstances where the computer only runs trusted code. For example a fully FLOSS software stack on home computer with JavaScript disabled in the browser.
Re:CPU Usage Differences After Applying Meltdown Patch at Ep... by ardacinar on Saturday January 06, 2018 @08:25AM (#16085150)
> code executed on your server. Epic's servers are used for login, where people send you data, and for game logic, where people also just send you data like "player x moved his avatar here, player y shoots etc".

Have you ever heard of the term 'buffer overflow'?