Re: Parameter Overflow Attack?
From: Mark Gordon (spamtrap@flash-gordon.me.uk)
Date: 11/28/02
- Next message: JayMore: "Re: How to do HTTP authentification "digest" method ?"
- Previous message: Bill Unruh: "Re: How to encrypt password forms in my web app? (Can't SSL)"
- In reply to: Walter Roberson: "Re: Parameter Overflow Attack?"
- Next in thread: Barry Margolin: "Re: Parameter Overflow Attack?"
- Reply: Barry Margolin: "Re: Parameter Overflow Attack?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 28 Nov 2002 22:33:19 +0000 From: Mark Gordon <spamtrap@flash-gordon.me.uk>
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 ;-)
> Real machines are much more
> complex, passing some items in registers, worrying about alignments,
> having to account for structs, possibly doing varargs differently.
> See for example this description of an ABI for SGI -N32 (MIPS cpus):
> http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0650&db=bks&fname=/SGI_Developer/books/Mpro_n32_ABI/sgi_html/ch02.html&srch=calling%20conventions.cc.umanitoba.ca>
<snip>
I knew that things were more complex within a module, especially when an
optimiser gets involved. However, I did not know (or ad forgotten) that
on some systems the frame pointer is used so parameters can be the other
way up. However, in my defence, I was using the term "standard C calling
conventions" because that was how I had previously seen it described.
The SGI ABI provides the same resiliance against too many parameters as
what I described as the standard C calling conventions.
-- Mark Gordon Still learning.
- Next message: JayMore: "Re: How to do HTTP authentification "digest" method ?"
- Previous message: Bill Unruh: "Re: How to encrypt password forms in my web app? (Can't SSL)"
- In reply to: Walter Roberson: "Re: Parameter Overflow Attack?"
- Next in thread: Barry Margolin: "Re: Parameter Overflow Attack?"
- Reply: Barry Margolin: "Re: Parameter Overflow Attack?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|