• 0 Posts
  • 7 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • Very funny, I stille have an old TPlink running now for 6 or 7 years, my parents had an old linksys that only did 2.4GHz running for 13 years or something. Before i replaced it for them.

    I honestly don’t know how a router breaks. It can become outdated or obsolete such that it can’t interface correctly anymore or it can have a hardware failure that kills it by surges or physical damage, or it can be completely unsecure because it hasn’t been updated in a decade but routing is “fairly simple” and just getting data throughput isn’t rocket science software-wise.



  • As someone who has to interface professionally with solidworks and everyone at my company on the mechanical side uses solidworks, it is also slow as fuck when the part or assembly gets a bit complicated. Just opening it takes a few minutes. If we have to open solidworks and an assembly from scratch during a meeting, that is 10 minutes gone.

    Definitely has 10x as many QoL and productvity features and much better TNP solutions and heuristics built over decades, plus very useful plugins, but speed and stability are not its strong points 😂




  • Dropping instead of blocking might technically be better because it wastes a bit more bot time and they see it as “it doesn’t exist” rather than an obsticle to try exploits on. Not sure if that is true though.

    For me:

    • ssh server only with keys

    • absolutely no ssh forwarding, only available to local network via firewall rules

    • docker socket proxy for everything that needs socket access

    • drop non-used ports, limit IPs for local-only services (e.g. paperless)

    • crowdsec on traefik for the rest (sadly it blocks my VPN IPs also)

    • Authelia over everything that doesn’t break the native apps (jellyfin and home assistant are the two that it breaks so far, and HA was very intermittent so I made a separate authelia rule and mobile DNS entry for slightly reduced rules)

    • proper umask rules on all docker directories (or as much as possible)

    • main drive FDE with a separate boot drive with FDE keyfile on a dongle that is removed except for updates and booting to make snatch-and-grabs useless and compromising bootloader impractical

    • full disk encryption with passworded data drives, so even if a smash and grab happens when I leave the dongle in, the sensitive data is still encrypted and the keys aren’t in memory (makes a startup script with a password needed, so no automated startups for me)

    For more info, I followed a lot of stuff on: https://github.com/imthenachoman/How-To-Secure-A-Linux-Server