What makes GrapheneOS Camera "secure"?

horde

I always wondered given "secure" is in its name, and imo the website and GitHub readme fails to highlight the security features it offers.

Dumdum

If I had to hazard any guesses, its probably along the lines of using modern memory safe languages (Java/Kotlin), no network connection, minimal permissions, no unnecessary bloat in the code, etc. in order to reduce as much attack surface as possible.

Johnnyloans

What makes GrapheneOS Camera "secure"?

An MBA would simply add secure to the name then double the price.

user63455

minimal meta data for each picture i think

SovereignCopper

user63455
horde

Those increase privacy, not security.

horde

found a post from official GrapheneOS's reddit post.

Our Camera app has various privacy features not present in Pixel Camera such as choosing an arbitrary storage location via the system file manager including app-based providers, recording videos without audio, muting audio dynamically, EXIF metadata stripping and more.

koocmit

SovereignCopper

Uploading to app-based providers enables direct upload to encrypted drives/volumes and filesystem-based software. This enhances security by encrypting photos locally without touching long term storage and avoids reliance on the camera these encryption tools provide which does not use proper APIs for quality.

Audio pause allows unaware users to not look around and upload clips on dodgy software or websites.

EXIF erasure as an easy toogle once option prevents dependency on EXIF stripping by messaging or image sharing services and/or partial EXIF erasure tools. It is also one less app on the device.

LeslieFH

What would make a camera secure (in a different manner) would be Content Credentials

https://glyndewis.com/blog/content-credentials

Which are actually available on stock Pixel 10 with Google Camera, can someone with Pixel 10 see if C2PA content credentials are also saved when using Google Camera on Graphene?

https://c2paviewer.com/articles/google-c2pa-pixel-10