My active account is @thayerw.

@thayer is inactive and no longer monitored; it remains only for the sake of post history.


  • 1 Post
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle



  • Sure, like I said above, GOS doesn’t at all prevent you from rooting the device. They only discourage it from a security point of view. Regarding MicroG, I’ve never had need for it myself but I’ve read many other posts over the years from users who have installed it on GOS in lieu of Graphene’s own implementation.

    I would argue that overall GrapheneOS provides more control over the OS than some other Android-based operating systems.




  • You’ll need to provide specifics if you want solutions to many of these issues.

    • What exactly isn’t working with your Yubikey?
    • Which bank apps? Did you check the compatibility list maintained by GOS?
    • Which apps aren’t working without Google Play?

    For the keyboard, there are several FOSS keyboards which support spacebar navigation, but you can also install Gboard and simply disallow any permissions, including network access.

    Regarding Signal, this would be a reality for anyone with a non-Apple device. You may need to find a compromise and simply use SMS, RCS, or even just email when dealing with certain people.

    There will always be one-off features available only on other devices or platforms. Only you can decide whether they are worth the cost of security and privacy.





  • thayer@lemmy.catoPrivacy@lemmy.mlRFC: Cross Platform Password Manager
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    4 months ago

    That used to happen to us before we started using SyncThing (and before we had data plans on our phones).

    By the time we migrated to it, we had a home server running 24/7 and this ensured that at least one device in the chain was always online, had the latest version of the database, and pushed it to other devices as they came online. Our phones also have data plans now, so things generally sync in realtime which helps avoid issues.

    If you don’t have at least one always-online device, I think the next easiest way to avoid sync conflicts is to modify the database from one designated device. That way even if a conflict does arise, you’ll know which device is always correct.

    For resolving the conflicts, I would open both databases, sort by modified, and review the latest changes in each.


  • thayer@lemmy.catoPrivacy@lemmy.mlRFC: Cross Platform Password Manager
    link
    fedilink
    English
    arrow-up
    41
    ·
    edit-2
    4 months ago

    KeePass, and more specifically the KeePassXC (desktop) and KeePassDX (Android) ports.

    My wife and I have shared a single KeePass database for about 15 years now and I couldn’t imagine switching to anything else.

    My reasons have remained the same over the years:

    • Free and open source
    • Offline (but supports cloud sync)
    • Lightweight
    • Cross platform
    • Supports autofill

    I would never entrust the management of my credentials to a 3rd party online service. They’re an easy target (it’s only a matter of when, not if they are breached), and they could go out of business at any time.

    We don’t use cloud storage for anything these days, but we keep the KP database (and many other things) synced across more than 7 devices using SyncThing, another amazing FOSS project.





  • There are too many differences for me to list here, but unlike mobile operating systems, Windows and most Linux desktops do not provide sandboxed environments for userspace apps by default. Apps generally have free reign over the whole system; reading/writing data from/to other apps without restriction or notification. There are virtually no safeguards against malicious actors.

    Mobile operating systems significantly restrict system-level storage space, making key areas read-only to prevent data access or manipulation. They also protect app storage, so one app can’t arbitrarily access or modify data stored for a different app.

    Mobile operating systems also follow an image-based update model, wherein updates are atomic. System software updates are generally applied successfully all at once or not at all, helping to ensure your phone is never left in a partial or unusable state after a system update.

    For desktop users, macOS, and atomic Linux distros combined with Flatpak are the closest comparisons.




  • No, the average user will never know the difference. I couldn’t tell you exactly what the current performance impact is for hardware encryption, but it’s likely around 1-4% depending on the platform (I use LUKS under Linux).

    For gamers, it’s likely a 1-5 FPS loss, depending on your hardware, which is negligible in my experience. I play mostly first and third person shooter-style games at 1440p/120hz, targeting 60-90 FPS, and there’s no noticeable impact (Ryzen 5600 / RX 6800XT).



  • While it would certainly be nice to see this addressed, I don’t recall Signal ever claiming their desktop app provided encryption at rest. I would also think that anyone worried about that level of privacy would be using disappearing messages and/or regularly wiping their history.

    That said, this is just one of the many reasons why whole disk encryption should be the default for all mainstream operating systems today, and why per-app permissions and storage are increasingly important too.