News for hackers. Stuff that matters.
Re:Proposal for a Friendly Dialect of C by Too on Wednesday August 27, 2014 @04:00PM (#8234432)
The security critical programs I've worked on, nobody would even think of randomly upgrading the compiler just because a new version happens to be available.
Re:Proposal for a Friendly Dialect of C by wglb on Wednesday August 27, 2014 @04:37PM (#8234602)
But take OpenSSL as an example of a critical security program. Nothing in the usage practice suggests not upgrading the compiler, or even going to the next version of libc.
Re:Proposal for a Friendly Dialect of C by duskwuff on Wednesday August 27, 2014 @04:31PM (#8234575)
Many open-source programs can be security-critical (any network-facing daemon, for instance), and there's nothing which ties them to a specific compiler.
Re:Proposal for a Friendly Dialect of C by userbinator on Wednesday August 27, 2014 @05:32PM (#8234808)
"security-critical" means different things to different people.

For some (many?), the failure of a security-critical system means unauthorised access to information.

For some, the failure of a security-critical system means people could die.

In the latter case (e.g. medical devices), having a stable environment is far more important than having the latest version.

Re:Proposal for a Friendly Dialect of C by duskwuff on Thursday August 28, 2014 @12:31AM (#8235888)
I usually hear the latter type of system described as "safety-critical" or "life-critical". You're right that it's an entirely different world, though.
Re:Proposal for a Friendly Dialect of C by jacquesm on Wednesday August 27, 2014 @07:30PM (#8235203)
It is the difference between security critical and mission critical.