Final's avatar
Final
final@stacker.news
npub1hxx7...g75y
Community & Support @ GrapheneOS Foundation. Posts my own and not endorsed by my employer. AI slop and Nostr DMs ignored. Email: final@grapheneos.org Matrix: f1nal:grapheneos.org
Final's avatar
AmberFinal 1 week ago
Our port to the Pixel 11 series was nearly complete after around a week of the devices being launched. It had to be cancelled due to lack of MTE support. Android 17 QPR2 has added MTE support for the Pixel 11 series and we've confirmed it works with #GrapheneOS with our QPR2 port. Our port to Android 17 QPR2 is nearly complete. Pixel 11 support can be added after we launch it for the other devices. Completing Signature 27 support is our main priority after QPR2 but we essentially finished Pixel 11 support a long time ago so we can ship that after QPR2 too.
Final's avatar
AmberFinal 3 weeks ago
Had a discussion with the @White Noise team about how they could improve especially in a security and privacy standpoint. The post and article below discuss a small part of the efforts made. These provide substantial security improvements while having no added overhead or friction to the user. If your application handles media, it's important that functionality is sandboxed and designed in a memory safe language. White Noise currently isolates image decoding in this way but now this has also been expanded to animated images as well. You can find out more below. Memory tagging (MTE), a ARM hardware exploit protection used heavily by GrapheneOS and latest generation iPhones are now opted in the app manifest. This makes it unable to be disabled in GrapheneOS and also enables it for capable phones enrolled in Android's Advanced Protection. The issue tracker also now tracks working on a few improvements, including adding this sandbox for other types of attachments too. I've also discussed on a improving accessibility features. View quoted note →
Final's avatar
AmberFinal 3 weeks ago
I hate talking about general security and privacy advice on social media. It's a common tactic by charlatans to make them appear trustworthy for saying basic things. But, this has to be said. An often overlooked detail of wallet company data breaches is the collateral damage to the customer. Your compromised information can be used to target you in additional breaches, such as for phishing emails or even credential stuffing. Everyone talks about the risk of real world harm but it's also your cyber health at stake. Never reuse your credentials and keep information you provide non-attributable where there is no consequence to do so. If you are running a business involved in decentralised finance, whether it be as a product or accepting a mode of payment, you must understand you will have a target on your back, all the time, with threat actors who work more hours than you do and also more likely to be held unaccountable should they succeed with their goals. You have to assume you WILL get a data breach eventually. No organisation is perfect. If you aren't ready to continuously put in an effort to security, quit while you can to protect your customers. Basic mistakes are the most overlooked, and often the most dangerous. There is never a wrong time to review your posture. Don't let your impacts be amplified by technical failures you only were able to discover after the breach happened.
Final's avatar
AmberFinal 1 month ago
I was sent this article showing what appears to be a document by Cellebrite that was marked as confidential describing a recent Advanced Unlocks capability. The document is a few months old. This capability allegedly uses a dedicated appliance with a stated range of about 8 metres. Given the range they suspect it is to do with Bluetooth. There is no mention of iPhones with MIE (hardware memory tagging, iPhone 17, Air and later) and it is not on the latest iOS version, which could suggest a patch. Take a look for yourself: image It would make sense that Cellebrite would choose to have capabilities like this one under development. When devices increase their security against physical attacks, the exploit developers will move towards a path of least resistance to exploit other components or circumvent the security measures that prevent the extraction, as we see with their automatic reboot cancelling exploits for iPhones. Since forensics labs contain devices in isolation to prevent network access and remote wiping, it is possible to make simulated / dummy network environments inside those containers where advanced labs can attempt exploit delivery without the risks. The full document is available on request so it needs to be looked at further. While I do not intend to make discussion threads on this site regularly I think this is in a public interest.
Final's avatar
AmberFinal 1 month ago
Android 17 QPR1 was released for Pixels on September 15. It has a regression in the Pixel kernel driver tree causing stuttering, lag and outright freezes under memory pressure. It impacts #GrapheneOS too since we updated the firmware/drivers but now we fixed it ourselves. Google is taking increasingly long to implement and ship fixes for major issues in Android. We're having to expand our workload to include handling basic updates, testing and quality control for the entire operating system. We have rapidly growing resources and we'll handle it. Pixel 11 series received a bug fix release near the start of September 2026 with the 2026-09-01 patch level. That update wasn't Android 17 QPR1 and also doesn't include the September 2026 Pixel firmware/driver security patches. Perhaps they noticed this issue and cancelled it. Standard Android and Pixel updates have a severe issue with delays. It usually takes 2-3 months for Google to ship fixes for both severe regressions and security issues. They often get the issues fixed in days but the release engineering and testing process is completely broken. Major Android releases including Android 17 QPR1 go through a long public testing period. It typically takes Google at least around 4 to 6 weeks to ship fixes for even the most severe issues. They either cancel the release (Pixel 11) or ship a broken release (everything else). Here's our fix for the awful Android 17 QPR1 regression causing lag, stuttering and freezes: https://gitlab.com/grapheneos/kernel_pixel_6.6/-/commit/ed5a9b87d99b45618fa55b3d6b53094cbd784b9f It's so severe that it's causing processes to be killed for stalls. It's unclear when Google will ship a fix for the issue. December 2026 wouldn't be a surprise. Due to this major Android 17 QPR1 regression, we've been looking into reducing memory usage. We found a way to eliminate most extra memory use from our secure spawning feature without any significant downsides. We'll try to get that huge improvement shipped before November 2026.
Final's avatar
AmberFinal 1 month ago
Our massive overhaul of the AOSP Messaging app has reached the Stable channel in our App Store after 3 releases. It's well on the way to becoming our own high quality #GrapheneOS Messaging app instead. There are still parts of the interface to overhaul including widgets and important features to add. Full support for RCS with all of the additional features it brings including proper group chats, media, opt-in read receipts and much more is going to be the largest project. We'll also be adding RCS end-to-end encryption via Messaging Layer Security (MLS) compatible with Google Messages and iOS. RCS support will be provided via an optional dependency on sandboxed Google Play for activation. In the longer term, we plan to make a fully standalone implementation requiring the carrier to support it. We probably won't make an alternate implementation of using Google's own system for this. Finishing the user interface overhaul, resolving many minor issues and adding important features including search are going to be the priority before getting to RCS. In the meantime, Google Messages is already fully supported on GrapheneOS including RCS with E2EE via MLS:
Final's avatar
AmberFinal 2 months ago
The @White Noise app transition to Kotlin and Jetpack Compose is really good. It's such a smooth, fast messenger. Even more so when I expect most apps relating to Nostr or BTC to be quite sluggish. There is a significant leap in usability for apps that are designed for a platform's native language and libraries.
Final's avatar
AmberFinal 2 months ago
When it comes to open source software, the corporates funded with state money who want to find vulnerabilities in your software for their advantage are often far more qualified, resourceful and committed to their objectives than the limited project developers are. You must be more cautious about having both a secure design and a secure implementation of the design of your software at the earliest possible stage of software development. This increases the time and effort to discover a vulnerability or can close out entire classes of vulnerabilities. We have seen how massive projects are weighted down from development standards of the late 90s and 00s that makes them have thousands of CVEs every release. https://www.phoronix.com/news/Linux-Kernel-CVEs-Nearly-2000 Check out some of the open-source AI tooling from Cellebrite to improve their workflows and automate in researching mobile device vulnerabilities. You can have opinions on the issues of LLMs (and I have several), but that comes with having to accept an adversary is accelerating how to harm you with that technology. View quoted note →
↑