ysnp

6 ms·

31.
by ysnp 3mo ago
Can you add CopperheadOS data 2014-2018 and AndroidHardening Project from 2018-2019?
32.
by ysnp 3mo ago
For what it's worth, strcat is the GrapheneOS founder so they will have a keen insight into current plans.
33.
by ysnp 4mo ago
Any promising mesh networks, radio networks or routing protocols worth looking into?
34.
by ysnp 4mo ago
It may be worth noting that GrapheneOS in most cases to date are not the initiators for conversations around extra device support. They do not control which mobile divisions and engineering teams can come to them and back genuine interest w
35.
by ysnp 4mo ago
The details of the partnership are mostly disclosed in the joint announcements but GrapheneOS has no say or influence on Motorola's stock Android image and policy. The main objective of the partnership is to do what you described in th
36.
by ysnp 4mo ago
I've not seen someone refer to a portion of GrapheneOS's mitigations as superficial and meaningless before. What might an OS with significant improvements to usable attack surface reduction and exploit mitigations look like to you
37.
by ysnp 5mo ago
They have commented elsewhere that any inclusion/exclusion criteria (if at all) should be transparent and collaboratively decided rather than arbitrary, monopolised or ineffectual/deceptive. They mention several times that people
38.
by ysnp 5mo ago
The requirements are not particularly stringent. It is more an embarrassing show from the rest of the Android OEMs that they don't meet basic standards like timely security updates and a decent support period.
39.
by ysnp 5mo ago
From what I've read I understand it is more like: /e/OS (recipient of EU funding) and iodéOS are European projects that have not been singled out by the French government in smearing despite them having the similar self-pro
40.
by ysnp 5mo ago
There are a lot of judgemental comments here criticising Daniel's character, responses and handling of what was likely a very trying and stressful period in their life. Barely any comments about the linked thread which is about Wired p
41.
by ysnp 5mo ago
Phantom Secure is directly named as one of the parties Donaldson was dealing with, with others being suspected: > Donaldson tried to make a deal with Phantom Secure, which ultimately didnt work out. Micay suspected other counterparties w
42.
by ysnp 6mo ago
It may be worth checking Motorola's OLED models in person (for example the Razr Fold, Razr Ultra and Signature) so see if their Flicker Prevention mode helps. I don't think any IPS models are likely to be supported in the first wa
43.
by ysnp 6mo ago
Having GrapheneOS preinstalled is an option they may discuss with Motorola. It is not the current plan. The current plan is that Motorola release their devices as normal, but some of the flagship devices in 2027 will support manual installa
44.
by ysnp 6mo ago
GrapheneOS will support future Morotola phones that meet a subset of their requirements, rather than existing phones. Less likely to be budget lines for now.
45.
by ysnp 6mo ago
DNSSEC is one of very few topics where voices I respect on security seem completely opposed (WebPKI depends on DNS vs. DNS security does not matter). Is there any literature that demonstrates deep understanding of both arguments? Why are th
46.
by ysnp 7mo ago
Is the case that captures all RF still planned for the productised Baochip?
47.
by ysnp 7mo ago
Can anyone from Motorola confirm that the form submission and time delay requirements will be removed?
48.
by ysnp 7mo ago
Hi daneel, what would you like GrapheneOS to do while you develop your own formally verified, open hardware, open source firmware/OS baseband processor they can use? Sit on their hands doing nothing or making the best of the least wors
49.
by ysnp 7mo ago
Since ~2023 all Motorola phones with Snapdragon SoCs (the ones most likely to support MTE as needed by GrapheneOS first) have been larger or equal to 6.5" screens.
50.
by ysnp 7mo ago
The Google Pixel has first-class support for alternate OSes (not custom firmware like a Chromebook). The OEM has to go out of their way to support avb_custom_key as mentioned in https://android.googlesource.com/platform&#x2F
51.
by ysnp 7mo ago
> are by incompetent/lazy/pressured devs who just throw in some library and don't even care that it leaks data to Google Even if I agreed with this statement, I don't understand why it is better to put limited/p
52.
by ysnp 7mo ago
The partnership is for future devices, rather than existing devices.
53.
by ysnp 7mo ago
They said they have access to security previews/patches but I have missed that they have full AOSP access now? Do you have a link?
54.
by ysnp 7mo ago
I am not a project member so I cannot speak for GrapheneOS, but maybe I can help clear up some misunderstandings. > insistence on not supporting MicroG leads to poor UX, The problem they are trying to solve is apps not working without t
55.
by ysnp 7mo ago
It took a while but congrats to Daniel Micay and GrapheneOS. Hopefully it is the first of a few (looking at you HMD, Sony, Samsung, Nothing). Will Motorola allowlist/whitelist GrapheneOS's avb key for green boot state? Does that h
56.
by ysnp 7mo ago
> some odd ideas about trust and PKIs. Can you explain what you mean?
57.
by ysnp 7mo ago
> I've had people tell me that nobody should use anything but GrapheneOS and stop supporting alternatives to throw all support into that because the others are "less secure" Without having an kind of authoritative knowled
58.
by ysnp 7mo ago
The point of GrapheneOS isn't improving a generic device's security, it's about setting an example for a highly private and secure OS. It's a FOSS project, so nothing stops a committed individual or community from using
59.
by ysnp 7mo ago
> Not everyone needs kernel hardening, or always E2EE (as with signal). If application processors and hardware crypto accelerators are good enough to make this invisible to the end user, then why not? Why not have everyone be on hardene
60.
by ysnp 7mo ago
I hope HMD reach out next: https://www.hmdsecure.com/

More ›