kismet

[purehate]

I had to learn vi all over again when i was building those openwrt routers

[.lonewolf]

Use kate... it's so beautiful

[Barry]

Use kate... it's so beautiful

Yes, yes she is. I'd love to use Kate....



Hey thorn, does that make up for the comment yesterday??

[.lonewolf]

Yes, yes she is. I'd love to use Kate....

She must be about twelve

Actually... she's only two years younger than me, so that makes me about fourteen

[Barry]

She must be about twelve

Actually... she's only two years younger than me, so that makes me about fourteen

She's a year older than me, so that makes her 30 something.

[drwalter]

I had kismet up and running perfectly although in the past week it started giving me some problems. I've been getting the Fatal: Specifying a uid-0 user for the priv drop is pointless.

This makes senes I guess I've got the line suiduser=root in my conf file. So I read through the readme and it suggested two things. First i tried running kismet with --disable-setuid although that didn't do anything and just pulled up the usage/help menu. Secondly I tried doing a make suidinstall which went through however I still got the same error. I figured the suiduser=root line in my conf file was the problem so I commented it, still nothing (it complained about not having a uidset). So now I'm out of ideas.

[PrairieFire]

I had kismet up and running perfectly although in the past week it started giving me some problems. I've been getting the Fatal: Specifying a uid-0 user for the priv drop is pointless.

This makes senes I guess I've got the line suiduser=root in my conf file. So I read through the readme and it suggested two things. First i tried running kismet with --disable-setuid although that didn't do anything and just pulled up the usage/help menu. Secondly I tried doing a make suidinstall which went through however I still got the same error. I figured the suiduser=root line in my conf file was the problem so I commented it, still nothing (it complained about not having a uidset). So now I'm out of ideas.

./configure --disable-setuid

Would be the correct usage.

[drwalter]

Thanks PrairieFire, it worked! I appreciate the help!

[theprez98]

./configure --disable-setuid

Would be the correct usage.

Thanks PrairieFire, it worked! I appreciate the help!

If you're the only user of this system, using this option is acceptable. However, remember Kismet's important warning about this:

REMEMBER: Installing Kismet suid-root is NOT SECURE ON MULTIUSER SYSTEMS.
Most users of Kismet are likely using single-user laptops or handhelds, where suidroot is very convenient. If you have ANY OTHER USERS ON YOUR SYSTEM, suidroot Kismet can be used to shut down the wireless and put files where you don't want to allow them to be put. If you have other users on your system, install kismet normally and 'su' to root before starting it.

[PrairieFire]

If you're the only user of this system, using this option is acceptable. However, remember Kismet's important warning about this:

Since when did people start reading, much less reading supplied documentation.