Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ysnp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
61.
▲
by
ysnp
7mo ago
> I don't think this has changed at all since. There is common knowledge to suggest that it is not the case (or maybe is no longer the case): > Mainstream smartphones do not provide DMA access from the baseband to the applicatio
62.
▲
by
ysnp
8mo ago
I missed this in the bustle of this thread but that's fantastic news. Hugely appreciative of the work yourself and your team at GrapheneOS are doing and it is great to hear it will be expanding/growing too.
63.
▲
by
ysnp
8mo ago
It is not the job of GrapheneOS to lower their standards and deplete their resources supporting every phone under the sun. We already have LineageOS for that. I would rather not be snarky but I don't understand why people keep blaming
64.
▲
by
ysnp
8mo ago
> Also some people (me) value independence from Google more than the highest degree of security (which relies on Google hardware). The requirements are indeed minimal. I have no problem with your valuing independence from Google, but p
65.
▲
by
ysnp
8mo ago
The founder, afaik, not just a developer. Tor Browser seems to be a project that requires multiple full time developers. I don't think GrapheneOS have the resources right now to do this alongside their OS development, device support an
66.
▲
by
ysnp
8mo ago
>GOS lulls users into complacency by focusing on the security angle only and encouraging users to install sandboxed GApps: https://grapheneos.org/usage#sandboxed-google-play Sandboxed-Google-Play is not encouraged or pro
67.
▲
by
ysnp
8mo ago
>GrapheneOS does not have an equivalent of ublock origin built into the OS which I'd consider step 1 of fighting the problem. Content filtering is built into the browser. GrapheneOS have always maintained that you cannot prevent an
68.
▲
by
ysnp
8mo ago
>Not everyone is running from an intelligence agency or cellebrite border checkpoints OK, but would it be such a bad thing if most people's personal devices were pretty damn resilient to mercenary spyware by default? I really don&#x
69.
▲
by
ysnp
8mo ago
I just want to note that I believe the default setting is that data is disabled for the USB port when the phone is locked except after a reboot (before unlocking the phone for the first time), so if you break your screen you have the opti
70.
▲
by
ysnp
8mo ago
GrapheneOS isn't rooted. Did you mean that your corporate MDM app doesn't run on non-certified OSes?
71.
▲
by
ysnp
8mo ago
From a quick look online it may be the Pixel 8 https://www.gsmarena.com/google_pixel_8-12546.php at 150.5 x 70.8 x 8.9 mm based on recommended devices.
72.
▲
by
ysnp
8mo ago
https://www.kuketz-blog.de/grapheneos-der-goldstandard-unter...
73.
▲
by
ysnp
8mo ago
I can understand the frustration, but it wouldn't be right to say they 'restrict themselves to Pixels'. They believe strongly in a standard for privacy/security of people's personal devices, and unfortunately only P
74.
▲
by
ysnp
8mo ago
"Break free from Google," is not GrapheneOS's motivation, just so people are aware. That is the blog writer's motivation.
75.
▲
by
ysnp
8mo ago
You should probably be asking Android OEMs why the requirements listed here https://grapheneos.org/faq#future-devices are unreasonable.
76.
▲
by
ysnp
8mo ago
Small correction, GrapheneOS are not making them. They are partnering with an existing large OEM to ensure one or a number of future flagship devices meets their security, privacy and support requirements.
77.
▲
by
ysnp
9mo ago
Could you elaborate a bit on why you've judged it as privacy theatre? I'm skeptical but uninformed, and I believe Mullvad are taking a similar approach.
78.
▲
by
ysnp
10mo ago
>Your project's team has regularly engaged in very underhanded attacks on ours despite us never doing anything to you. We have archives of it. What team are you talking about? JMP/Cheogram? This is the first I've heard of
79.
▲
by
ysnp
10mo ago
Well, in the much longer term they have usually mentioned they would like to use a more secure/private foundation (more in the direction of Qubes/Redox/Fuchsia) with a compatibility layer for Android apps if they have the res
80.
▲
by
ysnp
10mo ago
Hopefully you don't mind me asking this question, but didn't you work with people who managed to do exactly what you are suggesting with a fairly small team at Essential for a few years?
81.
▲
by
ysnp
10mo ago
This depends what you mean by 'issues with NFC'. My understanding is that Google require an OS that is blessed by them for contactless payments in Google Wallet to work. That restriction applies to all alternative operating system
82.
▲
by
ysnp
10mo ago
It's inaccurate that GrapheneOS fully endorses Signal and Tor. The GrapheneOS founder was blocked by Moxie (when they were still leading the project) for criticising their approach. They have also warned countless times about the limit
83.
▲
by
ysnp
10mo ago
Reducing waste is very important, but I think this is something you need to take up with the Android OEMs. GrapheneOS can't really do anything about the fact that Android OEMs stop supporting the device and allow vulnerabilities to go
84.
▲
by
ysnp
10mo ago
I don't think that is a consideration for the project. Their OEM partnership also includes supporting a current generation Snapdragon SoC which seems to feature an integrated modem. > A component being on a separate chip is orthogon
85.
▲
by
ysnp
10mo ago
It's interesting because the OEM is quite likely to be in the 'Avoid at all costs!' bucket based on current information.
86.
▲
by
ysnp
11mo ago
Can you detail the current metadata and security problems with CryFS? Do they also extend/apply to securefs?
87.
▲
by
ysnp
11mo ago
>Think mesh networking, resilient ad-hoc application clustering, non-Internet P2P, like Freifunk but everywhere. (if dumbed down) What's are the gaps in features and functionality between what you're describing and what might b
88.
▲
by
ysnp
1y ago
On bundling apps in general: https://grapheneos.org/faq#bundled-apps . For the calendar app particularly I think they assessed that the AOSP Calendar app was beyond saving (left to rot by AOSP/Google). I cannot remember
89.
▲
by
ysnp
1y ago
Because the technicalities of accomplishing something like that are quite complicated from what I understand. If an app has the necessary permissions and network access, almost anything you try to stop it from transmitting data about the pl
90.
▲
by
ysnp
1y ago
They are already stretched a bit in terms of doing what they are comfortable and best at which is implementing privacy and security enhancements in AOSP and maintaining them across AOSP changes and upgrades (or getting them upstreamed if pa
More ›