Re: Port binding under linux in ASM
- From: Evenbit <nbaker2328@xxxxxxxxxxx>
- Date: Thu, 24 Apr 2008 12:02:26 -0700 (PDT)
On Apr 20, 9:52 am, tin.cans.and.str...@xxxxxxxxx wrote:
On Apr 20, 1:52 am, Frank Kotler <fbkot...@xxxxxxxxxxx> wrote:
But at the "sys_call" level, there's really only one - "mov eax, 102"
- ebx takes the "command", or "subfunction", "SYS_SOCKET",
"SYS_BIND", "SYS_CONNECT", etc. and ecx takes a pointer to
a "parameter structure". The meanings of the parameters differs
depending on which "subfunction" we're doing, but (for some reason)
we recycle the same "structure".
Righto - and there's a dearth of information available on the web
concerning how to make use of the socketcall function at the assembly
level.
If you can find a tutorial on how to do it from C (or other language)
-- it would give you a good start.
I imagine that the process would not be too different from how to do
it in Windows. There is a simple "instant message" example here:
http://flatassembler.net/examples/quetannon.zip
We can use the loop-back address {127.0.0.1} for testing during
development.
Nathan.
.
- Follow-Ups:
- Re: Port binding under linux in ASM
- From: tin . cans . and . string
- Re: Port binding under linux in ASM
- References:
- Port binding under linux in ASM
- From: tin . cans . and . string
- Re: Port binding under linux in ASM
- From: Chuck Crayne
- Re: Port binding under linux in ASM
- From: tin . cans . and . string
- Re: Port binding under linux in ASM
- From: tin . cans . and . string
- Re: Port binding under linux in ASM
- From: tin . cans . and . string
- Re: Port binding under linux in ASM
- From: Chuck Crayne
- Re: Port binding under linux in ASM
- From: Frank Kotler
- Re: Port binding under linux in ASM
- From: tin . cans . and . string
- Port binding under linux in ASM
- Prev by Date: Re: delete bytes
- Next by Date: Re: Port binding under linux in ASM
- Previous by thread: Re: Port binding under linux in ASM
- Next by thread: Re: Port binding under linux in ASM
- Index(es):