Live data from Hacker News

Viewing profile — xign

xign

HN member
Joined
Wed, Jan 18, 2017, 12:54 AM UTC
HN karma
40
Public activity
71 items

About xign

No profile information was provided.

Recent public activity

  1. comment
    Comment #46582710

    The whole point of open source license is that they are a legal document that can be enforced and have legal meaning. It's not just a feel-good article. Your argument is like sayin…

  2. comment
    Comment #46068202

    I can't even reproduce your supposed "issue" regarding the Zig compiler "bug". I have an Apple Silicon Mac and tried your reproducer and zig compiled and ran the program just fine.…

  3. comment
    Comment #45933235

    Timed disclosure is just a compromise between giving project time and public interests. People have been doing this for years now. Why are people acting like this is new just becau…

  4. comment
    Comment #45933170

    Whether the codec is from 1995 or 2025 does not matter. What matters is that the codec is compiled in and working by default on ffmpeg as they intend to bundle all codecs for the u…

  5. comment
    Comment #45933107

    But the vulnerability exists already. You are making it sound like Google invented a problem for the project. Maybe the project should be name called if it has hundreds of vulnerab…

  6. comment
    Comment #45933080

    What makes you think the bad actors aren't already finding these bugs? From the looks of it, there isn't really any rocket science going on here. There are equally well-funded bad …

  7. comment
    Comment #45933010

    Yeah, ffmpeg's responses is really giving me a disingenuous vibe as their argument is completely misleading (and it seems to be working on a decent amount of people who don't try t…

  8. comment
    Comment #45932998

    I'm an open source maintainer and I have never been in a situation where someone filing a security issue will withhold indefinitely, nor would I ever think of asking them to withho…

  9. comment
    Comment #45932976

    Public disclosures also means users will know about it and distros can turn off said codec downstream. It's not that hard lol. Information is always better. You may also get third-…

  10. comment
    Comment #45932953

    Except users can act accordingly to work around the vulnerability. For one, it lets people understand where ffmpeg is at so they can treat it more carefully (e.g. run it in a sandb…

  11. comment
    Comment #45932923

    The key point here is: how would a distro know about this vulnerability if Google didn't disclose it? ffmpeg is acting as if Google should have just shut up about it instead of usi…

  12. comment
    Comment #45932901

    I think the answer is pretty simple: ffmpeg is being thin-skinned here. They do care about the vulnerability (despite whining it's an old / obscure format), but they don't want to …

  13. comment
    Comment #45424108

    What is a dick move is releasing an open source project and then getting mad at people cloning it and then go on a PR blitz to try to destroy said fork. You are basically saying "p…

  14. comment
    Comment #45031506

    Notice how replies like this never get a response?

  15. comment
    Comment #45031443

    Seems like there are multiple ways to address that within the GitHub ecosystem. For example, you can set up a GitHub Action trigged by `push_request_target` that will call CodeRabb…

  16. comment
    Comment #43398770

    I don't think you should ever allow dependabot to make direct commits to the repository. The only sane setting (IMO) is that dependabot should just make PRs, and a human needs to v…

  17. comment
    Comment #43398740

    I mean, I think there's a difference between trusting GitHub and trusting third parties. If I can't trust GitHub, then there's absolutely no point in hosting on GitHub or trusting …

  18. comment
    Comment #43398668

    I don't trust apps. I trust Apple (enough) that they engineered iOS to have a secure enough sandbox that a random calculator app can't just compromise my phone. Most developer pack…

  19. comment
    Comment #43375417

    Because LLM generated mediocre code tends to more buggy with more edge cases and harder to debug that those a good programmer wrote.

  20. comment
    Comment #43375396

    With the garbage collection aspect, I do want to point out that eventually people rediscover the benefit of lower level ways to do things and instead come up with improved methods …

  21. comment
    Comment #43375348

    That's a future that's not the case today. With compilers, I rarely have to dig into assembly code and generally I just work in the domain (programming languages) that I'm comforta…

  22. comment
    Comment #42536353

    I have worked in other large companies that use libcurl and they aren't even listed above. It's pretty much the de facto way to do HTTP requests in C-land unless you really want to…

  23. comment
    Comment #42536317

    No? Adding a Rust backend does not change the API. It just calls into the Rust backend via C bindings. If all you care is ABI stability from the user side none of this would break.…

  24. comment
    Comment #42536285

    I think this has to be put against the larger context of Rust… fans that push very hard for the entire world to be rewritten in Rust. Just look at how many Rust projects where thei…

  25. comment
    Comment #42408314

    I think usually people like to blame GitHub Action's design, but this repository here seems to have not done the bare minimum in securing itself and more focused on producing a "st…