Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

BSD Cafe Billboard

BigSneakyDuckB

BigSneakyDuck

@BigSneakyDuck
About
Posts
4
Topics
0
Shares
0
Groups
0
Followers
2
Following
0

Posts

Recent Best Controversial

  • FreeBSD user groups
    BigSneakyDuckB BigSneakyDuck

    The FreeBSD User Groups page has got quite outdated so crowdsourcing some replies has helped update a few things. Mostly group closures unfortunately but also some changes of contact details.

    For people who don't have a Reddit user account, I also started a FreeBSD Forums thread that found a few more updates, including a change to a long-standing venue.

    So feel free to reply there too: forums.freebsd.org/threads/102512/

    I don't check for replies quite so regularly here - but if you don't have a FreeBSD Forums or Reddit account then leave a reply here and I'll get back to you at some point.

    FreeBSD freebsd documentation meatspace user group meetup

  • AI: misinformation about Anthropic Claude Mythos, Nicholas Carlini, and FreeBSD
    BigSneakyDuckB BigSneakyDuck

    Thanks Graham. I'll summarise for people here who might not want to follow the Reddit thread.

    Another of Devansh's claims repeated in El Reg, that "the Linux kernel bug" was found by Opus 4.6 not Mythos Preview, is also wrong. The Carlini/Anthropic article from 7 April makes it clear that Mythos Preview found multiple Linux kernel vulnerabilities! This comes from Devansh misunderstanding this post by Michael Lynch: https://mtlynch.io/claude-code-found-linux-vulnerability/

    Devansh is also incorrect in his claim that all five exploits listed by Lynch were found by Opus 4.6 - Lynch makes no claim about what model was used, and by looking at the commits you can see the third one ("futex: Require sys_futex_requeue() to have identical flags") was found by Mythos Preview: Carlini's 7 April report includes "see, e.g., commit e2f78c7ec165 patched last week". https://github.com/torvalds/linux/commit/e2f78c7ec1655fedd945366151ba54fcb9580508

    Looking at the dates on the other commits, I think at least one other was found by Mythos Preview too.

    The weird thing is that other parts of Devansh's substack post actually get the Calif/Anthropic distinction correct. So I just cannot understand how he looks in Calif's GitHub repo and attributes the work to Carlini unless - and the writing style and theme of the blog suggests this might well be the case - it was substantially written by AI. My sneaky duck senses are very strongly tingling on that, in fact. It would be ironic if a journalist writing an article about AI not being so scary after all has been misled by an AI in the process...

    Since Devansh doesn't add any original and just regurgitates other stuff (often inaccurately) it's a shame the journo didn't go straight to Devansh's cited sources and quote them instead. Would have saved stuff getting corrupted in the pass-the-message telephone game.

    FreeBSD freebsd carlini claude mythos cve misinformation

  • FreeBSD 16 System Calls Table
    BigSneakyDuckB BigSneakyDuck

    @naltun
    For comparison, syscalls(2) from the Linux man-pages project:

    https://man7.org/linux/man-pages/man2/syscalls.2.html

    FreeBSD freebsd calls system

  • Tell about your best practices setting up a FreeBSD server
    BigSneakyDuckB BigSneakyDuck

    I recently submitted a Bugzilla PR for the FreeBSD Handbook's Security chapter, noting that it does not contain the phrase "hardening" or cover the how to perform the kind of hardening measures that I've seen documented in other OSes, or mandated by workplace policies.

    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294167

    This is far from my area of expertise so any additional comments there on what the Handbook should include would be welcome. Obviously there will be some hardening requirements for personal laptops that are different to hardening for servers and vice versa, which makes structuring the chapter a bit tricky. In fact one of my complaints in the PR is that advice which should be drilled into all users, like taking note of FreeBSD Security Advisories, is at the very bottom of a long page - anybody who reads that far will have to get past a lot of material only relevant for more specialist use cases.

    https://docs.freebsd.org/en/books/handbook/security/

    FreeBSD setup hardening best-practices freebsd
  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups