• 0 Posts
  • 133 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle
  • Creat@discuss.tchncs.detoSelfhosted@lemmy.world•How do you solve email?
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    5 days ago

    Do not fully self-host your mail. It’ll be constant trouble. Large providers like Google and Microsoft are notorious for blocking them, or never even accepting mail from them in the first place. You can get it unblocked in theory, I hope you like whack-a-mole. Ironically often by eMail.

    What you can do is just buy a hosted mailbox (small or no storage), and have a server at home that instantly collected everything (IMAP). It also basically just proxies outgoing mail to them (SMTP). In practice you host and control your mail, without the peering-issues.




  • You misunderstood my point. LocalSend is great. It does exactly what it promises, and works well.

    But you’re claiming “AirDrop = LocalSend” and that is not true and causes false expectations. People used to Apple think they can use it in all the same situations and for the same things, which they can’t. Just because you mostly used it in the same network doesn’t mean most people use AirDrop that way, and I know quite a few that mostly use it while out and about, meeting new people etc.

    The “Good advice” version is too tell them there is LocalSend, which can do quite a few things like AirDrop, but not all. Basically make it clear they need to be on the same network.


  • This is such bad advice. If you tell people that, people expect it too work like AirDrop, which it doesn’t.

    LocalSend is great, but it is much more limited than AirDrop. As the name suggest, it only works if people are in the same network. If you’re in your home network, and both devices are yours, that’s probably fair enough, but that isn’t the point or (only) use case of AirDrop.

    Also if you’re installing it on a Linux machine which happens to have a firewall enabled by default, you will have to open the correct ports for it to to work out even just see the other devices.




  • It’s all a matter of what you consider reasonable risk. I also run some specific services exposed where it makes sense (they are designed to do this, think things like home assistant or next cloud or jellyfin), but would never put anything that is used to do server administration public facing (Webmin, Termix, proxmox, that sort of thing). If the purpose of the tool is to perform or allow elevated actions, I run it behind a VPN (yes for me that includes ssh).

    There’s also a difference between being randomly port scanned and/or probed, or being actively and personally targeted for some reason. If the second is ever a reasonable threat, that changes what is acceptable dramatically as well.


  • Yes, it inherently is. Authentication/encryption happens as the very first thing at the network level, before anything resembling a service becomes accessible. This is fundamentally different than for example a web interface, which needs to present “the Web page” to allow the user to log in, which might involve multiple individual parts that can already have a 0-day.

    As a more direct comparison: look into historic vulnerabilities between ipsec VPN and SSL VPN. The former is the older technology, the second is more “web like”. The number of serious CVEs for the latter over just some manufacturers (Cisco, fortinet, …) in one year probably beats the number for ipsec in is entire life time.

    Going back to Tailscale (or netbird, …): it is one very secure layer which then secures everything. You can have 1 service or 20, same security. If you expose individual services, c you also expose every possible vulnerability of all of them, so all 20 services if that’s what you run.


  • That actually sounds great then. It probably also depends on how the phone is used, but that likely applies just the same to play services. I mean comparing if you’re always in WiFi, mostly on mobile or often on bad mobile.

    But if it barely shows up for you, that’s good to know. I just remember when first setting up notifications that the options without play services had semi-scary warnings associated with them, which stopped me from using them (and having play services running anyway, it didn’t seem to make sense to not just use them).


  • Home assistant by default uses and relies on play services for notifications. It’s what allows instant and reliable notifications without also causing significant battery drain.

    This can of course be turned off, but it comes with significant warning labels that battery and reliability will suffer. It has to hold a web socket connection, or frequently poll for updates/status.

    From my understanding system level support is needed to make this efficient and low battery, but I don’t know if graphene or similar roms provide something like this (or if they even can)? I would also be very interested to know.







  • But that’s exactly the problem. Those that were the target audience for the article do not have well managed passwords. For them the passkeys arguably do increase security, while having a bit more “lock-in”.

    For those that have well managed passwords (like probably most in this community), they are perfectly fine to use because they don’t have lock-in either. I have full control over my used passkeys.

    Basically you’re not getting the “normies” to use proper password management, and for them they do provide additional security and convenience. They can always add more passkeys on different vendors, you’re not limited to just 1 per service. Yes, adding them is a hassle, but so it’s managing passwords and following higher security standards in general.


  • My various servers, firewall and nas are relatively power optimized. Everything including switches (most with some 10g ports) and access points is 160 W or so combined. I can’t give you monthly usage, as I’ve got solar+battery so it’s frequently just 0 kWh for some days. It’s also rather hard to separate from the other power usage in the house when solar doesn’t fit cover it.


  • This is such a weird stance given the actual change that was made. No actual age verification, no external communication of any kind. All that got added is a number field. The ability to store a number labeled “age” for user accounts. That’s it.

    There already is a field for first name and last name. You can leave them blank as well (most probably do). If any software requires a number to be there, just enter 99 or whatever. Unless this gets severely worse this is such a nothing-burger.

    I’m not happy about any step into that direction either, but pick your battles (or hill I guess). This certainly is a weird one.