326
Lasse Collin, the other xz maintainer, has acknowledged the backdoor (tukaani.org)
submitted 2 years ago by to c/linux@lemmy.ml
53 comments fedilink hide all child comments
 

They haven't particularly made a comment on the situation so much as acknowledged it's happening. They seem to be going with the story that they had nothing to do with it and this is news to them. Hope to hear more from them soon so we can find out more about the situation, how and why this happened, etc.

(The sceptical tone isn't because of disbelief of Collin, it's because we don't know enough about the situation to be able to say Collin is or isn't telling the truth here.)

you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 2 years ago (1 child)

I‘m not sure what you‘re suggesting. Every piece of FOSS software is made by someone and the a lot of it builds on top of some upstream thing. Otherwise everyone would have to rebuild from scratch and FOSS would break down. Or am I missing your point?

Also, you cant make every 16 yr old user pay for a foss product. Companies must be made to pay for foss and downstream teams must be made to send parts of their income upstream, no matter if they make enough.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] -8 points 2 years ago (1 child)

    I suggest you read my comment again.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (2 children)

    Mate, we are discussing on two different threads. Chill out. Maybe I didnt get your point so feel free to elaborate or leave it. Your choice.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 years ago* (1 child)

    Mate, we are discussing on two different threads. Chill out. Maybe I didnt get your point so feel free to elaborate or leave it.

    I think it would be really good if all of us on the internet agreed to a rule, which is that if you mischaracterize someone or misread them, it's not that weird for them to want you to not do that. So I don't think it's fair to response to a comment correctly noting they are being mischaractized by going out of your way to try and make it about their emotions/mental state.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -3 points 2 years ago (1 child)

    Yes. I simply think I already wrote what I needed to. The answer to your question is there. I guess it takes time to see my point.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (2 children)

    You only said 2 things:

    • we shouldn't rely on free software made by free labor, and we need to say goodbye to some 60-70% or more of the software we use
    • important software shouldn't reuse code already made, they should reinvent the wheel and in the process introduce unique vulnerabilities and spend orders of magnitude more time doing that

    None of these make sense in my opinion

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 years ago* (2 children)

    we shouldn’t rely on free software made by free labor, and we need to say goodbye to some 60-70% or more of the software we use

    Again I'm just reading along, and as a person who cares about, you know, the principle of charity, I don't see how you can possibly think that's the most charitable interpretation of what they said. I took them to mean we should do what we can to ensure these projects have financial resources to continue, not that we should "say goodbye" to them.

    And here's the crazy thing: I'm not even saying I agree. I just think it's possible to address a face value version of what they're talking about without taking unnecessary cheap shots.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 years ago* (1 child)

    But being charitable to the person you're responding to, they twice said explicitly that they didn't understand what was being said and asked for elaboration and both times got a reply that more or less suggested that they didn't understand because they're illiterate. At some point the reaction becomes understandable.

    edit: different poster from the first two, but I think they were sympathizing with the other person

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago

    That's where the not that weird idea comes into play. It's not that weird to not want to be misrepresented - that's an entirely different thing from trolling, or strawmanning, or seeking out inflammatory topics on purpose. It's a natural and understandable reaction, and we shouldn't respond to it by deciding it's ok to retaliate with increasingly less fair characterizations of their statements.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 years ago (1 child)

    I took them to mean we should do what we can to ensure these projects have financial resources to continue, not that we should "say goodbye" to them.

    They have said this:

    Something as critical as OpenSSH should be (and possibly is) funded by the users and also NOT use third party libs because it's dangerous, as this incidence showed.

    Emphasis mine.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago* (last edited 2 years ago)

    And again, that's not even within an country mile of being a good faith attempt at charitable interpretation, for several reasons.

    You're twisting their words into some sort seemingly overnight goodbye to all software relying on third party libs. A more normal way of taking that is envisioning a more gradual progression to some future state of affairs, where to the greatest extent possible we've worked to create an ecosystem that meets our needs. An ecosystem that's build on a secure foundation of known and overseen libraries that conform to the greatest extent possible to the FOSS vision. Ideally you don't just say goodbye, you work to create ersatz replacements, which there's a rich tradition of in the FOSS world.

    Your other point was even worse:

    important software shouldn’t reuse code already made, they should reinvent the wheel and in the process introduce unique vulnerabilities

    Somehow, you decided that putting words in their mouth about going out of their way to solve the problem only with worst-case-scenario bad software development practices (e.g. lets go ahead and create unique vulnerabilities and never re-use code) is a reasonable way of reading them, which is completely nuts. FOSS can and does re-use code, and should continue to do so to the extent possible. And like all other software, strive to avoid vulnerabilities with their usual procedures. That's not really an argument against anything specific to their suggestion so much as its an argument against developing any kind of software at any point in time - new games, new operating systems, re-implementations seeking efficiency and security, etc. These all face the same tradeoffs with efficient code usage and security. Nothing more or less than that is being talked about here.

  • permalink
  • fedilink
  • source
  • parent