<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Hey, Anthony.</div>
<div> </div>
<div>I think you are making an argument for argument's sake, but I don't see it as black and white. ;-)</div>
<div> </div>
<div>DNA is probably the most complex input string you can imagine, so I'm not surprised they managed to do that. Naturally occurring viruses break complex systems coded in DNA for eons now... We're a bit late to the party.</div>
<div> </div>
<div>Now, sensor input might or might not be able to break a system. Can't see how numeric data will do that easily, though. I guess it's possible, but it's a lot easier to protect against, too.</div>
<div> </div>
<div>I will not deny there's risk, but in this case the risk is small. BTW, I do not wish to make the case that a small system <em>should</em> be written in C. I think there's good reasons for it to be done in Rust or other languages.</div>
<div> </div>
<div>I don't think it's a panacea, either. For existing systems, risk inherent in the existing system has to be weighed against the effort and bugs introduced by rewriting a system. And that is an entirely different business case, one which keeps countless Fortran and Cobol libraries alive because a known bug is often preferrable to a rewrite, for example when considering engineering applications where a minor error in computing outcomes can lead to catastropic outcomes in the real world.</div>
<div> </div>
<div>The bigger an existing is, the worse the business case for a rewrite is. Not saying it should not be done, but it should be evaluated impartially first. This includes honestly evaluating whether enough volunteers can be found to even make it feasible. It might probably fail on that last count even if a clear gain in stability can be expected ... in the long run.</div>
<div> </div>
<div>Best regards,</div>
<div>Oliver</div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Samstag, 23. September 2017 um 10:29 Uhr<br/>
<b>Von:</b> "Anthony Ramine" <n.oxyde@gmail.com><br/>
<b>An:</b> "Oliver Korpilla" <Oliver.Korpilla@gmx.de><br/>
<b>Cc:</b> ok@cs.otago.ac.nz, "erlang-questions Questions" <erlang-questions@erlang.org><br/>
<b>Betreff:</b> Re: [erlang-questions] Erlang VM in Rust</div>
<div name="quoted-content">Just forge input to the sensor in such a way it triggers a buffer overflow or something else in it.<br/>
<br/>
Nowadays we can even forge DNA strands to confuse DNA readers so…<br/>
<br/>
<a href="https://twitter.com/bldgblog/status/895728956724322304" target="_blank">https://twitter.com/bldgblog/status/895728956724322304</a><br/>
<br/>
> Le 23 sept. 2017 à 09:28, Oliver Korpilla <Oliver.Korpilla@gmx.de> a écrit :<br/>
><br/>
> Having said that I see no immense security risk in writing code for a remote sensor in C. It avoids one of the prime security risks: human user interactions<br/>
</div>
</div>
</div>
</div></div></body></html>