Re: Parameter Overflow Attack?

From: Barry Margolin (barmar@genuity.net)
Date: 11/30/02 

From: Barry Margolin <barmar@genuity.net>
Date: Sat, 30 Nov 2002 06:25:33 GMT

In article <20021128223319.220e64dd.spamtrap@flash-gordon.me.uk>,
Mark Gordon <spamtrap@flash-gordon.me.uk> wrote:
>On 28 Nov 2002 19:09:35 GMT
>roberson@ibd.nrc.ca (Walter Roberson) wrote:
>
>> In article <20021128164153.41e80c7b.spamtrap@flash-gordon.me.uk>,
>> Mark Gordon <spamtrap@flash-gordon.me.uk> wrote:
>> :Also, the normal C calling conventions are that the parameters are
>> :pushed on to the stack in reverse order, followed by the return
>> address:so the called routine would see everything correctly. The
>> caller is then:normally responsible for removing the parameters from
>> the stack.
>>
>> I do not think that you are correct that this is
>> "the normal C calling convention".
>
>I did not say normal, I said standard ;-)

Huh? Your message is quoted above, and the third word is "normal".

But if you meant standard, which standard were you talking about? I don't
think ISO/ANSI C specifies the way in which arguments are passed, nor do
any of the Unix specifications (POSIX, SUS, etc.). This type of detail is
generally covered in ABIs, not standards that deal with source code only. 

-- 
Barry Margolin, barmar@genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.

Relevant Pages

  • Re: Is C99 the final C? (some suggestions)
    ... > Dijkstra's weighted shortest path algorithms were nice for client-server based ... but the future is peer 2 peer. ... >>The C standard specifies what is UB and what's not. ... I can do no such thing with stack ...
    (comp.lang.c)
  • Re: Is C99 the final C? (some suggestions)
    ... > the standard? ... There doesn't have to be any mention of "stack" in what I try to ... "There are five standard signed integer types, ... standard-like language. ...
    (comp.lang.c)
  • Re: Toward a Forth thats easier to learn
    ... Because loops use the return stack. ... standard. ... portability. ... I'm saying that writing standard code demands new ...
    (comp.lang.forth)
  • Re: Why GCC does warn me when I using gets() function for accessing file
    ... standard does not define the term "variable". ... other people keep claiming -- that C doesn't have a stack (if function ... Where the analogy falls down, however, is that that above code can be ... but the standard *CANNOT* specify that guarantee. ...
    (comp.lang.c)
  • Re: Required stack size
    ... Any C implementation must implement a "stack", ... but the proposed solution won't work. ... My point is not that I know of any real-world implementations for ... would not violate the standard, and the proposed solution is therefore ...
    (comp.lang.c)