• @badbytes
    link
    512 hours ago

    Should be required to release source code after support lapses.

  • 𝕸𝖔𝖘𝖘
    link
    fedilink
    English
    2
    edit-2
    12 hours ago

    Maybe we should stop going for the D, and start going for the wrt

    Edit: added link.

  • @[email protected]
    link
    fedilink
    41 day ago

    This is the ones that were many years past EOL right? Like early 2000s shit? Or are they saying that for currently supported equipment now?

    • @rtxn
      link
      English
      7
      edit-2
      1 day ago

      Fine, I’ll read the article for you.

      (edit)

      however the company again said it wouldn’t be issuing a fix, since the affected devices have all reached EoL.

      • @[email protected]
        link
        fedilink
        English
        8
        edit-2
        1 day ago

        Yeah, but keep in mind that the EOL was set by D-Link, who also has an interest in selling you new devices and not spending a lot of money supporting older devices. If there are 60.000 devices connected to the internet, they are doing their work exactly how they should and are not at the end of their life - if D-Link fixes their own security hole.

        And let’s be honest: Some articles on some tech sites won’t get everybody who has one of those devices to buy a new one. We now have 58000 new bot net members on our beautiful internet

  • @[email protected]
    link
    fedilink
    English
    2
    edit-2
    1 day ago

    Roughly 60,000 vulnerable devices are currently connected to the internet, the majority being located in Taiwan.

    The model isn’t even available in the US, BleepingComputer states, since it reached EoL almost a year ago.

    I can’t see a product page that would disclose when it was available. Only their general And of Life Policy.