I don't think it's a matter of programming standards. The methods used to exploit systems are almost always something you could never have guessed. Flaws in code can be extremeny difficult to see, as was the case in the SSL Heartbleed bug. None of the devs saw the bug when it was approved for merging. Seeing what it was and what it ought to have been would be like seeing a needle in a haystack. I have thought for some time that it is the nature of digital information and our human minds incapacity to comprehend it in its real form that makes it nearly impossible to produce "unhackable" code.
Bob S > On May 18, 2017, at 19:48 , Kay C Lan via use-livecode > <use-livecode@lists.runrev.com> wrote: > > On Tue, May 16, 2017 at 6:46 PM, Mark Waddingham via use-livecode > <use-livecode@lists.runrev.com> wrote: >> >> I'd at least hope that 'smart cars' software is engineered to a much >> higher standard than other places: >> > Well it may not even be 'smart' cars, even just modern cars may have > problems depending on circumstances. This article also raises an > interesting issue with regard to Uber and/or similar: _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
