VUVUZELA for BlackBerry

The preferred noisemaker of the 2010 World Cup: the vuvuzela. For some reason these were distributed to fans attending World Cup matches, ruining the match for everyone watching at home.

When played by a stadium full of people the vuvuzela sounds like angry bees. I'm always up for a small project to help improve (or build) my BlackBerry development chops, and a vuvuzela app seemed like a perfect candidate. There are a slew of vuvuzela apps for the iPhone, but I only saw one other vuvuzela app for the BlackBerry, and that one only has a single vuvuzela sound.

Mine? It has 7.

I built the app with the 5.0 JDE. I tested it on a Storm2 9550 and Bold 9700 both running OS 5 and an 8820 running 4.5 and it worked on all three. If it doesn't work for some ancient OS, get a new phone.

Usage

Visit http://j.mp/cfg-vuvuzela using your BlackBerry to install the app. On newer devices the icon can be found in your Downloads folder.

Scroll and click a button to play the sound, or press the keys 1-7. You don't need to hold the ALT down; pressing W is the same as pressing 1. I haven't tested this on a SureType (Pearl) device.

Known Issues

  • Multiple audio threads – This is a J2ME limitation. I use javax.microedition.media.Player to play the audio, and you can only have one Player instance on CDMA devices and two on GSM. I read this on the BlackBerry support forums, and confirmed with a member of RIM's media development team.
  • Initial launch – the first time you launch the app on OS 5 it can take up to two minutes before the screen displays. Oddly enough it launches immediately on an old 8820 running OS 4.5. I'm looking into why this happens.
  • Volume control – I'm actually not sure where the volume setting comes from, I just play the sound and it works, and it's loud. The way the VUVUZELA should be.
  • The folks over at SistMan Software also have a vuvuzela app, and there is a conflict since both of our primary modules are named Vuvuzela (Vuvuzela.cod, etc). Until that's fixed, you can't have both apps installed. I like to think mine is better since it has more sounds, but they launched first and I'll publish a minor update with a unique module name.

Download

Download it OTA – Please link to this page, and not the .jad directly.

AT&T Downplays Critical ICCID Leak

Recently the email address and ICCID (SIM serial number) of at least 140,000 iPad 3G owners were left unprotected by AT&T. AT&T chose to blame "hackers" for stealing this information, but that is just deflection. AT&T didn't adequately protect customer information, and as a result someone found it.

AT&T also claims that it was only the email address and ICCID that leaked, which is another partial truth. A 2008 paper titled SIMs and Salsa (quick view) demonstrates how the ICCID is directly linked to the IMSI.

AT&T SIM cards have a 20-digit ICCID, and the IMSI is 15 digits long.

The iPad ICCIDs all seem to begin with 8901410424 and followed by 9 important digits and then a single checksum digit. For example 89014104240123456781.

An AT&T IMSI is 15 digits, made up with the MCC (310), MNC (170) and the 9 underlined digits preceding the checksum in the ICCID. So if your ICCID was 89014104240123456781 as in the example above, your IMSI would be 310170012345678.

You can find your ICCID on your iPad by opening Settings, choosing General and then About.

Why is the IMSI Important?

Each device has a unique IMSI, and the IMSI is considered sensitive enough that it's rarely sent over the wireless network. Even the name – International Mobile Subscriber Identity – implies that it is something that shouldn't be shared freely.

The IMSI is also one of two pieces of information needed to clone a SIM card, the other being the Ki, or subscriber authentication key. Fortunately the Ki can only be retrieved with physical access to the SIM card.

But, knowing who a specific IMSI belongs to, for instance someone at the White House, allows an attacker target a specific user. Using technology like an IMSI catcher an attacker can insert their own device between a target and the carrier network and monitor data or voice conversations. There are a number of flaws in GSM that I assume could also be exploited relatively easily by someone – like a foreign government – with the proper resources and motivation.

AT&T is downplaying their own incompetence at securing customer information, and is putting customers at risk. Customers who are newsworthy in their own right. Even if the information on the iPad isn't sensitive, it can easily be compromised and used as an attack vector onto a previously inaccessible corporate wifi network.

Perhaps AT&T feels that is not a real risk? The latest jailbreak is a userland jailbreak and it's not inconceivable that it could be adapted to work in Mobile Safari. The first iPhone was able to be jailbroken simply by visiting a special website. And Dave Aitel has been selling Silica since 2006. One of the use cases Aitel would pitch for Silica was to mail it to a CEO and let it automatically hack anything it could find, beginning with wifi networks.

AT&T needs to immediately and proactively issue all iPad 3G subscribers new SIM cards.

Things that are broken on search.twitter.com

Searching.

To be specific:

#1: Searching and expecting to find any results older than 5 days

#2: Searching for with an until date more than 7 days ago – this is an option on the Advanced Search page, and has returned a HTTP/404 for at least a year now

#3: Partial matches – I can find this post (for the next 4 days) by searching for Ozzy or fucking, but not fuck

#4: source containing anything with a space. I can search for source:Tweetie but not source:"Twitter for iPhone"

The site fails miserably at it's sole purpose – searching.

Never say Amazon doesn't hold a grudge

I was never a fan of Amazon's skitzophrenic pricing for the Kindle version of books, but I think Macmillan is utterly retarded for thinking that consumers will be be fine paying more for books, and that people will understand the difference between a hardcover and paperback price – of an electronic book.

Amazon was taking a loss on every $9.99 book they sold, because they wanted to further the ebook platform and not confuse people with variable pricing. Amazon is thinking long-term, whereas Macmillian is thinking like a 167-year old company that's run by people who are confused by and scared of the Internet.

If there is any doubt left about who has the reader's best interests in mind, try comparing pricing for a random book from Macmillan's Top Sellers page.

Eight Days to Live at Amazon

Eight Days to Live at Macmillan


© 2007-2012, Corey Gilmore | Posts RSS Feed | Comments RSS Feed | Contact

 

The views expressed on these pages are mine alone and not those of any past or present employer. All information presented on this site was obtained lawfully and not through disclosure under the terms of an NDA.