Onno (VK6FLAB)

Anything and everything Amateur Radio and beyond. Heavily into Open Source and SDR, working on a multi band monitor and transmitter.

#geek #nerd #hamradio VK6FLAB #podcaster #australia #ITProfessional #voiceover #opentowork

  • 116 Posts
  • 306 Comments
Joined 1 year ago
cake
Cake day: March 4th, 2024

help-circle



  • I’m happy for you to quote me, but it does require that you actually quote what I said rather than what you think I said.

    Specifically I said:

    As far as I can tell, this post is an advertisement for Graphene OS. In real world terms, in my opinion, it adds nothing of substance to the privacy or security landscape.

    I did not state that Graphene OS didn’t add to the security landscape, though that’s how you interpreted it. Using “it adds nothing”, I was referring to the article linked in the OP. Could I have worded this better, sure. Did I say what you think I said, no.



  • Only one problem.

    Graphene OS only runs on 16 models of phone, Google Pixels. I’ve bought a dozen or so Google hardware devices over the years and I refuse to go through that abysmal experience ever again.

    Graphene OS might be amazing for all I know, but only supporting Google hardware makes it a joke in the real world outside of the Google fanboy bubble.

    As for deleting all the content of your phone, what makes you think that border security or law enforcement won’t access your data directly from your backup on Google’s cloud?

    As far as I can tell, this post is an advertisement for Graphene OS. In real world terms, in my opinion, it adds nothing of substance to the privacy or security landscape.










  • The real question is: Why?

    Here’s some answers to your question:

    1. Backup your data, nuke the drive, start again.
    2. chroot is the tool for the job. Backup your data before you accidentally nuke your drive.
    3. Shrink the partition and write a new one in the empty space, but backup your data before you accidentally nuke your drive.
    4. Connect an external drive, install on it, but backup your data before you accidentally nuke your drive.

    Finally, the reason that the wiki didn’t help is that the question is asked by either a person with not enough experience, or one who doesn’t need the wiki. This is a non trivial process and you should backup your data before you proceed, lest you accidentally nuke your drive.

    Edit:

    Also, anything you break can be fixed … but only if you have a backup.








  • The long list is the permissions as the Google Play store presents it.

    Below each app column shows empty if that permission is not required, or shows the permission if it is.

    I’m not sure how else you feel that this information should be presented.

    As far as vague goes, that’s my point. We grant permissions to launch an app with often little or no thought as to their interactions, like calender contacts and internet, or files and internet, or system permissions.



  • The spying, as you call it, at the OS level is one thing, the data leakage at an App level is a different thing entirely. The lengths that the Google Play store goes to hide permissions and the poor level of granularity, let alone the wholesale outsourcing of service critical applications and their “required” permissions is beyond the pale and not regulated, let alone enforced, in any way.

    For shits and giggles, you should check the permissions associated with your bank, telco, government, medical and other life essential applications, never mind the ones you use for entertainment.