Also at k3can@mastodon.hams.social

  • 0 Posts
  • 19 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2023

help-circle
  • The slightly lower power draw pi5 vs a Tiny will eventually make up for the higher initial cost, but you can save more by turning off lights when you leave a room or skipping a round at the bar.

    In my opinion, the wider software compatibility, better processing power, and expansible RAM and storage options far outweigh the eventual theoretical savings.

    That said, if you need the super small SBC form factor or GPIO pins, definitely go for a pi. They absolutely have their use cases. I have 4 or 5 of the 3B and 3B+, and have used them on-and-off for a variety of tasks over the years.










  • You’re not a “target” as much as you are “a thing that exists.” These aren’t targeted attacks.

    That said, you can look into adding some additional measures to your webserver if you haven’t already, like dropping connections if a client requests a location they shouldn’t, like trying to access /admin, /…/…, /.env, and so on.

    On nginx, it could be something like:

    location ^/\.|)/admin|/login {
        return 444;
    }
    

    Of course, that should be modified to match whatever application you’re actually using.




  • A lot of how you set up your system is just going to depend on how you want to set it up.

    I run podman (like an improved version of docker) in a single LXC container for applications that are primarily packaged as docker apps. I think I have 4 or 5 applications running on that LXC.

    For things that are distributed via apt, git repo, etc, I’ll either create a new LXC or use an existing LXC if it’s related to other services I’m running. For example, crowdsec is run in the same machine as nginx since those two work together and I’ll always want them both running at the same time, so there’s no reason to separate them.

    I have mariadb running in its own LXC so that it can follow a different (more frequent) backup schedule than the mostly static applications that interact with it.

    Anything that needs to interact directly with hardware, like Home Assistant, or I want kernel separation for, will get a full fledge VM instead of a container.

    It’s all about how you want to use it.




  • I self host.

    I use nginx as a reverse proxy with crowdsec. The backends are nginx and mariadb. Everything is running on Debian VMs or LXCs with apparmor profiles and it’s all isolated to an “untrusted” VLAN.

    It’s obviously still “safer” to have someone else host your stuff, like a VPS or Github Pages, etc, but I enjoy selfhosting and I feel like I’ve mitigated most of the risk.




  • I know I’m a bit late to the conversation, so I don’t know if this is still helpful… But I have a camera with “AI Detection” built into it and it appears to send alerts via its ONVIF connection. I’ve disabled motion and other detectors on my NVR (AgentNVR) and instead configured it to just wait for an alert from the camera itself to start recording. It’s been working quite well.

    My initial plan was to use a coral TPU and frigate, but the Coral/Gasket drivers appear to be pretty old and I couldn’t get them to work properly, myself.