Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
strcat
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
27 ms
·
361.
▲
by
strcat
1y ago
https://news.ycombinator.com/item?id=44780766
362.
▲
by
strcat
1y ago
https://news.ycombinator.com/item?id=44780766
363.
▲
by
strcat
1y ago
This post is a German translation of the Kiwi Farms thread personally targeting me with harassment based around fabricated stories, spin and completely unsubstantiated claims/theories. The post was made by a someone after they made sim
364.
▲
by
strcat
1y ago
It's not a security upgrade over current AOSP overall and is definitely not a port of GrapheneOS to other devices. Someone could make a partial port of GrapheneOS to other devices but this is not that. > but includes security backpo
365.
▲
by
strcat
1y ago
Memory tagging isn't Pixel exclusive anymore. Fairphone doesn't lack baseband isolation since it's a standard Snapdragon feature. Fairphone is worse than many OEMs at providing the standard security features and patches. Repe
366.
▲
by
strcat
1y ago
Yes, but they need to meet our official requirements: https://grapheneos.org/faq#future-devices We're working with a major Android OEM and it's going well so far. It's still in an early phase where they'
367.
▲
by
strcat
1y ago
> Even Graphene OS reported that they're in talks with some vendor... Have there been any updates towards that? The startup we were working with before went bankrupt. In June, we started working with a major Android OEM which has pr
368.
▲
by
strcat
1y ago
> Theoretically Fairphone + e/OS may have been an option, but the security is crap. Lack of current privacy/security patches and the current privacy protections in Android means having very poor privacy too. There's no equ
369.
▲
by
strcat
1y ago
MTE mainly exists to catch the initial memory corruption in the first place rather than to protect specific targets from memory corruption. The current limitation of only having 16 possible tag values makes the fallback to probabilistic pro
370.
▲
by
strcat
1y ago
We use the standard reserved tag (zero) for freed data but we also dynamically exclude the previous non-free tag for the current slot and the most recent adjacent non-free tags (i.e. the current tag for the adjacent slots or the previously
371.
▲
by
strcat
1y ago
https://news.ycombinator.com/item?id=44776816
372.
▲
by
strcat
1y ago
Memory tagging is an important security feature. The way GrapheneOS uses it is explained at https://news.ycombinator.com/item?id=44678704 . Only having 16 possible tags doesn't impact the deterministic protections we pr
373.
▲
by
strcat
1y ago
> Note I described MNT reform as -mostly- open It's near completely closed source hardware. The SoC providing nearly the whole core system is fully closed source. An open source boot chain after the closed source early boot doesn&#x
374.
▲
by
strcat
1y ago
> The entire point of Replicant was replacing all mutable closed software, firmware, and blobs with open alternatives and they did to a large degree succeed at that isolated goal. They did not replace firmware with open alternatives. Not
375.
▲
by
strcat
1y ago
> I am not qualified to actually diagnose you with anything You should stop calling be insane, delusional, etc. It's quite easy to stop. > yet also you seem stuck in a revisionist history narrative that people were trying to rip
376.
▲
by
strcat
1y ago
> PPC64le Talos II workstation which has a fully open hardware motherboard and open CPU architecture? The ISA is open source, not the whole CPU architecture and design. There are older open core designs from IBM but that's a differe
377.
▲
by
strcat
1y ago
> creating a separation between hardware trust and OS trust Typical Android devices have fully open source kernel drivers. There are usually dozens of closed source libraries in userspace such as the well known Mali GPU driver library. C
378.
▲
by
strcat
1y ago
This doesn't mean it's open hardware or that it has open firmware. It has a closed source SoC and many other closed source components. Those components are closed source hardware with closed source firmware. Snapdragon uses a fork
379.
▲
by
strcat
1y ago
No, someone took an out-of-context screenshot of information conveyed by the GrapheneOS account and misrepresented it. We were describing what a source we described as unreliable told us based on what they said was a leak from Google. You c
380.
▲
by
strcat
1y ago
> Plenty of laptops exist you can get away with running fully open source and auditable firmware, and a few that are mostly open hardware too, by the MNT Reform team. MNT Reform has a regular closed source ARM SoC as the main component a
381.
▲
by
strcat
1y ago
> Phones -are- optional and if you think otherwise you might be an addict. Smartphones are small portable computers. You're using a similar computer to make posts on social media platforms including Hacker News. > It is better in
382.
▲
by
strcat
1y ago
Battery life improved a lot with the 9th gen Pixels other than the Pixel 9a due to the dramatically more efficient cellular radio. Set it to "4G" or the GrapheneOS added "4G only" as the cellular network mode and you sho
383.
▲
by
strcat
1y ago
> Multiple fully or mostly open hardware computers exist. They just cannot run android. No, not really, and there's no reason those can't run AOSP. > MNT Reform It has a typical closed source ARM SoC and other components. Th
384.
▲
by
strcat
1y ago
> CalyxOS, which not only suffers from the same "problems" you criticize in GrapheneOS, but is also inferior in every way when it comes to security and privacy? CalyxOS lacks the current driver/firmware patches and isn
385.
▲
by
strcat
1y ago
AOSP having a regression causing a timestamp to be added somewhere isn't a reasonable justification for blocking security updates. No system without the ability to investigate the cause and determine if it's okay would be reasonab
386.
▲
by
strcat
1y ago
> GrapheneOS (like all modern AOSP based ROMS) can literally not function with just the open source code. It does not inherently require any closed source code or hardware. Real world hardware is closed source and requires tons of closed
387.
▲
by
strcat
1y ago
> some things about the UX in this is so bad, which i love because it discourages me from using the phone more. every time i end a phone call i struggle hanging it up. i don't know how to go forward in the browser because the swipe
388.
▲
by
strcat
1y ago
See https://news.ycombinator.com/item?id=44687530 . > Although it is conterintuitive to use a Google device to get away from Google The purpose of GrapheneOS is privacy and security, not specifically avoiding Google, whic
389.
▲
by
strcat
1y ago
> I'd like to switch phones soonish and was looking at the fairphone 6 with /e/OS but feel deterred by its mid range specs which would probably limit its longevity. I would like to get away from google. Fairphones lack pro
390.
▲
by
strcat
1y ago
Our hardware requirements are listed at https://grapheneos.org/faq#future-devices . There are a small subset of other devices with at least nearly all of the security features we require. However, those devices either don&#x
More ›