• nymnympseudonym@piefed.social
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 hours ago

    If he hadn’t used duress and had just refused, he’d have been fine. Graphene is secure

    Graphene devs fucked over this guy. They should apologize

    When Graphene is serious, the duress passcode will QUIETLY wipe your phone and leave it looking normal, preferably with normal-looking innocuous photos, media, etc.

    This is what happens when devs aren’t really thinking about the real world use case.

    • rumba@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      41 minutes ago

      Something designed like SAmsung Knox would be much better. the rest of the phone/apps are still fine.

    • GalacticRobot@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 hours ago

      They shouldn’t apologize, the dude should of known that destroying evidence during an investigation is going to land you in jail.

      • nymnympseudonym@piefed.social
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 hours ago

        No. If you make and distribute security-related software, you should consider the safety of your user.

        Your threat model absolutely should include this exact scenario. And you should know enough to understand and implement principles like plausible deniability and repudiation.

    • kestrel7_7@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours ago

      Can’t Graphene be used like this already? Dude may not have known, or may not have bothered to set up multiple profiles. But I’m pretty sure it can be done.

      • nymnympseudonym@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        32 minutes ago

        Point is that when graphene gets the distress code, it makes it really clear that it’s wiping the phone.

        That’s the Stupid Part