oce 🐆

I try to contribute to things getting better, sometimes through polite rational skepticism.
Disagreeing with your comment ≠ supporting the opposite side, I support rationality.
Let’s discuss to refine the arguments that make things better sustainably.
Always happy to question our beliefs.

  • 0 Posts
  • 45 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle





  • oce 🐆@jlai.lutolinuxmemes@lemmy.worldBackdoors
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    3 months ago

    You have provided no valuable argument except “believe my experience”, so I am answering with an equally weak one. Provide me some good quality study and I will be happy to change my mind. I recognize this lack of enlightening information is pretty aligned with closed source philosophy.





  • oce 🐆@jlai.lutolinuxmemes@lemmy.worldBackdoors
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    3 months ago

    In this case, downgrading to the not affected version. If there’s no possible downgrade, stopping the compromised system until it is fixed.
    Keeping the vulnerable system up because you think nobody else should know is a bet, I don’t think it’s sound. State actors are investing a lot to find and exploit those vulnerabilities, in this case probably even funded the implementation of the vulnerability, so I think you should assume that any vulnerability you discover is already used.


  • oce 🐆@jlai.lutolinuxmemes@lemmy.worldBackdoors
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    3 months ago

    No I don’t think you said I was entirely wrong, that part was clear enough.

    My issue is more with your argument from authority and personal experience. It is very easy to be biased by personal experience, especially when it brings good money.

    access controls and supply chain management and traditional security mechanisms.

    So I’ll put my personal experience too (which is also a low value argument). From the outside it may seem this is well done in big companies. But the reality is that this is often a big mess and security often depends on some guy, if any, actually having some standards and enforcing them, until they leave because the company doesn’t value those tasks. But since it’s closed source, nobody knows about it. With open source, there’s more chance more people will look at this system and find issues.
    I don’t doubt some ultra sensitive systems like nuclear weapons have a functional closed source security process because the government understands the risk well enough. But I think there are way more closed source systems, at lower danger level but which still impacts people’s security, that are managed with a much lower standard than if they were open-sourced.



  • oce 🐆@jlai.lutolinuxmemes@lemmy.worldBackdoors
    link
    fedilink
    arrow-up
    30
    arrow-down
    3
    ·
    3 months ago

    Crowd sourcing vulnerability analysis and detection doesn’t make open source software inherently more secure.

    It does, because many more eyes can find issues, as illustrated by this story.

    Closed source isn’t inherently bad, but it’s worse than open source in many cases including security.

    I think you’re the only one here thinking publishing PoC is bad.


  • oce 🐆@jlai.lutolinuxmemes@lemmy.worldBackdoors
    link
    fedilink
    arrow-up
    83
    arrow-down
    3
    ·
    edit-2
    3 months ago

    If your security relies on hidden information then it’s at risk of being broken at any time by someone who will find the information in some way. Open source security is so much stronger because it works independently of system knowledge. See all the open source cryptography that secures the web for example.
    Open source poc and fix increases awareness of issues and helps everyone to make progress. You will also get much more eyes to verify your analysis and fix, as well as people checking if there could other consequences in other systems. Some security specialists are probably going to create techniques to detect this kind of sophisticated attack in the future.
    This doesn’t happen with closed source.
    If some system company/administrator is too lazy to update, the fault is on them, not on the person who made all the information available for your to understand and fix the issue.




  • oce 🐆@jlai.lutolinuxmemes@lemmy.worldDebian security amirite?
    link
    fedilink
    arrow-up
    51
    arrow-down
    1
    ·
    edit-2
    3 months ago

    The malicious changes were submitted by JiaT75, one of the two main xz Utils developers with years of contributions to the project.

    “Given the activity over several weeks, the committer is either directly involved or there was some quite severe compromise of their system,” Freund wrote. “Unfortunately the latter looks like the less likely explanation, given they communicated on various lists about the ‘fixes’” provided in recent updates. Those updates and fixes can be found here, here, here, and here. https://arstechnica.com/security/2024/03/backdoor-found-in-widely-used-linux-utility-breaks-encrypted-ssh-connections/

    That really sucks. This kind of thing can make people and companies lose trust in open source. I wonder if we will learn the reason behind that. I would guess the developer was paid a lot of money by some organization to risk ruining his reputation like that.