PlayingPossum

10 ms·

1. 1.▲
   by PlayingPossum 2y ago

   It is still being used by a cool open-source project, Kazoo, which is essentially a multi-tenant PBX.
2. 2.▲
   by PlayingPossum 2y ago

   Exactly, and I think you'd expect the people managing those servers to be experts and do their job. That's the whole point of what I wrote.
3. 3.▲
   by PlayingPossum 2y ago

   That's the point - you don't need to know your stack. You don't need to worry if CUPS is installed, enabled, or listening on your interface. You don't need any of that, as long as you do the bare minimum and configure yo
4. 4.▲
   by PlayingPossum 2y ago

   Seriously, anyone who disagrees with that ends up with even bigger problems, like getting hit by ransomware. You, not some developer or Linus Torvalds or anyone else, are responsible for your client and your data. If you put your server on
5. 5.▲
   by PlayingPossum 2y ago

   To be fair, most regular users are not impacted by this vulnerability. That is exactly what is written in the article.
6. 6.▲
   by PlayingPossum 2y ago

   I mean, if you install your server and open it to the internet without securing it with a FW, what would you expect to happen?
7. 7.▲
   by PlayingPossum 2y ago

   Correct me if I'm wrong, but to be affected, don't you need to have UDP port 631 exposed to the outside world? Apologies for being a bit blunt, but if you're exposing services like printing to the internet that shouldn't