After messing about with the examples for a while, I decided to see if I could whip something up from scratch. I had bookmarked Mark, K6HX’s entry about an Arduino based Morse Code Beacon and decided to take a crack at it. My code is a bit of a kludge, but it does work:

Now, to get this hooked up into a radio to make sure it can do more then blink an LED…

UPDATE: Uhhh… Yeah, so I guess Mark updated his beacon and did some pretty impressive stuff, making my implementation look like a Pinto while his is a Corvette. Oh well. It was a learning experience.

This aside, I find the story interesting for a number of reasons: First I like how the iPhone is specifically mentioned. Byron mentions that:

Hackers could go after sensitive information exchanged while using Web apps for phone banking and stock trading; or they could eavesdrop on sensitive conversations, discussion about medical histories, for instance.

Actually, in cases where you are on a 3G network, you’re safe from this attack on the data side, as 3G networks use the A5/3 cipher. The problem is that, at least in AT&Ts case, even if you are on a 3G network, any voice calls are routed over regular GSM channels, which use the faulty A5/1 cipher. I believe T-Mobile is in the same boat. Fixing this is rather simple from a technical standpoint, just flip the voice side over to 3G as well. Of course, we know that in real life it’s almost never that simple. Both carriers’ 3G network is nowhere near the size of their GSM networks, and who knows what kind of capacity they have on the 3G side. However, the decision here is completely on the carrier: What do they value more, their customers security and privacy or their profit margin?

Plus, I think the larger question here is when did mobile phones become secure? I think any person with a background in Information Security or Radio that was around in the early 1990s either monitored cell phones or knew of someone that did. While with the introduction of digital phones the monitoring became more difficult by your simple geek, given a sizable sum of money, it is still possible. The creation of devices such as Cryptophone proves this. Even before these tools were released, there are attacks on GSM in the wild which are “active” attacks, such as spoofing cell towers and then telling the phone to go sans encryption.

Next, regarding the question of releasing these tools; Byron calls the release taking the “morally debatable high ground.” I think his logic is really flawed, and he shows why in his article:

As this timeline depicting the emergence of the Conficker worm shows, the bad guys pay big bucks to black hat researchers adept at finding vulnerabilities, which can be immediately exploited for profit — before anyone issues a patch.

And now grey hat researchers,  like Moore and Nohl,  build careers out of concocting campaigns to embarrass vendors under the banner of compelling vendors to resolve security flaws in popular products – usually highly profitable cash cows — in a timely manner.

It’s been shown that attackers pay large sums of money for attacks that aren’t patched, making a market for enterprising attackers with questionable morals to develop them. With the existence of this market, why are we assuming that the bad guys don’t have rainbow tables for A5/1 already computed and are actively recording calls from high value targets? Cons It’s silly. Releasing these tools essentially destroys the already tattered blanket of ignorance people have been wrapping themselves up in since people started shouting that A5/1 was insecure and once again shows us that mobile phones are, by their very definition, insecure devices.

Goodbye Crash, Goodbye Burn. You have been faithful lab servers for the past two-plus years, but I must send you into that big beowulf cluster in the sky. I still remember when you were the only two servers we had, jammed full of VMWare images, utilities, and malware for analysis. But your age has finally caught up to you and your Pentium III processors and limited RAM are showing their age.

Good night you princes of the rack, you kings of the lab!

Hardware: B-, Sleek, great size, and a nice form factor. However, the device can feel rather flimsy at times. I am afraid that the device will fall with the keyboard open and my Pre will do some kind of morbid Oreo Twist to itself. Also, when shut, the device has some give where the two halves meet. In addition to this, Palm: MicroUSB port? Come on. Doesn’t every geek have a ton of accessories for Mini USB connectors? Are we seeing the connector conspiracy rear it’s ugly head again? Finally, the little gasket over the connector is annoying to get off, makes charging it annoying.

Battery Life: C+, I’m pleased how long it lasts, but considering my MDA could last about 2 days under fairly heavy use and how I can blow through about 1/5th my Pre battery in an hour under similar conditions? Not good. I think a car charger and a MicroUSB cable for USB charging are required accessories for any Pre user.

WebOS: A-, Wow. WebOS is nice. That’s not to say it has some very rough spots: Want to have one notification sound for an SMS message and another for an e-Mail? Tough noogies.  Navigate to a specific spot in a text field? We may be here for a while. However, all the rough spots can be buffed out in future updates. Overall, it’s zippy, the app store is filling up with goodies regularly, and the UI is great. Multitasking is awesome too, the lack of which is one of the things that turned me off about the iPhone. Overall, you can tell that WebOS is still a 1.X operating system, but with a little work by Palm it can easily take over the iPhone OS.

Network coverage: D, In a word: Bleh. THIS is the one drawback to the device: Sprint ‘Now” network. I think the “now” means that “You’ll be checking if you have coverage now.” I’ve heard mixed reports that it’s a Pre problem versus that it’s a Sprint problem, but I have seen it fluctuate between 1 and 5 bars in specific spots while staying stationary. I also seem to flip over to “roaming” (thankfully, free) at random spots, which means while I can still get voice, I can’t get a data connection. While T-Mobile was not without dead spots, I seemed to get better coverage with them. I’m hoping this is more of a problem with WebOS then Sprint as I can probably wait for Palm to work the kinks out of it’s transceiver rather then wait for Sprint to add additional cell sites.

Accessories: C, Come on, no holster? Just a stupid pouch? Geez. Also, the fact that the USB cable also doubles as the charging cable by plugging into the wall adapter? Lame. Palm, come on, give me two cables so I can keep one around in case I need to do an emergency charge off a USB port. It can’t be that expensive. As a side not, while I make no endorsement of it, the web store over at Treonauts seems to have lower prices for Pre accessories then Sprint.

Overall: B/B-, I am pleased and the Pre is a great device. I keep finding myself pleasantly surprised that it does something with ease that my old Windows Mobile device couldn’t (Like… say… delete e-mail messages from my mail server! Amazing!).  That’s not to say that there are some chinks in its armor, but I think it’s a worthy competitor to the iPhone. It’s still very much a 1st generation device and has the issues thereof, however if you’re looking for an iPhone alternative, I’d recommend giving the Pre more then a casual look.

I cracked open the clock and surveyed the circuit board:

We’re not interested in the IC in the upper right. That’s the FM receiver. What we’re interested in is the IC in the lower left:

Behold, the LM8560! From Howard’s e-mail I know that I was supposed to jump pin 15 to pin 28, however, I wanted to be doubly sure those numbers were correct . So, I found the LM8560 datasheet online and found the pinout (page 2). You can tell which way the chip is orientated by seeing which way the notch is pointing (on the left in the above picture). I also found out that Pin #28 is the 12/24 hour selection and pin #15 is “Vss”, which is IC-speak for “ground”. So, essentially, we’re grounding the 12/24 hour selection pin so it’s it makes the IC, and thus the clock, go into 24 hour mode. Should be easy right? Well, it would be if I were good at soldering, but after 15 minutes of abortive attempts I was finally successful.

Notice the scorch marks on the corners of the IC and cap right next to it! Hey, stop laughing! The soldering was made a touch easier by the fact that I could fit the wire into the little holes that the pins go down through. This made it slightly easier to solder together. After checking with my multimeter to make sure that the connection was good and that I didn’t accidentally solder another pin. I was pleasantly surprised and somewhat shocked when it told me that I only got the pins I was supposed to. So, I closed it up and plugged it in.

OK. No smoke. Now, let’s adjust the time…

Booyah! Success! Using parts I had around at home, I made a clock that was more-or-less useless to me into a clock that isn’t and also saved about $25 in the process! Huzzah!

This goes to prove that you too can do hardware hacking. After all, if I can, anyone should be able to…