• 26 Posts
  • 1.02K Comments
Joined 3 years ago
cake
Cake day: June 22nd, 2023

help-circle

  • solrize@lemmy.mltoSelfhosted@lemmy.worldReplacing a landline phone
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    5 hours ago
    1. I’ve had trouble getting Jami to work at all, I think because of incompatibilities between versions and whatever. You might have better luck with something like Linphone.

    2. I haven’t tried a VOIP hardphone but I use Linphone on Android sometimes. I would say call quality is worse than normal cellular voice calls even those are certainly VOIP at some level too.

    3. VOIP is more crap to fool around with and periodically troubleshoot, but you can get it to work if you have to. I don’t find landlines to be worth it any more (I just use mobile voice) but they’re probably still the most reliable of the approaches, and I guess it depends somewhat on your family’s discomfort level with technology.

    VOIP hardphones are nicer to use than mobiles, but I guess unlike traditional landlines, they don’t work in power outages. All the ones I’ve seen rely on a power cube.















  • When you say E2EE that usually refers to encryption and decryption at each end. So the endpoints see the plaintext but it’s encrypted in transit.

    I think you don’t want E2EE in the above sense. You want all the encryption and decryption to be on the client, i.e. you want encrypted remote storage where the server side ONLY sees ciphertext.

    Anyway yeah, maybe just SSHFS or NFS to an encrypted disk image on the loopback FS of your local machine. I think the remote side shouldn’t even have a file system (i.e. that exposes metadata like file sizes) rather than just a raw disk-like image. But, it could still be possible for someone monitoring disk activity on the server side to infer some things about that.

    How much data are you talking about? What is your budget? You might be better off with a dedicated server, e.g. Hetzner server auction. That would make various active monitoring at the host less likely. You’d still want to encrypt in about the same way as you would a VPS.

    You are trying to serve a LAN? You mention you can’t use a local server, but if “can’t” only means it’s inconvenient, it might be worth the effort anyway. Come to think of it, a transatlantic internet connection will also be pretty slow.



  • Don’t put your Keepass on a remote server! Jeez. For your photos you could run Nextcloud on a VPS with an encrypted file system. That wouldn’t be super duper secure (the host could get the keys out from the running VPS) and you’d have to deal with reloading keys every time you rebooted the VPS for whatever reason, but it’s a pretty simple thing to do. IDK if that would count as E2EE since the VPS does see the plaintext in transit.

    Maybe you could do something with SSHFS and an encrypted disk image (all encryption and decryption is on the client side) but that starts getting slow and flaky.

    Tbh I don’t bother with anything like that for my own photos. They’re just on my local machine and not on the network. I have some encrypted Borg backups on a remote server but no Nextcloud or anything like that.