• 0 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle


  • If it’s the system with the (locked) KeePass database on it, you should be fine. The encryption can be tweaked so that unlocking the database takes a second even on modern systems. Doesn’t affect you much, but someone trying to brute-force the password will have a hard time. It also supports keyfiles for even more security.

    If somebody infiltrates your end user device, no password tool will be safe once you unlock it.



  • After trying them all, I’m back at having a local KeePass database that is synced to all my devices via iCloud and SyncThing. There are various apps to work with KeePass databases and e.g. Strongbox on macOS and iOS integrates deeply into Apple’s autofill API so that it feels and behaves natively instead of needing some browser extension. KeePass DX is available for all other platforms, and there are lots of libraries for various programming languages so that you can even script stuff yourself if you want.

    And I have the encrypted database in multiple places should one go tits up.










  • Thing is, DMCA doesn’t apply all over the world. There are countries where whatever electronic device you buy is actually yours and you’re allowed to do whatever you want - including messing with the firmware. Also, I’d argue, the DMCA doesn’t apply if you dump the firmware/keys for yourself only without distributing it.

    That being said, it’s unfortunate that these people are mostly in the US where the party with more money decides when a lawsuit is over and not some sane judge that just throws this case back at Nintendo. But after the stuff with Disney+ and the recent one with Uber, I’m not surprised at all anymore.





  • You might want to look at Terramaster NASes. E.g. their F4-423 is basically an Intel NUC married to a SATA controller. They have an internal USB port where you can pull the OEM flash drive and insert your own, then install e.g. UnRAID or OpenMediaVault on it.

    That will be my next device if my Synology DS415+ finally dies.



  • I’m using OwnTracks in HTTP mode as I couldn’t be bothered with MQTT. For that, you only need the HTTP(S) endpoint/URL to log to, optionally user credentials and then it’s a “TrackerID”, “UserID” and “DeviceID” so the receiving server knows who’s talking.

    Side note: Traccar uses different ports to receive different protocols. For OwnTracks protocol, the correct port is 5144.

    My OwnTracks configuration is basically like this:

    • TrackerID: 1
    • DeviceID: Phone
    • UserID: mb
    • URL: https://mytraccarserver.com:5144 (the port itself is HTTP-only IIRC, but I’ve mapped Traefik Proxy in front of it which handles HTTPS)