• 0 Posts
  • 381 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle



  • Hard to figure out what you’re trying to accomplish.

    Are you using x11 forwarding? X11 doesn’t touch audio, so x11 forwarding itself won’t work, you’ll have to tunnel the whole stream.

    And if you get that to work, you’ll have reinvented https streaming. It’s so much simpler to just use a local client to connect to remote resources, or make the stream available in a protocol meant for streaming media, like rtsp or das.



  • I did. The article is scant, and the source report is everything bad about ai in the vuln world; high drama, low info. LPEs are not RCEs!

    And we don’t know what the exploits are. If it’s a bunch of local jvm consoles or vi escapes into shell where it’s like “oh this could give you root!”, that’s not super useful without knowing if it’s a dumb initial config or an actual use-after-free or other memory exploit.

    That’s why we don’t classify manufacturers with bad/no default creds as CVEs, that’s just bad

    Like I said, there is a lot of work to do before these become legit, and it almost certainly won’t be 958 exploits after actual professionals review them properly.

    And again, stop taking OpenAI at their word about security.



  • If you have ever actually seen the discovery process, you’ll understand that bugs and rce’s don’t just popup on a list from a computer. Sure, you can generate a list of places to start testing, but each of those has to be validated, reproduced, documented and understood before it’s confirmed. It’s not just the discovery of a starting point that constitutes an rce or other vuln, there’s a ton of work that needs to be done by humans also.

    So a few bad ones in the news? Sure. A list of 1500 non-validated rces? I’m not holding my breath.

    You really have to think critically and let go of the “hacker” sensationalism in infosec, it’s easy to fall into.



  • 30 years of neckbeards naively insisting that web services should be free.

    Why. You were off to a great start.

    I’m one of those neckbeards and web services should be free, as in a social service. So should potable drinking water.

    Paying for a social service with money voluntarily or with your own data is not a really a choice between providers, it’s an admission that we should, in fact, all remain essentially cattle.









  • It shows that the CVE fixes were consistent during the last 2.5 years and 14 releases.

    Right, yes. But if the transitions from 4.x to 5.0 and 5.x to 6.0 were also shown, we’d be able to see that the bump itself isn’t significant, and that this happens after every major version release.

    The magnitude of the bump is what’s important, and we can’t see that without comparing to pre- and post- AI tooling.

    Why 5.0 and 6.0, those are ancient. This goes back to 6.9 from May 2024, where Ai usage in the Kernel wasn’t a thing until the recent few releases.

    That’s the whole point.


  • Minor versions go up according to a certain pattern based on how the change mgmt is handled for the kernel, but major releases are marked when the kernel team “feels it’s the right time”.

    From lwn: https://lwn.net/Articles/871989/

    To kernel developers, version numbers continued to have no meaning other than as a measure of where things were on the timeline, he said; users were encouraged to run the latest version. But if you tell customers they need to move from 3.20 to 4.0, they will consider it a multi-year effort that requires planning and paperwork; “so they will only do it when they have time, which is never”. Going from 3.20 to 4.0 seems like a big jump, and 4.0 to 4.2 seems much smaller, even though the latter brings roughly double the number of changes.