PROBLEM: Fatal error about being unable to find the suiduser
Kismet drops the privileges of the main packet processor to a specified
user for security - handling hostile remote data as root is just a bad
idea. If a nonexistent user is specified, Kismet will bail.
FIX: Set a valid user as the suiduser config variable. If you're sure you
don't want privilege dropping, you can run configure with the
'--disable-setuid' option, but this is NOT reccomended for most users.
But how to set a valid user as the suiduser config variable??? in BT3???