overview for Skorp

The Browser Wasn’t Enough, Google Wants To Control All Your Software in c/technology@lemmy.world

[–] Skorp@sh.itjust.works 1 points 1 day ago (1 children)

CalyxOS is not hardened in any way and is in some ways less secure than stock AOSP. They are also on a hiatus and have discontinued updates: https://discuss.grapheneos.org/d/24791-departure-of-calyx-calyxos-leadership-and-discontinuation-of-calyxos-updates

Would you trust an open source software maintained by a developer who you disagree with politically (or otherwise don't like the developer)? in c/asklemmy@lemmy.world

[–] Skorp@sh.itjust.works 8 points 1 day ago (1 children)

He lied about stopping use of GrapheneOS. He can be seen in videos long after still using GrapheneOS on his Pixel. Also, the reasons he stated for not using/trusting it were nonsense. There was not, and is not, a technical way to target a user with malicious OTA updates.

He was also one of 3 owners of a for-profit telecom that included Nick Merrill (Founder of Calyx). https://sec.gov/Archives/edgar/data/2009536/000200953624000001/xslFormDX01/primary_doc.xml is the SEC filing for shares issued in February 2024 .

Google will block sideloading of unverified Android apps starting next year in c/technology@lemmy.world

[–] Skorp@sh.itjust.works 2 points 1 week ago

LineageOS also significantly regresses security compared to barebones AOSP.

Userdebug builds
No locked bootloader or verified boot
Incomplete backports of patches

GrapheneOS: Another contributor attacked & banned by Daniel Micay in c/cybersecurity@sh.itjust.works

[–] Skorp@sh.itjust.works 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

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.