News for hackers. Stuff that matters.

A comment on Ubiquiti all but confirms breach response iniquity. Parent comment

Re:Ubiquiti all but confirms breach response iniquity by de6u99er on Sunday April 04, 2021 @07:59PM (#26693927)
This reads like a horror story, but reminds me of a guy my boss hired once against my objections.
[ Parent | on HN ]
Re:Ubiquiti all but confirms breach response iniquity by tediousdemise on Sunday April 04, 2021 @08:09PM (#26694000)
Indeed. Even more terrifying is using an unsafe language like C rather than Rust or C++ for systems development. shudders
[ Parent | on HN ]
Re:Ubiquiti all but confirms breach response iniquity by bogwog on Sunday April 04, 2021 @10:57PM (#26694861)
C++? Safe??
[ Parent | on HN ]
Re:Ubiquiti all but confirms breach response iniquity by tediousdemise on Monday April 05, 2021 @07:53AM (#26697840)
Smart pointers? Automatic memory management?
[ Parent | on HN ]
Re:Ubiquiti all but confirms breach response iniquity by UncleMeat on Monday April 05, 2021 @08:29AM (#26698099)
They help a little. But there are so many more ways of introducing vulns to C++ programs than just double frees and use-after-free. Replacing all your pointers with shared_ptr won't give you a safe program. Not even close.
[ Parent | on HN ]