Smoked strawberries?

August 4th, 2009

As the founder of the Society for the Preservation and Restoration of Classic Cocktails, you would think that I would welcome the resurgence of interest in cocktails, and the growth of a contemporary “cocktail culture”.
Indeed I do. I am glad to see such things as craft bitters and mixers, as well as small-batch liquors. The availability of absinthe and absinthe like substances (other than Pernod) also makes me happy.
But I’m wondering if we’ve gone too far.

For discussion purposes, I direct your attention to the July 2009 Spirit, the Southwest Airlines in-flight magazine. Starting on page 70, we have the “Spirit Guide to Spirits“, which purports to tell you what tools, mixers, and spirits you’ll need to “replicate at home what everyone drank in the ’30s, ’20s, and earlier”. The article also provides helpful recipes from five of “the best mixologists in America”. This list includes Robert Heugel of Anvil Bar and Refuge, a place I’m very interested in trying next time I’m in Houston.

But let’s take a look at the recipes. Heugel’s recipe for the “Border Storm” is probably the least complicated (a mix of dark rum and ginger beer); I think this would probably work well with a good quality commercial or craft ginger beer. Heugel’s recipe, though, calls for preparing your own ginger beer; the process he gives for this takes about three days to complete, including two days of fermentation, and yields about 48 ounces of ginger beer.

Next up, we have something called “Ninety Years of Aviation”, which “goes best with a creme de violette ‘caviar’.” What that involves is freezing a container full of canola oil, preparing a mix of creme de violette, Parfait Amour, lemon juice, and gelatin, placing that mixture into a squeeze bottle, squeezing drops into the cold canola oil to make ‘caviar’, then washing the ‘caviar’ with cold water (to get the oil off, of course). All of this is for something that’s served alongside the drink itself (which is gin, lemon juice, and maraschino liqueur, shaken over ice and strained into a cocktail glass).

After that, we have the “Ramos Gin Fizz Marshmallow”, which appears to be a basic marshmallow recipe, except for added flavors from gin, lemon and lime juice, and orange blossom water. Ever make your own marshmallows? Neither have I. Is there a point to doing marshmallows? What was wrong with the classic Ramos Gin Fizz?

Next, there’s the “Nubo Di Fumo”, which calls for smoking two strawberries “with cherry wood shavings in a stove-top smoker box”. In addition, the “Nubo Di Fumo” also calls for three slices of “oven-dried strawberries, for garnish”. We also have tequila, Galliano, agave nectar, and Banyuls vinegar. Never mind that strawberries are the most overrated of fruits; again, what are we doing here? Is there a point beyond trying to impress people enough so that they’ll pay $11 for a cocktail? (I’m just guessing; the “Nubo Di Fumo” is not on the cocktail menu at Absinthe.)

Finally, we have the “Bacon Old-Fashioned”. Ah, a classic bourbon cocktail. Only in this case, the bourbon isn’t just bourbon; it is bourbon that’s been infused. How? “…pour the (bacon) fat into a large glass jar and add the spirit, then swirl together. Cover and let the mixture sit in a cool, dry place for three days to one week, then refrigerate for 24 hours.” After which you strain off the congealed bacon fat, and you’re left with bacon flavored bourbon. I like my bacon more than the next guy, but seems to me to be an example of “Just because you can do it, doesn’t mean that you should.”

What is wrong with us? Does it take cheap gimmicks like bacon-infused bourbon and fake caviar for us to try the drinks of our fathers?

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

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)

August 3rd, 2009

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

Dining in Las Vegas 2009

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

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.

DEFCON notes: Day 1

August 2nd, 2009

I’ve been running a little behind on these, but I’m trying to catch up. I’m also going to try to insert links to the actual presentations as they go up.

Quick takes:

“Is your IPhone Pwned?”: This was turned into a more general talk about the whole class of smartphones, including Windows mobile devices. They demonstrated one exploit that involves settings on Windows devices from some vendors. (Basically, the exploit involves misconfigured security settings that allow a remote computer to send malicious WAP push messages that the phone will accept.) Patching mobile vulnerabilities is difficult; there’s a lot of QA issues that have to be dealt with by each vendor for each platform, plus the FCC gets involved if you touch the radio code. Beyond that, the presenters spent a lot of time discussing the design of their Fuzzit tool for finding phone vulnerabilities. Key takeaway: the state of mobile security today is roughly equivalent to the state of network security as of 1999.

“Hacking With the iPod Touch”: Key takeaways:

  • There’s a lot of tools available for penetration testing on the iPod Touch if you’re willing to jailbreak the device. (Wilhelm’s presentation includes a long list of available tools. Did you know that you can run Perl, Python, and Ruby on the iPod Touch? Neither did I.)
  • Nobody gets suspicious if they see you fiddling with your iPod Touch. A full-sized laptop, or even a netbook, might be a different matter.

“That Awesome Time I Was Sued For Two Billion Dollars”: Jason Scott is a pretty good speaker, but this was sort of a “meh” talk. “Yeah, I got sued for two billion dollars by someone who is apparently mentally unbalanced (in the speaker’s opinion -DB) and the case got thrown out of court.” Key take away: Don’t let yourself be intimidated by legal (or legal-looking) documents.

“Three Point Oh”: Couldn’t get in to see Long’s talk.

“Something About Network Security”: Kaminsky’s talk this year concentrated on vulnerabilities in the PKI infrastructure, and specifically certificate attacks. I still think Kaminsky is the cat’s pajamas, but his talk this year seemed a bit off, compared to some of his previous talks (for example, the tunneling data over DNS hack).

I heartily endorse this event or product.

August 1st, 2009

Pico, makers of fine FPGA development boards.

I haven’t actually worked with any of their products (though learning more about FPGAs is on my list of things I’d like to do) but the people they sent to DEFCON 17 were very nice. I even got two of their “business” cards.

IMG_0318

Someone’s getting one of these as a slightly late birthday present.

Hola, senior. We are the Federales; you know, the Mounted Police.

July 31st, 2009

IMG_0314

I only had to stand in line for about 20 minutes to get one. The latest batch was gone by noon; there were signs up at registration that they were not getting any more, and rumors later in the day that a fresh batch had come in.

Also, posting this gives me an excuse to link to one of my favorite sites, for those who haven’t seen it before.

Five. Five dollar. Five dollar slice.

July 31st, 2009

What is the greater cultural meaning of a New York pizza place charging $5 for a single slice of cheese pizza?

A small slice of heaven on Earth.

July 30th, 2009

Sometimes, life is nothing but “bad news and the pills that go with it” (to quote Achewood). And then, sometimes, something goes right.

Riesling

Num Tok

Woon Sen soup

Scallops with red curry

0-Day DEFCON Notes

July 30th, 2009

I like DEFCON. I like Dark Tangent personally. I like Joe Grand, the guy who has designed the DEFCON badges for the past few years.

But, guys, it looks really bad when, for the second year in a row, you run out of badges early on Thursday and have to issue temporary badges until more real ones get to the con Friday morning. You don’t even have the Olympics to blame this year. This is especially frustrating now that badge hacking is an official event/contest.

DEFCON talks I will not be attending:

“Hacking UFOlogy 102: The Implications of UFOs for Life, the Universe, and Everything.”

“Two years ago at Def Con 15, Richard [Thieme] presented Hacking UFOlogy. He supported his contention that (1) UFOs are real and (2) the data to support that statement is voluminous with numerous references and links…”

Hippie, please.

DEFCON talks I plan to attend:

“Is your iPhone Pwned”, Mahaffrey, Hering, and Lineberry. (This may be tough to get into, but it is scheduled against Dark Tangent’s intro and Joe Grand’s discussion of the badge, so we’ll see.)
“Hacking with the iPod Touch”, Willhelm
“That Awesome Time I Was Sued For Two Billion Dollars”, Scott
“Three Point Oh”, Long. (For the speaker’s reputation; I’ve heard Johnny Long speak before, and he’s someone I’d like to know better.)
“Something About Network Security”, Kaminsky. (Again, for the speaker’s reputation; Kaminsky is to TCP/IP what Musashi was to the sword.)
“Hacker vs. Disasters Large & Small”, RenderMan and Schearer
“Personal Survival Preparedness”, Dunker and Dunker
“Picking Electronic Locks Using TCP Sequence Prediction”, Lawshae
“Sniff Keystrokes With Lasers/Voltmeters”, Barisani and Bianco
“Bluetooth, Smells Like Chicken”, Spill, Ossmann, and Steward. (It looks like they’re going to talk about using software-defined radio to sniff Bluetooth, techniques for breaking the pseudo-random hopping sequence, and apparently some stuff that can be done with sub-$10 off-the-shelf hardware.)
“RAID Recovery: Recover Your PORN By Sight and Sound”, Moulton
“USB Attacks”, Vega
“Cracking 400,000 Passwords, Or How To Explain to Your Roomate why the Power Bill Is a Little High”, Weir and Aggarwal

I missed the panels on “Hacking With GNURadio” and “Hacking the Apple TV and Where your Forensic Data Lives”. Perhaps next year I need to arrive on Wednesday. If there is a next year.

Clippings

July 30th, 2009

I’m not exactly sure how to describe this *NYT* story; I would use the phrase “human interest”, but it’s actually about a revolver. Specifically, a vintage S&W .32 Hand Ejector that fell out of a perp’s waistband, went off, and hit a cop.

The revolver was traced to the Smith & Wesson plant in Springfield, Mass., according to law enforcement sources.

Oh, boy. That’s some fine police work there, tracing a Smith and Wesson revolver back to the Smith and Wesson plant.

But, when a .32-caliber revolver is fired, it keeps the casings inside its rotating chamber instead of spitting them out like a semiautomatic pistol, making it hard for forensic investigators to determine whether it had a criminal past.

Say what?

Like other guns seized by the police, it will be melted down and reincarnated as wire clothes hangers.

(insert cheap Mommie Dearest joke here)

(Above by way of the S&WCA mailing list.)

In other news, the legendary Reverend Ike has died.

Going Transmetropolitan FYI

July 30th, 2009

I’m in Las Vegas for DEFCON, so posting may or may not be light.

I may try to do some live (or semi-live) blogging from the convention, depending on how things go. I may end up just compiling notes and posting when I get back to the room at night. (For those who are not familiar with DEFCON, one of the things it is most famous for is having the most hostile network in existence.)

I wish Wikipedia had one throat, and I had my hands around it.

July 29th, 2009

By way of the *NYT*, we learn about the latest Wikipedia controversy:

“… a furious debate involving psychologists who are angry that the 10 original Rorschach plates are reproduced online, along with common responses for each. For them, the Wikipedia page is the equivalent of posting an answer sheet to next year’s SAT.”

http://www.nytimes.com/2009/07/29/technology/internet/29inkblot.html?_r=1&ref=todayspaper&pagewanted=all

Bonus: Mike Godwin content.

Efficient closest point calculation; how to?

July 28th, 2009

Randall Lawrence Waterhouse

Current meatspace coordinates, hot from the GPS receiver card in my laptp:

27 degrees, 14.95 minutes N lattitude 143 degrees, 17.44 minutes E longitude

Nearest geographical feature: the Bonin Islands

—Neal Stephenson, Cryptonomicon

One of the projects that I’ve had cooking in the back of my mind is to implement something like Waterhouse’s signature block in Cryptonomicon. After all, I’ve reached a point in my life where I actually have GPS equipment and a computer that are small enough to use on an airplane. (Unlike Waterhouse, I tend to fly coach.)

There’s a couple of different parts to this project as I see it.

  • You need an interface to the GPS reciever to get the current position data. That should be easy; both Perl and Python have GPSD interfaces.
  • You need a database of geographic points. It looks like that shouldn’t be a hard problem to solve; there’s some online databases that I think can be made to work, or converted, for this purpose.
  • You need an interface between your programming language and the database to look up points. Again, that should be easy; I’m assuming the database of geographic points is stored in some sort of standard SQL databse, and both Perl and Python have SQL database interfaces. (One possible problem is that I want to be able to run this on a Nokia N800, and the SQL database choices for that machine are kind of limited.)
  • You need to be able to calculate distance between two points. That’s easy: see http://www.movable-type.co.uk/scripts/latlong.html  for an example.
  • But here’s the problem. Let’s say you have a database of two million geographic points. How do you efficiently find the closest point to your current geographic location?

I’m stumped by the last part. Doing two million Haversine calculations seems like a time consuming operation; I suspect on a N800, the closest point would have changed substantially by the time the calculations finish.

Anyone have any good ideas? If I ever do write the script, I promise public acknowledgment (and public posting of the code).