• 0 posts
  • 7 comments
Joined 3 months ago
Cake day: August 10th, 2026
  • Hardening ios is just turning a bunch of shit off in settings and turning on lockdown. It breaks a bunch of things.

    I would point most people at a dns blocklist and vpn enforced with a device management profile.

    iOS already doesn’t allow most types of background operation, can manually filter apps access to (just by the nearest device’s count) 22 different permissions and has a very useful app privacy report.

    I am a daily user of both ios and graphene so if you have any questions, fire away!

    E: oh yeah, and using adp. Gotta have that.

  • If your primary concern is privacy and security then the next best thing to graphene in the anglosphere (you are asking in English on an English language web forum) is hardened ios. Do not take my word for it, do your own research on this topic.

    It may be worth recognizing the extent to which the phone network and internet are a surveillance technology and to which metadata about encrypted data will expose information about you.

    If your primary concern is vendor lock in then the best thing is the one you can move away from most quickly and for the majority of people that’s a question of moving to third party services as opposed to first party ones. If avoiding vendor locking is your main goal then I recommend first moving entirely to third party services under the Android ecosystem.

    Privacy & security and avoiding vendor lock in are mutually exclusive at this time (and for the overwhelming majority of previous times). Choose wisely.

  • Not today, satan.

    Passwordless root allows you to require another factor of authentication on the off chance you didn’t set up key only ssh login like the top of the guide says. That second factor is the administrator account name. Now you can make this as generic as you want but assuming your non root admin account isn’t named “administrator” or “admin” then you just increased the security of your system.

    Suggesting that because privilege escalation exists there is no difference between a user and root is absurd on the face of it. Privesc requires vulnerable versions of vulnerable packages with the specific circumstances present that allow pre and post exploitation actions. In case you were operating under the assumption that most privesc goes from local administrator to root, usually you’re going from some relatively unprivileged user account that handles a service up to root and that’s harder than just invoking sudo.

    You would still want to roll over your credentials and restore from backups but “safe cracking tools exist so just leave the cash register deposits in plain view on a shelf behind the desk” isn’t a strong argument for password root.

    E: @talkingpumpkin@lemmy.world correctly pointed out that a nonstandard admin account name isn’t a second factor. It’s more like an additional secret.