3 ms·
> Applications can now opt-in to requiring secure coding for their saved state by returning TRUE from this method. Unless an app opts in, it will keep allowing
by shp0ngle 4y ago
> Applications can now opt-in to requiring secure coding for their saved state by returning TRUE from this method. Unless an app opts in, it will keep allowing non-secure coding, which means process injection might remain possible.
> This vulnerability will therefore be present for as long as there is backwards compatibility with older macOS applications!
This sounds… really really bad?
- shp0ngle 4y agoalso the first footnote is very bizarre
- jshier 4y agoNSSecureCoding is so old at this point (macOS 10.8, 2012) that anyone still writing Obj-C who hasn't adopted it is essentially committing malpractice.
- Sohcahtoa82 4y agoI mean...people are still writing code with textbook SQL injection and XSS vulnerabilities. A startling number of developers know nothing about security.
- deleted 4y ago[deleted]