• 0 Posts
  • 2 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • expand@partizle.comtoPrivacy@lemmy.mlFuture of smartphone privacy
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    1 year ago

    There are many phones you can unlock/relock the bootloader on. That’s not why pixels are used. https://grapheneos.org/faq#future-devices

    "Devices are carefully chosen based on their merits rather than the project aiming to have broad device support. Broad device support is counter to the aims of the project, and the project will eventually be engaging in hardware and firmware level improvements rather than only offering suggestions and bug reports upstream for those areas. Much of the work on the project involves changes that are specific to different devices, and officially supported devices are the ones targeted by most of this ongoing work.

    Devices need to be meeting the standards of the project in order to be considered as potential targets. In addition to support for installing other operating systems, standard hardware-based security features like the hardware-backed keystores, verified boot, attestation and various hardware-based exploit mitigations need to be available. Devices also need to have decent integration of IOMMUs for isolating components such as the GPU, radios (NFC, Wi-Fi, Bluetooth, Cellular), media decode / encode, image processor, etc., because if the hardware / firmware support is missing or broken, there’s not much that the OS can do to provide an alternative. Devices with support for alternative operating systems as an afterthought will not be considered. Devices need to have proper ongoing support for their firmware and software specific to the hardware like drivers in order to provide proper full security updates too. Devices that are end-of-life and no longer receiving these updates will not be supported.

    In order to support a device, the appropriate resources also need to be available and dedicated towards it. Releases for each supported device need to be robust and stable, with all standard functionality working properly and testing for each of the releases.

    Hardware, firmware and software specific to devices like drivers play a huge role in the overall security of a device. The goal of the project is not to slightly improve some aspects of insecure devices and supporting a broad set of devices would be directly counter to the values of the project. A lot of the low-level work also ends up being fairly tied to the hardware."

    I think basically the higher standard of security on pixel devices allows/makes it easier to setup verified boot so you can relock the bootloader and retain that chain of trust it provides. Rather than an leave it unlocked in something like lineageOS where there is no verified boot and therefore all software isn’t coming from a trusted (verified) source.


  • what’s your reasoning behind ubuntu? Ease of use and maintenance? I’d argue rolling release distros that don’t require ppa’s or snaps are easier to maintain.

    Arch has been amazing in my experience. In the last 5 years I’ve just rsynced my arch install to the 5 different desktop/media pcs across my house with zero issues.

    If the DIY aspect of it is too much for you to handle (which really is only user required at install and the install guide is actually great and only requires you to read carefully to succeed) you can use something like endeavourOS that removes the arch install process and is still pretty close to arch. I’ve personally found arch (and endeavourOS but NOT manjaro) significantly easier and less annoying to maintain than ubuntu and even debian that I run on my servers.

    Also, I have never used it but ArcoLinux is an arch based distro that has a lot of built in features that allow easy desktop environment switching and a lot more. The main guy (Erik Dubois) has a youtube channel and a real passion for teaching people. There is a wealth of information there.