Critical Security Issue Identified in iTerm2

Re:Critical Security Issue Identified in iTerm2 by CJefferson on Wednesday October 09, 2019 @05:57PM (#21208601)

While I have no concrete evidence, I would strongly suspect you should worry much more about security holes in your OS than in iTerm2.

[ Parent | on HN ]

Re:Critical Security Issue Identified in iTerm2 by rurban on Thursday October 10, 2019 @01:37AM (#21211269)

You mean the holes they are adding in the latest years? macOS wasn't getting better since SnowLeopard. The HW neither.

[ Parent | on HN ]

Re:Critical Security Issue Identified in iTerm2 by jhanschoo on Thursday October 10, 2019 @02:37AM (#21211585)

If you're running a current version, then vulnerabilities are being patched as they are updated.

If you're running a version that is not receiving security updates, you remain vulnerable to vulnerabilities discovered (perhaps in later versions using same code) after the updates have ceased.

[ Parent | on HN ]

Re:Critical Security Issue Identified in iTerm2 by rurban on Thursday October 10, 2019 @09:58AM (#21214554)

I'm running a version which is not yet vulnerable to file system destruction (also mine still is case-sensitive as it started), and is not vulnerable to critical discoveryd/mDNSResponder and Mail bugs.

It's a complicated pro-contra decision, but in Apple's case it's an easy decision. They have abandoned all developer good will some years ago already.

Running current versions is rarely advisable. Just see the gcc-9 disaster.

[ Parent | on HN ]