• 0 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle

  • In this context “self host” can ironically mean using a cloud service for hosting. You can use a file based password manager and just sync the database. Solutions like KeePass have apps for many platforms, and they can often even directly load from cloud storage, like Google drive, OneDrive or DropBox. The password database is strongly encrypted, and even if your storage gets compromised, your passwords are still safe (assuming a good password or some then better security was used to encrypt it).

    You give up the convenience of having a single service and having to get each device to access the file. But that’s it. It’s not that hard and so much better than a password service, even if just for their attack surface, or the “likely target” these are.


  • Ah the Internet classic: calling someone’s comment irrelevant, when you clearly haven’t even read, or at least not understood it. It isn’t that long of a comment. Try reading it again.

    Oh whatever, here’s another attempt at explaining it: there’s a huge difference if my passwords are in a place where people generally keep passwords, or if they are where only my passwords are. If someone has never heard of me, but they attack my cloud-password-solution and get in, they still get my passwords. Someone attacking me personally, if he’s truly competent as a hacker, in probably screwed either way. At least he can only attack me, he can’t attack “some public thing” and get my stuff “by accident”. Think “personal safe in my home” compared to “public bank” (ignoring the fact that a bank is insured and all that for this analogy).

    Your second point would be valid if open source didn’t exist. First of all I didn’t imply that it was inherently safe, I implied that there isn’t a single point of trust, which was my would point. Even if you can’t read/audit it yourself, there are projects that have public audits by reputable security companies. Plus if there truly were backdoors, assuming a non-tiny user base, someone would’ve probably noticed.

    Then your final point seems to acknowledge the attack surface, but the problem with the “locally encrypted blob” is that this statement from the cloud provider is another thing you just have to believe them on. They might do that, they might not. Many don’t even claim that, because people like convenience and want options for password recovery to their password service. those two are mutually exclusive.


  • Stop using “the cloud” to store your passwords. Unless you control said cloud, you have to trust someone to not fuck up their security that you now depend on. Everyone eventually does.

    The difference is also, that someone who’s job is storing other people’s passwords is by definition a target. So is the fuck up, someone will notice. If you host those yourself, or you rent a place where you can host them for yourself, that is just one person’s server. The interest and possible gain for someone gaining access is so small, it’s even unlikely. So when you inevitably fuck it up, the chances someone notices before you do are relatively small.






  • Yes exactly. I didn’t wanna name-drop them cause they are closed for new dynDNS signups. You can create an account to manage your own domain, but you currently can’t signup for their dynDNS service, unfortunately.

    That being said, I would still highly recommend them for managing your own domain, if you’re looking for a place to host literally just the DNS part.





  • The native Android client just can’t do two way sync. Just put a text file or something into any folder (from the web or desktop). Now sync that folder to Android. Now edit it on the web/desktop, and look for the changes on Android (without actively telling it to “sync”). Then change the file on Android, these 2nd changes are never sent back to the server unless you explicitly tell it to “sync” again, manually. That’s what I mean with 2 way sync.

    There are quite a few files where you just need that to work to use them properly, like the database of a password manager as a prime example. Mine can talk to Nextcloud natively, so I don’t need the client for that, but I was incredibly close to just switching to syncthing, if I didn’t have active users that use the web office integration of Nextcloud.





  • Nothing is “obvious” about that. What you present as the only possible conclusion from their actions is just your subjective interpretation. Could be true, of course. I highly doubt it (which is my subjective interpretation).

    Someone realized that the investment required for making a PC port (or having the studio include it) is less than the money you can make from selling it on PC. Selling consoles (the hardware) isn’t what makes them money, it’s reasonably common for them to be sold at a loss, especially early in the life cycle. Profit comes from people buying games they take a cut from, which is unchanged if Sony is also the publisher (or even the developer).

    In any case, if I’m right or wrong isn’t even the point either (I’m probably wrong, too). The point is it’s incredibly complicated, and nothing is even slightly “obvious” about it.