Vanadium version 147.0.7727.101.0 released:
github.com/GrapheneOS/V...
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
Forum discussion thread:
discuss.grapheneos.org/d/34177-vana...
#GrapheneOS #privacy #security
You can use an app to do an initial import of your contacts or to keep them synced. Proton has a suite of apps with end-to-end encryption including contacts sync as one example. If people really want they can use Google's contacts sync on GrapheneOS but we recommend a more private service.
[...] high usability. We're gradually making replacements for more Google services apps rely on. Location services, network-based location, geocoding and more has already been replaced and much more is coming.
Contrary to what's often claimed, GrapheneOS is far more usable and requires far less sacrifice compared to other alternatives. Providing far better protection against sophisticated exploits isn't at the expense of that. Our opt-in sandboxed Google Play compatibility layer combines privacy and [...]
[...] the Camera, Microphone and other permissions too. Our major improvements to exploit protections are there to protect user privacy. Privacy depends on security and that's why we heavily work on security too.
We're continuing to work on improving privacy, security, usability and app compatibility for all of our users. Contact Scopes, Storage Scopes, per-app Sensors toggle, VPN leak protection and many other features we provde are very important privacy protections. We're building alternatives to [...]
[...] with a better permission model increasingly addressing being coerced to grant access. GrapheneOS has many users with little technical knowledge and isn't hard to install or use.
We're building GrapheneOS to protect everyone's privacy and security. It's aimed at widespread adoption and is highly usable. It's compatible with the vast majority of Android apps. It has major privacy benefits for every user including stopping a lot of data collection by apps and services [...]
[...] whole. It isn't only embedded devices but also desktops, mobile devices and servers being used as part of these botnets. It isn't only people with these insecure devices who are harmed. It can get much worse.
Growing numbers of internet connected devices are incorporated into botnets. This harms the privacy and security of the internet as a whole through heavily pushing it towards centralization behind services such as Cloudflare. Insecure devices without security patches harm the internet as a [...]
[...] development. For most computing devices, defense is increasingly far behind offense. iOS and GrapheneOS are exceptional cases not representative of degrading privacy and security across computing devices.
Attackers continue improving their exploits of privacy and security weaknesses. Commercial exploit tools are increasingly widely deployed for broad attacks. Software has a very high density of privacy and security vulnerabilities. LLMs are accelerating both vulnerability discovery and exploit [...]
[...] heavily involve competition between attackers and defenders. Most defenders are making little progress and falling increasingly far behind.
GrapheneOS provides a massive upgrade for privacy and security over the standard Android Open Source Project. GrapheneOS is nowhere near good enough and we have an enormous amount of work to do improving both. Our work is an ongoing process and doesn't have an end point. Privacy and security [...]
[...] exploits of those happening on a large scale. Operating systems, browsers and other apps need to do a much better job protecting users. Enormous progress is needed on both privacy and security.
Privacy and security on computing devices need to become far stronger to protect people from pervasive violations of their rights. Users have their privacy pervasively violated by corporations, criminals and governments. There are endless privacy and security weaknesses in software with [...]
The editors of Wired (@wired.com) appear determined to turn an article about GrapheneOS into a hit piece. Wired contacted James Donaldson, CEO of Copperhead, and appears to be treating his thoroughly debunked fabrications about the history of the project as their primary source. This is outrageous.
@katie-drummond.bsky.social At the last minute, the story was changed to incorporate many unsubstantiated claims about the history of the GrapheneOS and the founder without verification. The main source is one of the primary perpetrators of years of harassment which WIRED is aware is happening.
@katie-drummond.bsky.social It's not a credible source of information about GrapheneOS and can be thoroughly debunked. Even presenting it as an alternate narrative is wrong considering how easily it can be debunked. The same goes for including inaccurate claims sourced from harassment content, etc.
@katie-drummond.bsky.social Making an article about GrapheneOS where the history is primarily sourced from a person who has been plainly exposed as fabricating these claims both publicly and as part of his failed legal attacks is wrong. Adding all of this in at the last minute makes it even worse.
@katie-drummond.bsky.social Since we were repeatedly led to believe the article wasn't covering these things, we haven't had an opportunity to provide not only our side of the story but evidence and witnesses to prove these claims are fabrications. The primary source is someone trying to harm us.
@katie-drummond.bsky.social Including these things at the last minute with no verification or proper opportunity for us to debunk it is wrong. We were repeatedly reassured and promised this wasn't going to be covered. We were misled and we can prove that publicly with our history of communications.
@katie-drummond.bsky.social Aside from that, sourcing inaccurate claims from harassment content with no attempt at verification prior to publishing it is also wrong. It's highly inappropriate to base an article around unsubstantiated claims towards someone already being harassed at an extreme level.
@katie-drummond.bsky.social WIRED shouldn't be giving a platform for people to make unsubstantiated claims about an open source developer and open source project with no attempt at determining the truth. The claims being made are very clearly false and the legal conflict has clearly demonstrated it.
They heavily pushed their narrative on Wikipedia and then laundered it back into Wikipedia from news organizations believing what it says and using it as the basis for how they describe GrapheneOS and the project's history. WIRED Is headed towards making things dramatically worse with this.
It won't matter what security conscious people largely believe if WIRED publishes a story pushing these false narratives and makes it mainstream. Copperhead was already highly success in pushing their false narratives on Wikipedia through inaccurate edits and low quality news sites paraphrasing it.
@katie-drummond.bsky.social If Wired wants to cover this, it should be done properly. The main person being used as a source has openly aimed to destroy GrapheneOS and the life of our founder for years. They're lying about nearly everything. There's extreme harassment towards our team already.
@katie-drummond.bsky.social We'd greatly appreciate if you could talk to us. A light story by a junior journalist shouldn't be having highly controversial stuff shoved into it at the last minute without verification. It's primarily sourced from someone we're in the late phases of a lawsuit against.
We're posting this to reach someone at Wired who can pause this and have it handled with the appropriate care it needs. Sourcing an article about GrapheneOS from a person who has spent years trying to harm us and is losing a legal battle including having to withdraw these claims makes no sense.
Wired wants a clickbait article with lots of controversy and isn't accepting it without it. We spent months talking to the author of the story and received repeated assurances about how it was being approached. The author of the article was clearly pressured into making it an inaccurate hit piece.