• 0 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: November 11th, 2023

help-circle


  • Mahonia@lemmy.worldtoAndroid@lemmy.worldgraphene os advice
    link
    fedilink
    English
    arrow-up
    8
    ·
    8 months ago

    I’ve been using GrapheneOS for about 5 years.

    Google pay won’t work, but everything else should. I’ve never experienced any of the issues the other commenter had, and I’ve installed Graphene on 4 devices (not dismissing you BTW, just saying I think your experience is quite uncommon).

    I don’t think third-party launchers are a good idea (you’re giving full device permission to an unneeded app) but it should work.

    Almost every app I wanted to use worked with Graphene before they introduced their sandboxed google services, and now everything I’ve tested works with Google push notifications. The only exception is Google pay, and there are upstream reasons for that. Keep in mind, on a very rare occasion the hardened memory allocator breaks compatibility (again this is very rare), but there is an app-specific setting toggle to turn this off so it’s kind of a non-issue.








  • Mahonia@lemmy.worldtoMemes@lemmy.mlTraditional values
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    9 months ago

    I don’t understand the format of this. Why put a dictator/murderer/war criminal and shitty capitalist/conservative talking head having this detailed and interesting conversation. These two in no way deserve any of the positive association this meme implies.


  • If you’re using a stock android device, the OS on your phone still has permissions to read and write to storage, by necessity. If what you’re concerned about is privacy, you have very limited ability to set storage scopes if you don’t trust the OS, and this doesn’t really change if you install an app.

    If you’re using fossify file manager or any other file manager, you’ve given that app+the default Files app access to your storage. This is not more private. Most of those similar apps are essentially just skins on top of the default manager (which I suppose could be useful). This only really adds attack surface and doesn’t have any meaningful privacy benefits, and potentially some detractors depending on the app you use.

    If you don’t trust the operating system and its utilities, the best option is to find an operating system you trust, and not to just install new skins on top of existing apps.



  • I don’t get these arguments. These tools aren’t weapons, and limiting legal access to pentesting tools will decrease corp’s and individuals’ ability to be proactive about security.

    These devices can be manufactured relatively easily and making them illegal will essentially mean the only people doing security tests are criminals. Large tech companies, correctly, run bug bounties where independent security researchers can make income by reporting reproducible and exploitable bugs. The concept here is called offensive security and it’s extremely important for building better and more secure platforms. This situation will never be improved by limiting legal access to useful testing tools.

    The responsibility should be on automakers and other companies that have massively insecure products, not on open source developers who are making products for security researchers.




  • It seems like maybe the problem is that automakers were able to widely market vehicles that use wireless protocols that are relatively easy targets for attack. This was never properly secure.

    Automakers should absolutely be held to higher standards (in general) than they are, and it’s not likely that banning specific devices is going to have any measurable outcome here. It’s pretty well known that people buy and sell malware, and people can just… make devices similar to a Flipper with cheaply and readily available hardware.

    This is just dumb posturing to avoid holding automakers and tech companies accountable for yet another dumb, poorly thought out, design feature.

    And obviously it doesn’t stop at cars. It seems pretty clear that snooping on any feature using RFID or NFC tech is only going to become more widespread. Novel idea: what about using… actual keys as the primary method of granting physical access? Lock picking is obviously possible but a properly laid out disc-detainer lock is pretty goddamn hard to bypass even with the proper tools, and that skill can’t just be acquired in the same way as with electronic methods of bypass.


  • I once tried to do a relatively basic repair on a phone, and ended up really breaking it. Like the touch screen won’t work because I broke some shit on the motherboard that now requires micro soldering broke it.

    So I send it to a repair company that allegedly does some micro soldering, and they call me to tell me they can’t repair it because their diagnostic utility doesn’t work unless it’s the stock OS (I’ve been a GrapheneOS user for many years). What they do is… wipe my data and then tell me it’s not the screen so they can’t repair it.

    Then I sent it to an actually good repair shop and they fixed it very quickly, easily understanding the problem. Good repair companies aren’t easy to find but damn are they worth it. They’re almost always smaller shops and they do not GAF what you do with your phone’s software.