Why I was banned from GrapheneOS by Daniel Micay - Michael Altfield's Tech Blog
tech.michaelaltfield.net
Daniel Micay banned me from GrapheneOS. Why? It was for the silliest reason...
  • wildbus8979@sh.itjust.worksEnglish
    7·
    6 days ago

    He was behaving like that back in the Copperhead days. He stole work he didn’t understand from Spender and publically harassed him to the point where Spender/GRsecurity pulled the plug on their public kernel patches. Huge loss for the Linux community.

    • Skorp@sh.itjust.worksEnglish
      32·
      6 days ago

      This is a blatant and complete fabrication that you are spreading. The project is on good terms with Spender and you have no evidence to support what you are claiming.

      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.