• 1 Post
  • 67 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle
  • That’s a bummer. I’ve been using the forked version as well, and even that dev has been annoyed with Google Play enough that it’s only released on F-Droid nowadays.

    Personally, I don’t think it’s an issue only releasing only on F-Droid, because the people interested in Syncthing wouldn’t be deterred by that if they’re not already using it, but I totally get why that might sap the last bit of motivation the dev has.


  • I’d be more concerned as well if this would be an over-night change, but I’d say that the rollout is slow and gradual enough that giving it more time would just lead to more procrastination instead, rather than finding solutions. Particularly for those following the news, which all sysadmins should, the reduction in certificate lifespan over time has been going on for a while now with a clear goal of automation becoming the only viable path forward.

    I’ll also go out on a limb and make a guess that a not insignificant amount of people only think that their “special” case can’t be automated. I wouldn’t even be surprised if many of those could be solved by a bog-standard reverse-proxy setup.


  • Part of this might be my general disdain towards sysadmins who don’t know the first thing about technology and security, but I can’t help but notice that article is weirdly biased:

    Over the past couple of days, these unsung heroes who keep the internet up and running flocked to Reddit to bemoan their soon-to-be increasing workload.

    Kind of weird to praise random Reddit users who might or might not actually sysadmins that much for not keeping up with the news, or put any kind of importance onto Reddit comments in the first place.

    Personally, I’m much more partial to the opinions of actual security researchers and hope this passes. All publicly used services should use automated renewals with short lifespans. If this isn’t possible for internal devices some weird reason, that’s what private CAs are for.




  • And you can even go a step further and configure it so all the ISOs go into a subdirectory. Then you can still use the USB for other stuff without it becoming a mess. Right now I have the following structure:

    ├ apps // Lots of portable apps, using the PortableApps systemdata // For copying files between devices
    ├ images // ISOs go here, separated into Linux, Windows and Utilities
    ├ installs // For apps that need to be installed
    ├ secure // Encrypted Veracrypt store
    └ ventoy // Ventoy config
    

    All that on a tiny USB on my keychain and super useful when you’re the IT person for the family.







  • Depends a bit on the clients.

    • KeePass: Will ask you if you want to synchronize/overwrite/discard the database when saving.
    • KeePassXC: Will autoreload the database in the background, so merge conflicts shouldn’t happen in the first place. Otherwise there’s ‘Merge database’ in the menu.
    • KeePass2Android: So I mixed up the names and this is the client I actually use. This one does all changes to an internal copy of the database that is then synchronized on request.
    • KeePassDX: As far as I can see it also has a mechanism similar too KeePass2Android.

    Assuming you only have one desktop and mobile client you should never run into any issues. If you do have multiple KeePassXC clients it’s all fine as well assuming Syncthing always has another client it can sync with.







  • (like do I seriously need No Man’s Sky installed all the time for the once every three months that I play it?)

    That sound’s like the data is in semi-regular use at least. For me it’s more like “Do I seriously need the sequel installed for that other game I haven’t even started yet, but am definitely going to start any day now, after years of having it installed?”.