Paper fun: Concerns with Time-Space Based Wireless Security

I’m presenting this at worlcomp this year.


Wireless ad-hoc network protocols are a  topic of much recent discussion and development. This has prompted many researchers to develop interesting and promising-sounding protocols that should be considered and examined. One such protocol, Authenticated Protocol for Wireless Ad Hoc Networks (APEC), was designed by Robert Hiromoto and Hope Forsmann[1]. APEC has been the subject of an increasing amount of scientific discussion and research around Universities, Laboratories, and professional conferences. In this paper, we examine APEC in depth and discuss many potential problems with the protocol that must be addressed if APEC is achieve widespread acceptance.

Paper: probelm_with_time_0.7

An analysis of a Time Synchronization Protocol

madwifi == awesome

You know, with how much people tout the prism2 chipset, atheros sometimes gets looked over.


I mean, it’s got interfaces to act as vaps, to go in rfmon mode…  pretty cool.  I haven’t figured out how to reach the full potential of my prism2.5 card yet though, so I guess I’ll need more experimenting with both

Analysis of a proposed key-management scheme for DSN

Broadcom Wireless and Linux

Here is the “straightforward” way

see (
for more info.

  • Download this windows driver
  • unzip the file you downloaded.
  • run “ndiswrapper -i FILE” on any .inf files you downloaded.
  • run “ndiswrapper -l” and it should say “driver present hardware present” if not, there is a problem.


depmod -a
modprobe ndiswrapper

try “ethq wlan0 scan” if it worked, this should do something.


With Ubuntu for some reason it loads a bad driver you should blacklist. This issue is covered a bit better here:

Here’s another issue with Edgy. I got this email from a friend. My Wireless stopped working because the latest version was bad. Probably not an issue now, but if you’re having problems you may want to give it a shot.

hey rich
Speaking of the devil, yeah, i just figured that out like 3 minutes ago. From what i can tell, it seems like the new version of ndiswrapper (like 1.7?) screws things up. Or something. So i just downloaded and installed an older version of ndiswrapper. I got ndwiswrapper-1.27. i just downloaded and extracted the file, didn’t use apt-get. after that:

1. cd to the extracted directory of ndiswrapper-1.27
2. sudo make uninstall (ur supposed to do this until there are no errors…)
3. sudo make
4. sudo make install
5. then just do sudo ndiswrapper -i filename.inf for your driver.

Now mine works again, yay. The problem i had thought was i didn’t have the kernel headers so it wouldn’t compile ndiswrapper. i (eventually) did a sudo apt-get install linux-headers-2.6.17-10-386. Now if you’re running a different version of the kernel, then replace that last string with ur version. the command to get ur exact kernel is “uname -r”. so yeah….do that, then do the make uninstall, make, make install, and then it should work again. I don’t have the link for that 1.27 version download, but google should find it pretty quick.

So in summary, the best solution is probably to get rid of piece of shit broadcom chips :)


Get every new post delivered to your Inbox.

Join 33 other followers