[6 / 3 / 1]
wtyyykbfpqb41.jpg
1675327795560686.jpg
First off, ignore and avoid Google Pixels, GrapheneOS/LineageOS and just Android in general.
>where's your proof that GrapheneOS is malware?
From the horse's mouth:
>GrapheneOS aims to provide reasonably private and secure devices. It cannot do that once device support code like firmware, kernel and vendor code is no longer actively maintained. Even if the community was prepared to take over maintenance of the open source code and to replace the rest, firmware would present a major issue, and the community has never been active or interested enough in device support to consider attempting this. Unlike many other platforms, GrapheneOS has a much higher minimum standard than simply having devices fully functional, as they also need to provide the expected level of security. It would start to become realistic to provide substantially longer device support once GrapheneOS controls the hardware and firmware via custom hardware manufactured for it. Until then, the lifetime of devices will remain based on manufacturer support. It's also important to keep in mind that phone vendors claiming to provide longer support often aren't actually doing it and some never even ship firmware updates when the hardware is still supported by the vendors...
>GrapheneOS also has high standards for the privacy and security properties of the hardware and firmware, and these standards are regularly advancing. The rapid pace of improvement has been slowing down, but each hardware generation still brings major improvements. Over time, the older hardware starts to become a substantial liability and holds back the project. It becomes complex to simply make statements about the security of the project when exceptions for old devices need to be listed out. The project ends up wanting to drop devices for this reason but has always kept them going until the end-of-life date to provide more time for people to migrate.
Source:
https://grapheneos.org/faq
>linux-hardened-docs:linux-libre-hardened-docs::[semifree] docs comes from nonfree linux-grsec kernel
>linux-hardened-headers:linux-libre-hardened-headers:fsf:linux_ linux-backports-modules.2A_ linux-ubuntu-modules:[semifree] blobbed source
>linux-hardened:linux-libre-hardened:fsf:linux_ linux-backports-modules.2A_ linux-ubuntu-modules:[semifree] nonfree blobs and firmwares
Source:
https://git.parabola.nu/blacklist.git/plain/blacklist.txt
Then you also have the ARM Trustzone backdoor along with their proprietary bootloaders. Yeah, that's gonna be a no from me. But as for pinephones/librems, I have no clue because I never used them, but from what I've heard they're a scam. The only smartphones/dumbphones you should be using are raspberry pi smartphones w/ kali linux installed and arduino phones. But then the next question is snooping on a network level by your carrier as well as identification through radio masts for 5G. Now it's all VoLTE spyware and they discontinued 2G and 3G. Reminds me of that Nashville bomber guy who was telling the truth about radiation from cellular signals. This I don't know how you can fix, but I'd be interested to hear a response from it.
>where's your proof that GrapheneOS is malware?
From the horse's mouth:
>GrapheneOS aims to provide reasonably private and secure devices. It cannot do that once device support code like firmware, kernel and vendor code is no longer actively maintained. Even if the community was prepared to take over maintenance of the open source code and to replace the rest, firmware would present a major issue, and the community has never been active or interested enough in device support to consider attempting this. Unlike many other platforms, GrapheneOS has a much higher minimum standard than simply having devices fully functional, as they also need to provide the expected level of security. It would start to become realistic to provide substantially longer device support once GrapheneOS controls the hardware and firmware via custom hardware manufactured for it. Until then, the lifetime of devices will remain based on manufacturer support. It's also important to keep in mind that phone vendors claiming to provide longer support often aren't actually doing it and some never even ship firmware updates when the hardware is still supported by the vendors...
>GrapheneOS also has high standards for the privacy and security properties of the hardware and firmware, and these standards are regularly advancing. The rapid pace of improvement has been slowing down, but each hardware generation still brings major improvements. Over time, the older hardware starts to become a substantial liability and holds back the project. It becomes complex to simply make statements about the security of the project when exceptions for old devices need to be listed out. The project ends up wanting to drop devices for this reason but has always kept them going until the end-of-life date to provide more time for people to migrate.
Source:
https://grapheneos.org/faq
>linux-hardened-docs:linux-libre-hardened-docs::[semifree] docs comes from nonfree linux-grsec kernel
>linux-hardened-headers:linux-libre-hardened-headers:fsf:linux_ linux-backports-modules.2A_ linux-ubuntu-modules:[semifree] blobbed source
>linux-hardened:linux-libre-hardened:fsf:linux_ linux-backports-modules.2A_ linux-ubuntu-modules:[semifree] nonfree blobs and firmwares
Source:
https://git.parabola.nu/blacklist.git/plain/blacklist.txt
Then you also have the ARM Trustzone backdoor along with their proprietary bootloaders. Yeah, that's gonna be a no from me. But as for pinephones/librems, I have no clue because I never used them, but from what I've heard they're a scam. The only smartphones/dumbphones you should be using are raspberry pi smartphones w/ kali linux installed and arduino phones. But then the next question is snooping on a network level by your carrier as well as identification through radio masts for 5G. Now it's all VoLTE spyware and they discontinued 2G and 3G. Reminds me of that Nashville bomber guy who was telling the truth about radiation from cellular signals. This I don't know how you can fix, but I'd be interested to hear a response from it.
