Avatar
Valley Joe
1963a361a5841aaf2764936caf750f2e0566e10ec20224c6a51218c8abb25ac0

You weren't toldn to blindly trust the hardware. Using GrapheneOS is advised because the hardware can't be trusted.

The guidance given was stating that regardless of a device having 'kill switches' you still have to trust the hardware.

Specifically regards the Pinephone for example.

You cannot avoid trusting the hardware manufacturer for the SoC, the overall device and other trusted components.

Pinephone uses components with serious security issues and doesn't configure the SoC securely. They can't provide the standard expected security updates and the device is missing most hardware-based security features like those depending on a secure element and verified boot.

Hardware kill switches don't make up for having lots of security issues in hardware, firmware and especially software. Using an OS with nearly non-existent application security model, lack of modern exploit mitigations, lack of memory safe language adoption, etc. is not progress.

Android Open Source Project is a Linux distribution, as is GrapheneOS. A substantial portion of our work is on the Linux kernel. We've made significant upstream contributions to the Linux kernel project with the bugs we've found, patches we've provided and code review.

An operating system doesn't need to use systemd, glibc, gcc/binutils, pipewire/pulseaudio, Wayland/X11, GNOME/KDE, etc. to be Linux. Linux is a kernel.

The radios and other peripheral components included in the devices we support are isolated. The common claim that cellular radios aren't isolated is completely false. What sets GrapheneOS apart is that regardless of any 'backdoors' (hypothetical until proven otherwise) is that, like RCE exploits similar to those recently discovered/patched by Googles Project Zero in the baseband, actors will still need to have an OS based exploit on top to compromise your data etc. No other OS provides the level of protection that GrapheneOS offers.

No external actor has ever claimed to have compromised a GrapheneOS Pixel. This includes third party state affiliated operators such as Cellebrite. They however are focusing a lot on older generation Qualcomm based Pixels and may have something in the next 12-18 months. Which is again why we advise uaing a modern OEM hardware firmware/driver supported device. The likes of which Pine/Libre are not.

GrapheneOS is killing it. Much respect.

Thanks, I appreciate you reaching out. I managed to get most of what I need. I'm still adapting but also practicing being more minimal. I am definitely enjoying it. I always appreciate a learning experience! 😅

Officially on graphene os 😈

For anyone interested; i use to make music (rap)...

I made this 9 yrs ago. I did the beat and lyrics and mix/mastered it myself on fl studio. An old friend of mine filmed and edited the video.

Would be glad to read your opinions! A talent i know ive slept on...

https://youtu.be/WcpX1mB3rUI

The original txn was overpaid, i clicked the red arrow and it led me to this page saying too low now? I dont understand. Why did it go from a to b to c? Is there anything i can do about it or do i have to just wait?

Thanks! I found it but i dont really know what to do with this information...says i overpaid 2x. No rbl...no eta...no locktime...

I appreciate it! Not too familiar with this stuff, i clicked the link, clicked new account and i just get this screen which gets me nowhere...im confused.

Dont watch it lol i never noticed it. Only see shorts. I did see Victor talking about implementing it tho