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.
[ Parent
| on HN ]
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.
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.