TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

CoreGraphics Memory Corruption

67 pointsby ssclafaniover 10 years ago

2 comments

walterbellover 10 years ago
No security fix for "arbitrary code execution" on iOS7. Why must users accept new functionality (and bugs) in iOS8 when this and other security bugs could have been fixed in iOS7? How long ago was Apple aware of this vulnerability - was release of the fix delayed until iOS8 in order to force everyone to upgrade?
评论 #8349203 未加载
评论 #8349677 未加载
评论 #8349217 未加载
pjmlpover 10 years ago
Oh look a buffer overrun exploit! In C, who would guess?<p>Static analyzers for C exist since 1979, but why use them...<p>&quot;Although the first edition of K&amp;R described most of the rules that brought C&#x27;s type structure to its present form, many programs written in the older, more relaxed style persisted, and so did compilers that tolerated it. To encourage people to pay more attention to the official language rules, to detect legal but suspicious constructions, and to help find interface mismatches undetectable with simple mechanisms for separate compilation, Steve Johnson adapted his pcc compiler to produce lint [Johnson 79b], which scanned a set of files and remarked on dubious constructions. &quot; -- Dennis Ritche on history of C.
评论 #8349720 未加载