Brief items
Security
Security quotes of the week
If adversarial interoperability still enjoyed its alt.-era legal respectability, then Facebook alternatives like Diaspora could use their users' logins and passwords to fetch the Facebook messages the service had queued up for them and allow those users to reply to them from Diaspora, without being spied on by Facebook. Mastodon users could read and post to Twitter without touching Twitter's servers. Hundreds or thousands of services could spring up that allowed users different options to block harassment and bubble up interesting contributions from other users -- both those on the incumbent social media services, and the users of these new upstarts. It's true that unlike Usenet, Facebook and Twitter have taken steps to block this kind of federation, so perhaps the experience won't be as seamless as it was for alt. users mixing their feeds in with the backbone's feeds, but the main hurdle – moving to a new service without having to convince everyone to come with you – could be vanquished.
I mean, given how many copyright, patent, and trademark trolls already exist, aren't folks super excited about the ability to soon deal with data or privacy trolls as well? It'll be a real blast. But what it won't do is actually protect anyone's privacy. Nor will it allow them to "share in the economic value generated by their data."
Kernel development
Kernel release status
The current development kernel is 5.4-rc8, released on November 17. "I'm not entirely sure we need an rc8, because last week was pretty calm despite the Intel hw workarounds landing. So I considered just making a final 5.4 and be done with it, but decided that there's no real downside to just doing the rc8 after having a release cycle that took a while to calm down."
Stable updates: 4.9.202 and 4.4.202 were released on November 18. The massive 5.3.12, 4.19.85, and 4.14.155 updates are in the review process; they are due on November 21.
Cook: Security things in Linux v5.3
Kees Cook catches up with the security improvements in the 5.3 kernel. "In recent exploits, one of the steps for making the attacker’s life easier is to disable CPU protections like Supervisor Mode Access (and Execute) Prevention (SMAP and SMEP) by finding a way to write to CPU control registers to disable these features. For example, CR4 controls SMAP and SMEP, where disabling those would let an attacker access and execute userspace memory from kernel code again, opening up the attack to much greater flexibility. CR0 controls Write Protect (WP), which when disabled would allow an attacker to write to read-only memory like the kernel code itself. Attacks have been using the kernel’s CR4 and CR0 writing functions to make these changes (since it’s easier to gain that level of execute control), but now the kernel will attempt to 'pin' sensitive bits in CR4 and CR0 to avoid them getting disabled. This forces attacks to do more work to enact such register changes going forward."
Development
SystemTap 4.2 release
SystemTap 4.2 is out. This release features "support for generating backtraces of different contexts; improved backtrace tapset to include file names and line numbers; eBPF support extensions including raw tracepoint access, prometheus exporter, procfs probes and improved looping structures".
Development quotes of the week
Page editor: Jake Edge
Next page:
Announcements>>