In the image they posted it showed GrapheneOS AFU (after first unlock) and Unlocked. Brute force methods are not viable and the filesystem is only accessible while the device is unlocked and is running a certain version apparently.
So, pretty secure while it’s locked but seems resilient even unlocked.
It’s great that a phone is secure when it’s locked but issues while the phone in use seems to get talked about less.
I’ve used graphene before and it does a great job of implementing some robust security measures that are active during regular use - just saying I wish there was more of a focus on this from this POV.
What do you mean here? If a digital forensics team, police etc gets their hands on your phone while it’s unlocked there really is nothing that can be done, unless you have some sort of killswitch attached to the USB port lol
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Now I hope they improve on their communication and stop being super aggressive. (Posted this already but my previous comment is gone).
This is cool and all.
It’s great really.
But I guess I’m more concerned with safety, privacy, and security while a device is running than when it’s locked.
Which I know grapheneOS does a good job of. So I’m not being critical, just chiming in.
In the image they posted it showed GrapheneOS AFU (after first unlock) and Unlocked. Brute force methods are not viable and the filesystem is only accessible while the device is unlocked and is running a certain version apparently.
So, pretty secure while it’s locked but seems resilient even unlocked.
Yeah that aligns with what I know about it.
It’s great that a phone is secure when it’s locked but issues while the phone in use seems to get talked about less.
I’ve used graphene before and it does a great job of implementing some robust security measures that are active during regular use - just saying I wish there was more of a focus on this from this POV.
What do you mean here? If a digital forensics team, police etc gets their hands on your phone while it’s unlocked there really is nothing that can be done, unless you have some sort of killswitch attached to the USB port lol
Sorry if I was unclear - I meant accessing/exfiltrating data / C&C type shit while you’re using the phone through whatever means.
They do though. Here’s a couple off of the top of my head:
Several of those are things theyve contributed back to aosp
deleted by creator
This isn’t even new… It’s a photo from GrapheneOS forum… From a while ago like 2024.
https://discuss.grapheneos.org/d/14344-cellebrite-premium-july-2024-documentation
This is a more recent version and includes the Pixel 9. You can see that when you compare the matrices.
Tbh the photo of the computer monitor was not legible enough for me to notice.