• 0 posts
  • 34 comments
Joined 1 year ago
Cake day: June 5th, 2025
  • This really isn’t a technical issue, it’s more an estate planning issue. The basic concern is if you die, everyone gets locked out. That is where a will, safety deposit box, and named executor come into play.

    Whatever credentials and guides needed can be safely stored and upon death that will activates and the executor hands over the access to whoever you are needing. The safest assumption to make in these scenarios isn’t that someone won’t know how to access the information, it’s that they won’t even know that information exists.

    You also have to remember that there is a lot of things to do after someone dies and that these people would also be mourning. So, with that consideration in mind, try to make the process as seamless as possible. Off-loading to an executor of the estate (someone who is not family) also lets those people close to you mourn without having that final burden.

  • This is a fair question to ask given recent events. I don’t run Fedora currently, so others could probably give a much more exact answer, but from what I understand of it:

    Bazzite is built on top of Fedora with uBlue. To compromise one of the packages, the attacker would have to bypass the Fedora enterprise team who are rage filled roid-driven experts who don’t take kindly to that sort of thing. They heavily secure their stuff. Even if an attack was successful, it would have little lasting effect because of immutability and having access to easy rollbacks.

    It’s not impossible (like somehow stealing Bazzite’s keys), but it’s incredibly unlikely. AUR/NPM package sketchiness is not anywhere on the same level as compromising Fedora’s keys.

  • Ok, this I can answer personally as we did multiple cases of this happening (CSAM, bomb threats, etc) at work.

    So, anonymity on the Internet is not actually a thing. Whether its an IP address or telecom switch or whatever, there is a path back to you even if only for either billing or connectivity purposes. So, for IP, we would receive a subpoena signed by a judge to hand over any and all information regarding the identify of the a given IP address (they include a long list of things whether applicable or not in the order so every potential base is covered). Once legal was able to review and handed it off to us, we take that and look at the DHCP logs to see that on a given date at a given time that the IP address was assigned as part of shelf A / slot B / port C. That shelf/slot/port combination is tied physically to an address/account. We provide the relevant logs and personal information of that user to law enforcement.

    For bomb threats over the phone, telecom switches love to tell every other telecom switch who they are (again, connectivity purposes). So, when you make a call to a business/school doing that, their PBX is going to log to the millisecond when that call occurred and who the switch was. Again, subpoena and we pull the SIP logs. We can even provide the RTP/RTCP packets and reconstruct the phone call audio if the subpoena asks for that.

  • I worked as a network analyst for a provider for several years and during that time I’d say ~90% of the issue stemmed from sketchy apps/services that the user loaded from their end.

    A lot of “free” VPN services will basically allow bad actors (the paid tier) to use your connection. A lot of IoT devices are also just openly available on the Internet to route through.

    From the ISP perspective, we managed the roads, not your car. There is a push to blame the ISP as it’s their network, but realistically how are they meant to provide security (in the context that is being asked) to any device that gets plugged into that network? We even had business customers demand we add clauses to contracts where we would accept responsibility for any malware they sent between sites over an MPLS setup.

    In the end, a lot of people seem to want this impossible scenario of the ISP managing security for them but also not inspecting their traffic.