[–] 1 point 1 week ago* (last edited 5 days ago) (3 children)

You can’t load modules built with a different compiler.

Sure you can. There's even multiple guides for how to write C++ kernel modules, which inherently is going to use a different compiler than what was used for the kernel itself. BOSS Linux even writes C++ kernel modules.

if you want to use a module wrote in rust you also need to have built in the rust support in the kernel

Only if the module uses rust-specific interfaces in the kernel, otherwise it can be assembled into a .ko to have plain C-style symbols loaded by the kernel like normal.

  • source
  • parent
  • context
  • [–] 1 point 1 week ago (5 children)

    you need to build the kernel with clang to build the kernel with the rust support

    I believe this statement is incompatible with how C works. The kernel can load modules written in any language as long as it outputs a .ko, so there can be no technical requirement for building the rest of the kernel itself with clang.

  • source
  • parent
  • context
  • [–] 2 points 2 weeks ago*

    I wonder how many people saw this coming.

    I get the sense that a lot of people were blindsided recently, not only from large recent donations to some groups, and Linus using AI... but also OSI declaring a focus on politics.

  • source
  • parent
  • context
  • [–] 3 points 2 weeks ago*

    IDK but I have a lot of issues with that list anyway... they seem to have a strange definition of "permissive AI policy", i.e. any mere mention of an AI service gets you on the list.

    Example: OpenBSD and NetBSD both show as "permissive" on the list, even though both have publicly stated otherwise, just because there are one or two commits where someone (prominent dev) commented something like "I had help from Claude but you can't tell, and I personally vouch for this and I know what I'm doing."

  • source
  • parent
  • context
  • [–] 13 points 2 weeks ago

    Thankfully modern browsers use Certificate Transparency, and there's no indication that any compromised certs were actually used publicly.

    However, there are many devices that use TLS which are not browsers, and those devices could in theory be selectively targeted with an evil cert without alerting the public CT servers.

  • source
  • parent
  • context
  • [–] 4 points 2 weeks ago* (7 children)

    This is actually much worse for privacy than leaving everything stock, because a site can tell you aren't downloading or running any javascript, and that immediately puts you in an extremely tiny bucket of people it needs to differentiate from, making any differences visible via IP/TCP/TLS/HTML/CSS much more unique.

    And yes, fingerprinting is possible with just HTML and/or CSS... I would argue even moreso without JS.

  • source
  • parent
  • context
  • view more: next ›