• 1 Post
  • 15 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle



  • You’re confusing a lack of handholding with gatekeeping.

    beginner friendly solution, something with a UI, fewer manual configs…

    First, you’re not entirely right. you can get a ton of self hosting done with things like Synology or Home assistant, and never see the complexity. You might get owned by a botnet, but it “works.”

    Self hosting securely has a steep learning curve, there’s no way around that. What you’re asking for is for someone to write programs that’ll let you skip the learning curve.

    GitHub is littered with abandoned attempts at doing this. You bury your lede by mentioning “your project” at the end. It’s your project going to be another well intentioned attempt that’s eventually abandoned or causes more problems than it solves?





  • per the searxng container instructions:

    Understanding container architecture basics is essential for properly maintaining your SearXNG instance. This guide assumes familiarity with container concepts and provides deployment steps at a high level.

    The fact that you’re logging into your container to manually edit your config hints that you need to read more about managing containers.

    Make sure you’re editing the file that you’re mounting on the host, and edit it from the host.

    Have you checked the actual log with podman logs? It’ll tell you what it’s doing about its config.


  • Why do tape drives seen to be best? What’s your use case? They’re still used in enterprise environments because they’re insanely dense compared to hard disks, and it’s real easy to load a truck with a few petabytes to ship elsewhere. Is that what you need? Density? Seems like not for just a few gigs.

    If you want backups you need to ship your media, tapes or otherwise, off-site.

    Pop your files into a cloud service and call it done. If you’re looking for long term archives and don’t want to use other people’s computers, burn some DVDs and store them at someone else’s house.





  • What in the world is “a proprietary OS I cannot trust”. What’s your actual threat model? Have you actually run any risk analyses or code audits against these OSes vs. (i assume) Linux to know for sure that you can trust any give FOSS OS? You do realize there’s still an OS on your dumb switch, right?

    This is a silly reason to not learn to manage your networking hardware.


  • A VLAN is (theoretically) equivalent to a physically separated layer 2 domain. The only way for machines to communicate between vlans is via a gateway interface.

    If you don’t trust the operating system, then you don’t trust that it won’t change it’s IP/subnet to just hop onto the other network. Or even send packets with the other network’s header and spoof packets onto the other subnets.

    It’s trivially easy to malform broadcast traffic and hop subnets, or to use various arp table attacks to trick the switching device. If you need to segregate traffic, you need a VLAN.

    Edit: Should probably note that simply VLAN tagging from the endpoints on a trunk port isn’t any better than subnetting, since an untrusted machine can just tag packets however it wants. You need to use an 802.1q aware switch and gateway to use VLANs effectively.