strcat

52 ms·

571.
by strcat 3y ago
We want to support other devices and consider this the main blocker because Exynos is not widely used outside Samsung and Snapdragon is better at overall security than MediaTek. Qualcomm dropped the ball on MTE but they're quite good a
572.
by strcat 3y ago
Ideally, but it's not realistic to convince them to do that yet. It is very realistic to convince them to use asynchronous MTE for the base OS and their own apps. The more secure asymmetric MTE is a much harder sell, but would be way n
573.
by strcat 3y ago
They have already fixed nearly all the crashes in the base OS. The issues we face are almost entirely regressions in new versions. They fix them consistently but they aren't stopping the regressions getting into releases because they d
574.
by strcat 3y ago
We provide a concrete list of requirements at https://grapheneos.org/faq#future-devices which we're trying to extend with as much of the unstated requirements as possible. Quality of implementation matters though.
575.
by strcat 3y ago
Pixels only support digital USB-C audio output. USB-C also has a lot of compatibility issues beyond this from non-spec-compliant cables, peripherals, chargers, ports, hubs, etc. Google and Apple have a perfectly good USB-C DAC which is far
576.
by strcat 3y ago
The hardware requirements are listed here: https://grapheneos.org/faq#future-devices Pixels are the only Android devices meeting these requirements at the moment. Other devices do not currently come close to meeting these s
577.
by strcat 3y ago
We're going to provide other network location providers including local ones. The existing ones aren't up to our standards which is why we didn't simply bundle them. In theory, we could also support toggling on the less priva
578.
by strcat 3y ago
You're correct that it was my position at one point, but it was around 4 years ago and a lot has changed. We did used to say iPhones were more secure from 2014-2019 but it started shifting in 2020 and then especially in 2021-2022 as AO
579.
by strcat 3y ago
Extended support is very difficult to provide in a way that fits into the expectations we have for robustness, app compatibility and security beyond the lack of incomplete patches. For example, it would be easiest for us to move the Pixel 4
580.
by strcat 3y ago
They can have up-to-date AOSP but a significant portion of the OS consists of the driver, HALs, non-GKI kernel tree, etc. Android security patch level is meant to cover all of that. They're using it in a way that's not permitted f
581.
by strcat 3y ago
MTE can provide strong deterministic security properties through reserved tags. Anything not tagged has a 0 tag and anything tagged has a non-0 tag by default since it's a default exclusion. You can exclude other tags statically or dyn
582.
by strcat 3y ago
MTE is actual hardware enforced protection, but simply doesn't have enough bits to reliably detect memory corruption in the general case. It's able to provide a lot of useful deterministic security properties via reserved tags. No
583.
by strcat 3y ago
> How does MTE compare to CHERI? MTE an CHERI use a similar approach but MTE doesn't have large enough tags to provide strong security in the general case. MTE can provide strong deterministic security properties through reserved ta
584.
by strcat 3y ago
We have extended support for end-of-life devices but discourage using it and make it clear that it's insecure. We dislike needing to provide it and many people don't realize we do because we make sure not to hype it up and instead
585.
by strcat 3y ago
We didn't propose enabling MTE for apps not opting into it any time soon. We proposed enabling it for the base OS by default. Pixels are already testing with HWASan and MTE so there are few issues found by it in the base OS. Enabling i
586.
by strcat 3y ago
MTE is an optional feature for ARMv8.5 and is only available via ARMv9 in practice. Snapdragon doesn't provide it but they told us they're likely going to add it by 2025/2026. Pixel 8 and Pixel 8 Pro are the main option with
587.
by strcat 3y ago
Yes, it's very possible that the EU will regulate this due to antitrust concerns and they are actively looking into it.
588.
by strcat 3y ago
> The Security Additions, Sandboxing Setup and a bit of slowness due to the hardened memory allocator are more annoying than just using plain android You can opt-out of secure app spawning if you deeply care about the small latency added
589.
by strcat 3y ago
Google Pay doesn't allow using a non-Google-certified OS. It checks this with the Play Integrity API. It won't be possible to spoof in the long term, so we don't pretend to be an insecure old device without hardware attestati
590.
by strcat 3y ago
> the recommended method involves using Web USB in Chromium which is meant to be easier for non-technical people but I couldn't get it to work. There's a bug on many Linux distributions which was fixed in fwupd but is still pre
591.
by strcat 3y ago
> Is it very challenging to install Graphene OS? It's very easy to install with the web installer. https://grapheneos.org/install/web You can buy a device with it, but nearly anyone can use the web installer. I
592.
by strcat 3y ago
Please read https://news.ycombinator.com/item?id=39672701 . My actual position is that current Pixels with the stock OS and iOS have comparable security. iOS has overall better privacy including privacy from apps. It's
593.
by strcat 3y ago
No, that's not correct and what you're stating about my views or what I have said is not correct. > Daniel Micay himself said that iphones are one of the best choices from a security perspective, GrapheneOS closing the gap. I h
594.
by strcat 3y ago
Pixels with the stock OS have comparable security to iPhones already. This thread is also about MTE which doesn't exist in Apple's hardware yet. The whole point of GrapheneOS is providing far better privacy and security than that
595.
by strcat 3y ago
> GOS's limited device support is disappointing, but I understand their reasoning. Our specific hardware requirements are listed at https://grapheneos.org/faq#future-devices . It's a very concrete list of requir
596.
by strcat 3y ago
GrapheneOS provides extended support for end-of-life devices but we strongly discourage using our extended support releases. You can see we do that from https://grapheneos.org/releases and https://grapheneos.org&
597.
by strcat 3y ago
GrapheneOS provides extended support for end-of-life devices but we strongly discourage using our extended support releases. You can see we do that from https://grapheneos.org/releases and https://grapheneos.org&
598.
by strcat 3y ago
No, that's not at all the case. We made our own MTE implementation for our hardened_malloc project with significantly stronger security properties. We had to fix multiple bugs in the OS and with Chromium's MTE integration to enabl
599.
by strcat 3y ago
It's based on communication with them. We've had it directly communicated to us. There are also multiple Google security engineers/researchers who liked/retweeted our posts. Google has stated the Pixel 8 is the first pla
600.
by strcat 3y ago
> The tradeoff isn't just memory use or performance -- it's also user-facing crashes that weren't present before. That is likely the bigger factor in deciding whether or not to enable the feature. We're only proposing

More ›