do. command. safety. ?
bobsneidar at iotecdigital.com
Fri Mar 30 17:49:56 CEST 2018
Any shell command that can do anything dangerous is typically protected by the host OS. You could not for example install software in a way that would bypass UAC in Windows. You *could* conceivably delete all the files in a folder I suppose, but you couldn't copy files to a protected location. Essentially anything the end user is capable of doing, LC can do, but this is not unique. You can say that about any application. If the IT department has given complete write access to everything to all their users (a common practice I am learning as I interact with our customer IT departments) then it's not up to LC to try to protect themselves from themselves.
> On Mar 30, 2018, at 08:43 , Tom Glod via use-livecode <use-livecode at lists.runrev.com> wrote:
> Dear Geniuses
> Sometimes.... late at night just before falling asleep I think about the
> dangers of the do command. Is it possible to inject code into this
> mechanism through malware?
> I do not have enough understanding of operating systems and their processes
> ...and the livecode engine....to be able to know if its a reasonable
> question or not.
> Thanks for any input on this.
More information about the use-livecode