Password sniffers....

[wilnix]

http://www.ibrado.com/sock-faq/

Try google for some more...

Wilnix

[Metgod]

http://www.ecst.csuchico.edu/~beej/guide/net/

Also, there are books on socket programming...
Uh.. can't think of the name off hand but.. UNIX Network Programming
might be the name.. look it up on Amazon and like Will said, a search engine...

[wilnix]

Metty probably knows better then I do, and it seems there is a lot online if you search.

Wilnix

[godaigo]

Thanks alot! It seems like this is something of a required subject if I'm gonna be doing anything in Unix. Of course my college classes really didn't address anything outside of "this is a program, here's how it's written" of course they don't tell you how it apply's to anything, or how to connect it to anything outside of your own projects structure! Thank god(or whatever  ) that I like to work out stuff on my own! Thanks again these two sites look like they'll get me started. Once the ball starts rolling....

[Metgod]

no problem..

[wilnix]

next.  

Wilnix

[f0x]

http://www.manualy.sk/sock-faq/unix-socket-faq.html
http://www.scit.wlv.ac.uk/~jphb/comms/sockets.html
http://pont.net/socket/
http://www.cs.rpi.edu/courses/sysprog/sockets/sock.html
http://www.uwo.ca/its/doc/courses/notes/socket/
http://www.cs.cf.ac.uk/Dave/C/CE.html

i am trying to do the same thing. well here are some of my bookmarks. keep me posted okie

[Metgod]

I've seen some of these, and they do have some good stuff. will probably check the others out as it's always neat to have more stuff to refer to. So thanks.

As an aside, and some caution....

(and MS is probably the biggest cuplrit here since they love breaking standards ... and I"m probably stating the well known but ah well ...)

main() must be int in the ANSI C standard (and I see in one of those links they don't specify at all and rely on compilers -- which is a bad bad practice). It's true that most compilers default it to int (especially K&R compilers), but... it's best to specify int (and not void or anything else). And prototypes are your friend indeed! But MS's C code is inherently broken (since they specify void) and won't work everywhere.

One thing I'd recommend is usually specifying -Wall in gcc.

Oh, and valgrind and dmalloc are quite useful. Never tried electric fence or the others, but valgrind is my favourite (saved me on several occasions I might add), plus doesn't really i nvolve modification of code -- just specifying debug symbols to be inserted into the executable.

Hope I didn't horribly bore you all, haha

[Metgod]

Also check this thread...

http://forum.hfactorx.org/index.php?board=34;action=display;threadid=1598

And a favourite of mine ....

http://www.gnu.org/prep/standards/standards.html

and can't forget the C FAQ!

http://c-faq.com/

Also check

http://cslibrary.stanford.edu (although I don't like some of this one's style and probably other things, but probably useful anyway).