• 8 Posts
  • 378 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • Don’t send spam, behave nicely, have proper configuration on postfix and dovecot, set up SPF and preferably DKIM, keep your domains reputation clean and so on. You’ll likely still end up on some lists, so you need to manually dig them trough and ask nicely for removal.

    Self hosting email has a pretty bad reputation and many will strongly advice against it, but in reality it’s really not that bad. But email as a whole is more complex beast to manage than simple website or running Jellyfin for your family and friends. You need to understand how the mail routing side of things work (SMTP itself, authentication for it encryption included and so on) and also you need to understand how DNS works and how various entries are related to mail transport. Then you’ll likely want at least some kind of spam filtering and so on. And with email you’ll need to have proper backup scenario too so that you don’t lose the likely pretty important data. All of that is perfectly doable and it’s not as difficult as many claim it to be, but there’s a bunch of stuff you need to understand and implement all of them correctly.



  • Fines are just the cost of doing business.

    In theory fines in EU don’t have a ceiling. 10% fine of companys turnover with OpenAI (or any other company running on borrowed money) would be a pretty steep cost of doing business and I don’t think all (if any) of AI-hype entities could actually swallow that.

    Obviously that’s just in theory, so far the fines have been a slight slap on the wrist, but mechanisms are in place to give actually meaningful fines for unethical practices. No one will go to jail tho, as EU doesn’t really have the power to jail US citizens.




  • It’s interesting piece of technology, but it’s not ‘radical’. The company behind the storage has done their homework and they seem to be well engineered, but the “technology” itself is pretty much as old as bonfires, people have used hot rocks to heat up tents for ‘a while’.

    But sand has pretty good thermal properties and size of these new iterations of old tech makes them pretty decent solution for energy storage with renewables. I’ve been following various ‘sand battery’ products for our own house, but the main problem with all of them tends to be the size required. In practise for our own house we’d need a sand battery roughly the size of 6m storage container (with heat pumps and all the other hardware) and that’d be so expensive that the investment wouldn’t pay itself back in my lifetime.




  • Just protecting for spoofed IP doesn’t add much in my opinion, at least compared to the effort of setting up and maintaining 802.1x. Easier way would be to set up different local networks per family and allow access to shared services via common firewall. That doesn’t require support from devices nor it doesn’t rely on security on them. Properly setting 802.1x would mean that you’ll need to manage every device on the network somehow and, assuming you don’t actually own or control the devices, that would be at least challenging.

    Your thinking isn’t wrong, in that scenario network level authentication would help, but overhead of such setup is, again in my opinion, way more complex than what you can actually get in return. Of course if you want to just do it for the fun of it, go ahead. And also, if the devices are on the same network, they can sniff MAC addresses and IPs of neighboring devices, so protecting anything with just IP/MAC is a lost cause.


  • Radius is a part of 802.1x standard and for your threat model that does absolutely nothing. If a bad actor can access a device already in your network, then network level authentication doesn’t do anything. For example it prevents from someone randomly plugging their device in your switch and getting access that way, or it only allows verified clients to your WLAN. But once the network connectivity is already established you need a totally different tools.

    Mainly that means firewall on your network and/or servers. There’s multiple ways to build that. You could get a separate firewall device to block access from the rest of the network to your devices or you can set up firewall for each of your things separately. All solutions have their own pros and cons and ‘correct’ solution depends on multiple variables.


  • Perhaps the easiest, and still at least decent, approach is to just run nmap (or any other port scanner) against your own subnets/IP addresses. That way you’ll at least find out if the firewall allows something trough which it shouldn’t, Also you can run tcpdump/wireshark on destination host to see if it receives packets it shouldn’t.

    For client authentication, if ARP filtering is not enough, you could set up 802.1x, but that’s likely a massive overkill (and overhead) for home network. I personally don’t authenticate clients separately. Just WPA2 on wifi and firewall rules to allow/deny traffic between subnets. Sure, it’s pretty easy to bypass, but in practise you’d need to be inside the house to access some parts of the network. But my threat model is mostly about a handful of IOT things which I don’t trust with full network access, not about someone unauthorized getting access to my home network.



  • Don’t put words in my mouth. I didn’t say anything about not needing to be concerned, I was just interested on what kind of virus they cooked in the datacenter-incubator and how that might affect on a general population. “Deadly bacteria”, while not incorrect, is a bit clickbait-y, as it doesn’t just kill everyone and their dogs.

    Of course there are reasons to be concerned and Meta should absolutely throw boatloads of money to clean up their mess. I was just interested about the bacteria in general, where it came, how it works and so on, nothing more and nothing less. I’m across the big pond and in here environmental regulations actually work, so I personally am not the one who should get angry about the situation, but it doesn’t mean that no one should, even if I don’t explicitly say so.



  • Apparently that particular bacteria is basically everywhere on the environment and amounts of it around is pretty harmless. Datacenter just offered a nice and warm environment for it to prosper and then dumped the shitload of bacteria into water treatment system and the treatment plants can’t manage that much of it properly.

    Also, while it could be deadly, it’s more likely that you’ll have couple of miserable days on the porcelain throne. But almost any underlying condition (being old, having any kind of gut issues, having flu…) can tip the scale and instead of literally shitty ilness you’ll end up in a box.

    While Meta is of course guilty here on multiple things one might argue that local government is equally responsible since they allowed Meta to connect their sewer pipe in the first place without proper precautions. But maybe Zuck just had to have a new limousine or whatever so responsibility part was skipped.


  • i still need to find a way to setup a simple sambashare via a web gui and a good backup solution.

    I’m running openmediavault as an VM for file shares and backups with proxmox backup server. Works pretty well. I’ve got a physical backup server in detached garage and another in a VPS which syncs the most important parts to remote location.


  • I definitely didn’t suspect there to be a whole new standard of wireless communication to that.

    There’s multiple. Some devices are on wifi, some on z-wave and as zigbee is getting quite a lot of support from vendors I’ll likely add that to the mix soon-ish. Also I could use bluetooth for some automations, but at least for now I don’t really see any advantages over that.

    As for pihole, it’s main DNS server for devices in my network and rest of the family uses the net quite a lot too (IPTV and streaming services included) so any longer downtime would cause at least annoyance for them so it’s nice to have an option to keep things running and take my time to maintain hardware or whatever. I of course could change DHCP server to offer something else too, but it’s simpler and faster to just migrate a VM to another host.


  • Is there a benefit for splitting your services on 2 hosts?

    I don’t know about OPs situation, but I have a mini-PC as proxmox hypervisor too addition to my main server. Mini-PC is located middle-ish of the house as it’s running home assistant with ZWA-2 and the location helps a lot with Z-wave coverage. But added benefit is that I can (within the pretty strict resource limits) move VMs to the mini-pc when doing maintenance on main server. It’s pretty handy to move PiHole and some other small stuff to another host so that everything on network still functions even if one hypervisor is down.