🇨🇦

  • 2 Posts
  • 87 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle






  • I wonder why so many people had issues with the v6 pihole update.

    I pulled the new docker container and it ran overtop the previous version just fine. The only issue I had was I had the admin password set to empty via an env variable and that variable name changed. Took like 10 min to find and fix. The rest migrated perfectly.

    Now I’m just waiting on orbital-sync to add v6 support, but that’s just around the corner and not that critical.


  • 95% of things I just don’t expose to the net; so I don’t worry about them.

    Most of what I do expose doesn’t really have access to any sensitive info; at most an attacker could delete some replaceable media. Big whoop.

    The only thing I expose that has the potential for massive damage is OpenVPN, and there’s enough of a community and money invested in that protocol/project that I trust issues will be found and fixed promptly.

    Overall I have very little available to attack, and a pretty low public presence. I don’t really host any services for public use, so there’s very little reason to even find my domain/ip, let alone attack it.


  • Looking at openspeedtests github page, this immediately sticks out to me:

    Warning! If you run it behind a Reverse Proxy, you should increase the post-body content length to 35 megabytes.

    Follow our NGINX config

    /edit;

    Decided to spin up this container and play with it a bit myself.

    I just used my standard nginx proxy config which enables websockets and https, but I didn’t explicitly set the max_body_size like their example does. I don’t really notice a difference in speed, switching between the proxy and a direct connection.

    So, That may be a bit of a red herring.