tssci security

Kismet, ipw2200, and wireless injection

To get Kismet to run under the ipw2200 driver, simply edit /etc/kismet/kismet.conf. Here is the diff -u output:

--- kismet.conf.orig    2007-04-03 13:51:29.000000000 -0700 +++ kismet.conf 2007-04-03 13:53:55.000000000 -0700 @@ -7,10 +7,10 @@ version=2005.06.R1

# Name of server (Purely for organizational purposes) -servername=Kismet +servername=thinker

# User to setid to (should be your normal user) -#suiduser=your_user_here +suiduser=marcin

# Sources are defined as: # source=sourcetype,interface,name[,initialchannel] @@ -19,7 +19,7 @@ # The initial channel is optional, if hopping is not enabled it can be used # to set the channel the interface listens on. # YOU MUST CHANGE THIS TO BE THE SOURCE YOU WANT TO USE -source=none,none,addme +source=ipw2200,eth1,addme

# Comma-separated list of sources to enable.  This is only needed if you defined # multiple sources and only want to enable some of them.  By default, all defined

I have not gotten wireless injection to work with aircrack-ng or any of the other wifi tools. I came across this thread which details how to get injection to work using a modified ipw2200 driver. I am using Ubuntu (kill me?) and this post might be helpful as well.. I started following steps without reading them all first and ended up deleting some ieee80211 modules I had trouble later tracking down. Note to self: backup any files that may get deleted before attempting anything new.

You get burned playing with FIRE

I wish I had posted this when I first wanted to about four weeks ago, (and maybe have saved some people from losing money) but SourceFire was not a good investment! No matter how much I support Snort IDS as an open source project, I don't want to put what limited, hard earned money I have into a company that's failing to meet financials, in debt up to their necks, and slowing growth and revenues. From what I could tell, people jumped on the SourceFire bandwagon just because it was a security company and had friends in the game. In the game of stocks, I think Jim Cramer says it best "I'm not here to make friends, I'm here to make money."

ShmooCon Video Reviews

LonerVamp has been watching ShmooCon videos all day long and has posted his thoughts on several of them.

My favorite talks (that have been uploaded) from ShmooCon are the following:

Also, be sure to check out the guys from Hak.5, who posted their latest vidcast (2x09).

ShmooCon 2007 Videos

ShmooCon 2007 videos are up. Check out http://www.shmoocon.org/2007/videos/.

What's the big deal about WEP??

Andy IT Guy writes, "I think we need to focus on in not how to crack what is already broken but how can we protect what is using it. I'd love to see WEP go away but it won't happen anytime soon." Andy hits the nail right on the head with this one. A lot of people are just starting to get WEP enabled on their old wireless 802.11b access points, and to tell them they need to upgrade again just for security isn't going to convince many of them. Here's my reasoning for sticking with WEP:

I am still using WEP, because I don't feel like going out and replacing all two wireless cards in my computers to support WPA. I'm a college student and don't have the money to spend frivolously on every new technology (even if it is better or more secure) that comes out. Every time I hear about [the insecurity of] WEP, bells ring telling me to upgrade, but I keep pushing it off. Maybe until a new standard is ratified, maybe not.

« Newer entries — 39 — Older entries »

blog comments powered by Disqus