• wildbus8979@sh.itjust.works
    link
    fedilink
    arrow-up
    14
    arrow-down
    2
    ·
    13 days ago

    Yeah strcat has been an ass since the Copperhead days. He’s set back Linux security at least a decade by pissing off Spender of GRsecurity to the point of making him remove the public patches (not that I think Spender was right to do that, but I understand why it happened after what Mackay did).

    The dude is toxic.

      • wildbus8979@sh.itjust.works
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        13 days ago

        He crashed and burned the Copperhead project, yes. Copperhead was just him and a business partner that he totally fucked over.

        • Scoopta@programming.dev
          link
          fedilink
          arrow-up
          3
          ·
          13 days ago

          Yeah sounds about right. The only reason I’m even running graphene right now is because I heard he left the project. Otherwise I wasn’t sure I wanted to be dependent on it

          • Zaptosis@monero.town
            link
            fedilink
            English
            arrow-up
            1
            ·
            8 days ago

            GrapheneOS is open source, just because you disagree with who runs it doesn’t mean the code itself is bad. Its an extremely popular project now & there are a lot of eyes on it.

            It has long since evolved beyond something Daniel can simply destroy as a whim & any attempt to sabotage it would be met with a roaring backlash & warnings from pretty much everyone in the privacy & security space.

            I think you’re good to keep on using GrapheneOS, there simply exists no better option. Though if you are set on switching I guess CalyxOS (if they remain in operation) or BraxOS would be the best alternatives.

            • Scoopta@programming.dev
              link
              fedilink
              arrow-up
              1
              ·
              8 days ago

              XZ was also open source…albeit less eyes on it probably. Point is we take “open source” for granted and assume it means “secure” but the person running a project, even an open source one, can do real damage.

              • Zaptosis@monero.town
                link
                fedilink
                English
                arrow-up
                2
                ·
                8 days ago

                I agree with that sentiment fully, just because something is open source doesn’t mean it’s automatically secure. Though when an extremely popular project’s entire focus is high security & the specific eyes on the project are the exact people who are professionals in security, I’m more inclined to trust that it would be pretty hard for Daniel to slip in a critical flaw into the code.

                Its just to me the whole idea that one man can sabotage a project of this scale seems pretty overboard. GrapheneOS is a great tool. A lot of people hated Edison, he was a huge ass with an even larger ego, but it doesn’t mean we shouldn’t use DC electricity. I would argue that if you dislike Daniel McKay, that same thought process should still apply. You may not think he’s the greatest guy, personally I don’t have any strong opinions on him. But what he’s done is undoubtedly extremely helpful to anyone concerned with both privacy & security.

        • tranquil_cassowary@sh.itjust.works
          link
          fedilink
          arrow-up
          3
          arrow-down
          6
          ·
          12 days ago

          The business partner fucked over him by stealing a bunch of crytpo donations that were meant for CopperheadOS which later became GrapheneOS. CopperheadOS which was agreed with Donaldson to be independent from the Copperhead company which was created to support the development of Copperhead but wasn’t allowed to control the CopperheadOS nor to have any ownership or copyright over the code.

      • tranquil_cassowary@sh.itjust.works
        link
        fedilink
        arrow-up
        3
        arrow-down
        5
        ·
        12 days ago

        They did not leave the project. They are still a developer, a director of the GrapheneOS foundation, and someone shaping the direction and quality of the operating system. They did step down in their role as lead developer though, which was taken over by another person, who is also a director. They also lowered their public social media presence on their personal accounts, in order to avoid harassment and attacks.

    • Skorp@sh.itjust.works
      link
      fedilink
      arrow-up
      5
      arrow-down
      6
      ·
      13 days ago

      That information you posted about Spender and GRsecurity is false. That isn’t why the patches were removed. The project is in good standing and contact with Spender.

      Also, your comment about crashing and burning the Copperhead project is blatantly false as well. The other business partner attempted a hostile takeover that was rebuffed.

      This blog post that they have posted across the fediverse, and multiple other platforms is a near complete fabrication of the timeline and what actually occurred. Anyone who has gone to GitHub to look at it has found that maltfield’s claims are baseless and they are acting inappropriate childish and unacceptable manner.

      You are just saying things without a shred of proof and no one is asking for any. So here I am: Please provide proof of all of these claims.

      • bombadil@programming.dev
        link
        fedilink
        arrow-up
        7
        arrow-down
        1
        ·
        edit-2
        12 days ago

        You are just saying things without a shred of proof

        Likewise.

        Please provide proof of all of these claims.

        • Skorp@sh.itjust.works
          link
          fedilink
          arrow-up
          3
          arrow-down
          2
          ·
          11 days ago

          Here is the information about Spender and GRsecurity copied from my other post:

          It was after GRsecurity became private that they had an issue with people making upstream security contributions, particularly upstreaming anything from the GRsecurity patches. They had disagreements about that, and then moved past it and are on good terms now.

          It’s absolutely ridiculous to claim that Micay has anything to do with them making things private.

          https://grsecurity.net/announce https://news.ycombinator.com/item?id=10126319

          It was Wind River, owned by Intel, which was the main offender for upstreaming the patches. Micay was the one who introduced GRsecurity in Arch Linux and did all the integration it had for PaX exceptions and the start of RBAC support (systemd was an issue at the time). It was afterwards once it became private that it was awkward because they didn’t want people upstreaming or maintaining ports of their work but at the time Micay was maintaining GRsecurity in Arch Linux and GrapheneOS (then called CopperheadOS) was using the PaX subset for kernel hardening, so there were existing uses of it to try to keep going in some way.

      • refalo@programming.dev
        link
        fedilink
        arrow-up
        5
        arrow-down
        1
        ·
        12 days ago

        Hello Daniel. Why do you keep creating alts and then calling everything fake news with no proof besides “google it yourself”?

      • wildbus8979@sh.itjust.works
        link
        fedilink
        arrow-up
        6
        arrow-down
        3
        ·
        12 days ago

        You’re drinking the strcat Koolaid. There was no take over. His business partner was mearly looking at avenues of monetization and dipshit blew a fuse.

        • tranquil_cassowary@sh.itjust.works
          link
          fedilink
          arrow-up
          4
          arrow-down
          5
          ·
          12 days ago

          Copperhead OS was supposed to be independent of the Copperhead company. They were not in the right to just take over the infrastructure and claim ownership or copyright of the code.