Just stumbled across this (overly dramatic?) article and thought I’d just post it here…

It’s more to act as a reminder that if you’ve got a NAS that is serving content to the interwebs, then make sure it’s behind a proxy of some kind to prevent weaknesses (ie in the management Web UI) being exposed.

Obvz, this article is pointing to Zyxel, but it could be your DIY home-built NAS with Cockpit: CVE-2024-2947 - just an example, not bashing that project at all.

I’ve used Squid and HAProxy over the years (mostly on my pfSense box) - but I’d be interested to know if there’s other options that I’ve not heard of

  • schizo@forum.uncomfortable.business
    link
    fedilink
    English
    arrow-up
    16
    ·
    23 days ago

    As someone who isn’t a fan of e-waste, I really hate these little “appliance” type NASes. Companies abandon them while they’re still perfectly usable and meeting someone’s needs, and tell you oh sorry, I guess you should buy a new one and throw your current one away. (Which, annoyingly, the article also does.)

    • HumanPerson@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      23 days ago

      I agree, though I wouldn’t blame the article. If it is insecure, you shouldn’t be using it unless it is set up to allow you to run a real os on it.

      • schizo@forum.uncomfortable.business
        link
        fedilink
        English
        arrow-up
        7
        ·
        23 days ago

        I mean I’m not blaming anyone other than the manufacturers who make things and then arbitrarily decide to stop supporting them while they’re still perfectly usable, leaving basically no choice other than trashing and buying a new one.

        • SayCyberOnceMore@feddit.ukOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          23 days ago

          Agreed.

          If the hardware’s standard, then it’s possible for people (us) to keep these things out of the ground / incinerator for a few more years, but if it’s custom / proprietary stuff, then that’s just terrible.

    • peregus@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      19 days ago

      Totally agree! Also, at work we have some Synology and their web UI is soooo slow that it’s almost unusable

  • Moonrise2473@feddit.it
    link
    fedilink
    English
    arrow-up
    14
    ·
    23 days ago

    I had one of those NAS (NSA320). Even when they were new and suppoted they were using some ancient custom version of linux with ancient packages. It would be insane to expose them on the internet.

  • Matt The Horwood
    link
    fedilink
    English
    arrow-up
    4
    ·
    23 days ago

    Depending on the login flow, I have a lot of stuff behind an oauth proxy. So that you have to have a working 2fa account to see the non 2fa system behind.

    • SayCyberOnceMore@feddit.ukOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      23 days ago

      I must get around to looking into 2FA / MFA sooooon (next ~5 years)

      Did you find it really straight forward to get setup?

      I think the fear of getting started with these things is sometimes worth it (home system offline for days) but often it’s quite simple…?

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    1
    ·
    22 days ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    HTTP Hypertext Transfer Protocol, the Web
    NAS Network-Attached Storage
    nginx Popular HTTP server

    [Thread #831 for this sub, first seen 26th Jun 2024, 05:55] [FAQ] [Full list] [Contact] [Source code]