> >> clobbering the frame pointer or the return address. I think some
>>>>> malware uses this.) f the frame pointer and return address are in a
>>>>> separate stack, there's less danger; if you don't go too far beyond
>>>>> the array, you can only clobber other declared variables.
>>>> Thanks Keith, you saw my point!!!
>>>> In addition, I just want to show that it is possible. I don't want to
>>>> implement it in Windows yet. If I can show that it works for a x86-
>>>> linux, it will be ok for me.
>> There may be existing practice for this. 'm not familiar with the
>> internals of either lcc or lcc-win, but if they don't support this you
>> might look at other compilers.
>> Keith Thompson (The_Other_Keith) XXXX@XXXXX.COM http://www.yqcomputer.com/
> "We must do something. his is something. herefore, we must do this.">
> -- Antony Jay and Jonathan Lynn, "Yes Minister"
I need to split the DATA segment in two pieces. One will hold
variables that I will assume "secure" and the other that I will call
"insecure". The idea is how to identify variables defined by the
programmer and used for the program itself like a counter (secure)
from variables that come from an input (insecure). How I can handle
it? Can I define a new attribute, e.g. s_int (secure int) or i_int
(insecure int)? How I will pass that information for the back-end
compiler in order to assign each variable in the correct DATA segment?
This is my idea: I am thinking in handling the two segments with two
different addresses or offsets; however, how the system will be assign
one of them? I guess it will need extra information, and for this
reason I think in a new attribute. The attribute will be used for the
programmer, who will define what variables is "secure" or no (high
At the same time, my goal is to implement it and prove that it is
possible, but I am not sure if lcc or lcc-win are the compilers that I
need. Can I modify lcc-win at the same way that lcc? Someone has
installed lcc in a Ubuntu-PC?