* Posts by jch

9 posts • joined 3 Apr 2016

All good, leave it with you...? Chap is roped into tech support role for clueless customer


Helping out friends

The receptionist and the remaining sysadmin were both friends: I wasn't about to leave them in the lurch. Both had left a few months later.

Linus Torvalds opts for the scream test: Linux kernel syscall tweaked to shut data-leak hole – anyone upset, yell now


Hands up everyone that’s heard of mincore(2)

OK. Anyone who hasn’t used it in anger, please put your hands down.

Who’s left?

The authors of the paper noted that in their admittedly limited test that mincore wasn’t even called once.

I’m sure there is a good use for it, but I’m unsure what.

New side-channel leak: Boffins bash operating system page caches until they spill secrets


Re: Linux patch

Yes, it is a change of semantics. Previously you could find out if someone had recently been looking at, say, /usr/share/dict/words but with the patch you can’t. You can only find out if a file is mapped by a process.

In practice this is not likely to be a big deal: mincore(2) is not exactly heavily used. You can still use mincore(2) to find out if some shared library, for example, is in use because it is mapped. You can’t know whether the pages behind the map are resident or not.


Linux patch

Linux now has a patch: 574823bfab82 ("Change mincore() to count "mapped" pages rather than "cached" pages")

It changes the semantics of mincore(2) to report mapped pages rather than present pages which means that you can no longer use that to determine if a file is present in the cache. You might still be able to mount a timing attack by flushing pages and measuring how long it takes to load the page to determine whether it was present before you loaded it. Whether that makes the attack infeasibly slow I wouldn't like to say.

Stack Clash flaws blow local root holes in loads of top Linux programs


Re: HOW?!

Read the advisory from Qualys _carefully_ it does explain how it works. I'm sure you'll see a proof-of-concept if not an outright exploit soon as well.

Systemd kills Deb processes


Re: Why user processes should persist after logout?

I do this regularly. I kick off a long-running compile, for example, then I log out because I'm going home and I'm not going to be logged in.

People have worked like this for a long time and now systemd comes along and says, no you can't do that, you must stay at work until 10pm watching your long running build run.

What struck me as especially stupid was the comment that perhaps system users should be exempt from that policy. What's a system user? The user created for that application software you just installed? You're not retrospectively insisting that application software should have its user's uid < 1000 but those uids are informally reserved for system use, not application use.

systemd needs a dose of real-life -- forcing your own desktop world view on everyone is preternaturally arrogant and stupid.

Microsoft lures top Linux exec from Oracle to Redmond


Re: Open Source?

I've even more sure you're wrong now :)


Re: Open Source?

Wrong on both counts.

Biting the hand that feeds IT © 1998–2019