Archive for August 3rd, 2009

DEFCON notes: Day 3, or “Killing Priest won’t bring back your G–d–n honey!”

Monday, August 3rd, 2009

Apparently, one of the pools at the Riviera was overrun by killer bees. The fake ATM has been well covered elsewhere.

Final set of quick takes:

RAID Recovery: Recover Your PORN By Sight and Sound”: Technically, a pretty decent presentation on recovering RAID, building on Moulton’s previous presentations on the inner workings of hard drives and their recovery/rebuilding. (Those presentations are linked here: I’m actually pretty interested in the one on SSD drives.)
Key takeaways:

  • Many people don’t understand RAID levels; they think that RAID 0 actually offers some protection against data loss, or there’s no hurry to replace that one drive in the RAID 5 that failed. (The presenter seemed to believe that photographers are particularly bad about these things, perhaps based on bitter personal experience.)
  • If you have a RAID full of pictures, some sub-$100 tools, along with intelligent analysis of reconstructed images, can help you rebuild the array. Even if you don’t know what order the drives were in originally.

“Cracking 400,000 Passwords, Or How To Explain to Your Roomate why the Power Bill Is a Little High” (preview): Or, how to use John the Ripper, and how to optimize your JtR runs.
Key takeaway: Lists of previously cracked passwords are good fodder for JtR. Would you believe people use the same password on more than one site? Even better, you can use lists of previously cracked passwords to build JtR word mangling rules.

People who deserve a “Thank You” (part 1 of an ongoing series)

Monday, August 3rd, 2009

Joseph Hall, for his excellent set of instructions on setting up WireShark under OS X.

Dining in Las Vegas 2009

Monday, August 3rd, 2009

So where did I eat while I was in Las Vegas?

Well, I had a great meal Thursday night at Lotus of Siam, one of my favorite restaurants in the world.

Breakfast on Friday morning was at Blueberry Hill on Flamingo, one of the locations of a very good local chain. Friday night dinner was at a place called Himalayan Cuisine, also on Flamingo, which serves Nepalese, Tibetan, and Indian food; the lamb Sekuwa was quite good.

Saturday night, I decided to try one of the local oddities (at least, I think this is local; I haven’t run across it in Austin or any other cities); all you can eat sushi, in this case at Yami Sushi, also on Flamingo. (Are you detecting a trend here?) Decent sushi at a reasonable price (about $23 for the all-you-can-eat option). However, there’s an extra charge if you don’t eat the rice, there’s an extra charge if you don’t clean your plate…I was slightly put off.

Sunday breakfast: The Egg and I, one of two locations of a local family-run chain. The egg puns are a little tiresome, but the food is wonderful; this gets an official Whipped Cream Difficulties endorsement. (Try the Collision Course; it will keep you going all day long.)

Sunday dinner: I was a little disappointed by the Tillerman last year, and tried to come up with a better idea. However, I couldn’t, the closing ceremonies ran long, and…well, I ended up back there again this year. Good thing; they’ve added a new “Monthly Specials” menu (not on their website), and the rainbow trout with a honey/citrus sauce was very good, and a steal at $22 (including mashed potatoes and the Tillerman’s massive “salad bar”).

DEFCON notes: Day 2

Monday, August 3rd, 2009

Saturday was a little calmer than Friday from my perspective. Part of the reason for that may have been Adam Savage‘s talk (and the meet and greet afterwards) took a lot of folks out of circulation for two or three hours. (I didn’t go.)

More quick takes:

“Hacker vs. Disasters Large & Small”: Michael Schearer, who did the first part of the presentation, also did the Hacker In Iraq presentation. As a Naval officer, he went through SERE school, so he’s got some hands-on survival experience which makes him worth paying attention to. Schearer’s part of the presentation basically covered short-term wilderness survival (as in, “I’m cold and there are wolves after me.“) and was more practical. Renderman’s half of the presentation was a more long-term, “How do we survive and rebuild society after the Big One?”, philosophical presentation. (Edited to add: links to the final versions of the slides; Part 1, Part 2.)
Key takeaways:

  • “Hacker skills are largely compatible with the skills necessary to survive in the wilderness or during a natural disaster.”
  • “Don’t be squeamish about breaking or destroying something to help you stay alive.”
  • “You are not Jack Bauer, MacGuyver, or Survivorman; you need practice to survive.”

“Personal Survival Preparedness”: Nice guy, okay talk, mostly dealing with survival in an urban environment after some devastating event (Katrina or worse).

“Picking Electronic Locks Using TCP Sequence Prediction”: Excellent presentation, short, and scary. Brief summary: many electronic lock systems are IP based and the traffic on the network is not encrypted. This makes the locks vulnerable to a man-in-the-middle attack (to capture an unlock command) and a replay attack with a spoofed TCP sequence number (to replay the command). These attacks bypass the existing control software, so the spoofed unlock command leaves no audit trail. The author is a network admin at Texas State University; woo hoo! Greater Austin/San Marcos Metropolitan Area represent!

Sniff Keystrokes With Lasers/Voltmeters”: Two pretty amusing guys with another excellent presentation. In the first half, they presented an attack on PS/2 keyboards with very simple hardware; all you need is a slightly hacked power cord connected to a common circuit with the computer in question on one end, and an ADC plus a micro-controller (for data acquisition, filtering, and storage) on the other and viola! In the second half, they outlined a acoustic-based attack that builds on previous research, combined with microphone hardware using freaking laser beams. As the authors said, “How cool is that?”
Key takeaway: “girls will melt when you show this…”

“Bluetooth, Smells Like Chicken”: Pretty much what I expected from the summary. Using software-defined radio gear (about $1000) you can monitor the Bluetooth frequencies. Bluetooth does frequency hopping over about 79 MHz, and the software-defined radio gear can only monitor about 25 MHz (max) at one time. But you can monitor one channel and use information from that packet to actually predict the frequency hopping cycle. The authors also presented a technique that allows aliasing of the entire Bluetooth spectrum to the 25 MHz available in the radio gear they were using without compromising the ability to extract packets. Finally, they discussed Bluetooth attacks using off-the-shelf sub-$10 hardware to sample and inject data.

Key takeaway: there is no longer any such thing as a non-discoverable Bluetooth device.