• 0 Posts
  • 37 Comments
Joined 2 years ago
cake
Cake day: July 19th, 2023

help-circle
  • This seems a bit convoluted as an explanation if I’ve understood it correctly. If Telegram as using a compromised hosting provider then you could have the strongest crypto in the world to prevent a man-in-the-middle from seeing the unique identifier for each device and it wouldn’t matter since they already who which user is which IP from the servers they control. They don’t stand to gain anything by exposing the unique string to MiTM attacks when they already control Telegram’s servers unless their goal is also to allow other countries to see which user has which IP too. It just seems like an incompetent implementation.



  • If you only care about having a static IPv6 address take a look at TunnelBroker by Hurricane Electric. They give you free /48 IPv6 blocks tunnelled through their network. Words of warning though: 1) some ISPs block using this service (prevent the tunnel from working), 2) in my experience I’ve seen high latency due to weird routing, 3) those IPs ending up on blocklists due to abuse and 4) the tunnel is unencrypted so traffic between you and Hurricane Electric is trivially intercepted, though if that was a problem in the first place then you wouldn’t be hosting from your home network anyway so this is mostly moot.


  • IP blocklisting is still very much a thing as well so you can expect any mail originating from a residential IP to be rejected due to their /24 or larger having previously sent spam, and that assumes you can send server-to-server mail (destination port 25/tcp) in the first place since many ISPs and server providers block traffic destined to that port by default to prevent users from getting their IP blocklists. My home ISP blocks outbound SNMP traffic (or at least did 10 years ago) presumably to also prevent abuse. That said, things like blocking inbound port 80/tcp and 443/tcp is purely a measure to prevent people running servers at home which I’m not a fan of.


  • Same is true for any tech thing. Sure, you can buy a perpetual licence for something but if you’re running it on anything but an isolated device then you will at minimum need security updates or the source code to fix it yourself. Same is true for things like console games where eventually the hardware will just die and it may become too expensive to replace it. Even emulation is case-by-case since some games use obscure calls which have no adequate emulation. Software doesn’t exist in isolation. For that, you have to revert to pen, paper and some analog tech.








  • They don’t need to be interested though. You could conceivably dump all the password you collect in an attack and just start trying them automatically like you would any other breach. Find a bunch of bank accounts and your chances you getting away with millions are high. Not to mention: a breach like this means changing all your saved passwords to re-secure them which is a multi-day affair.



  • I don’t think ZFS can do anything for you if you have bad memory other than help in diagnosing. I’ve had two machines running ZFS where they had memory go bad and every disk in the pool showed data corruption errors for that write and so the data was unrecoverable. Memory was later confirmed to be the problem with a Memtest run.




  • The OOM killer is particularly bad with ZFS since the kernel doesn’t by default (at least on Ubuntu 22.04 and Debian 12 where I use it) see the ZFS as cache and so thinks its out of memory when really ZFS just needs to free up some of its cache, which happens after the OOM killer has already killed my most important VM. So I’m left running swap to avoid the OOM killer going around causing chaos.