null_ptr0

well on my older desktop i recently added a dual boot with kubuntu, so now it has kubuntu 7.10 and windows xp (im thinking sp2). well im hoping its not sp2, because of the dreaded raw-sockets kill. so i wrote a simple syn flooder with kate and compiled with gcc, when, to my suprise, didn't work. the following socket() call failed and produced the perror("socket()") call.
im afraid that this is because windows has already messed with the networking drivers and disabled raw sockets.
if anyone here has some insight, please help

edit:
i believe nmap does work (port scanning atleast). im severely confused.

Jimbo

drivers would be specific to the OS running at the time...

__________________
<insert disclaimer here>
<insert shameless plug for Visual Studio here>

null_ptr0

yeah i shortly realized that after i pressed submit. disregard the whole post, i just needed to supply root password again by appending sudo infront of it

Jabo

Is there something wrong with raw sockets? networking challenged here.

Jimbo

Not sure, but I'd guess it requires root privileges, hence the need for sudo.

[edit:] actually, this makes sense. Giving raw network access seems (to my slightly buzzed mind, had a couple drinks this evening) like a very possible security risk, hence the need for - as Vista so well puts it - elevated privileges. Requiring anything using raw sockets to either run as root or call setuid() to get root privileges seems like a feasible requirement.

__________________
<insert disclaimer here>
<insert shameless plug for Visual Studio here>

null_ptr0

jimbo and jabo, in windows xp sp2 and above, raw sockets are disabled at driver level.

EDIT:
sorry for the bump

Jimbo

Even so, the problem was occurring in Kubuntu, wasn't it?

__________________
<insert disclaimer here>
<insert shameless plug for Visual Studio here>