Compile time executable calling?
Tofu Ninja
emmons0 at purdue.edu
Sat Jul 13 01:34:48 PDT 2013
On Saturday, 13 July 2013 at 07:13:37 UTC, Walter Bright wrote:
> On 7/12/2013 11:52 PM, BLM768 wrote:
>> On Saturday, 13 July 2013 at 04:23:56 UTC, Walter Bright wrote:
>>>
>>> A big problem with it would be the equivalent of the "SQL
>>> Injection Exploit".
>>> Since the compiler can now execute arbitrary code, someone
>>> passing around
>>> malicious source code could do anything to your system.
>>
>> Assuming that the user is compiling the code in order to run
>> it (which does seem
>> to be the most common case, at least in my experience), the
>> user is already
>> running arbitrary code. I don't really see how this would
>> create a greater
>> security risk than what already exists.
>
> People can be endlessly creative at this kind of thing. I'm not
> at all sure you and I have thought of every possible exploit.
Any idea how difficult such a thing would be to implement? Any
one willing to work on something like this? If something like
this was made, would it be included?
More information about the Digitalmars-d
mailing list