Hugh Pickens writes "The NY Times reports that German encryption expert Karsten Nohl says that he has deciphered and published the 21-year-old GSM algorithm, the secret code used to encrypt most of the world's digital mobile phone calls, in what he called an attempt to expose weaknesses in the security system used by about 3.5 billion of the 4.3 billion wireless connections across the globe. Others have cracked the A5/1 encryption technology used in GSM before, but their results have remained secret. 'This shows that existing GSM security is inadequate,' Nohl told about 600 people attending the Chaos Communication Congress. 'We are trying to push operators to adopt better security measures for mobile phone calls.' The GSM Association, the industry group based in London that devised the algorithm and represents wireless operators, called Mr. Nohl's efforts illegal and said they overstated the security threat to wireless calls. 'This is theoretically possible but practically unlikely,' says Claire Cranton, a GSM spokeswoman, noting that no one else had broken the code since its adoption. 'What he is doing would be illegal in Britain and the United States. To do this while supposedly being concerned about privacy is beyond me.' Simon Bransfield-Garth, the chief executive of Cellcrypt, says Nohl's efforts could put sophisticated mobile interception technology — limited to governments and intelligence agencies — within the reach of any reasonable well-funded criminal organization. 'This will reduce the time to break a GSM call from weeks to hours,' Bransfield-Garth says. 'We expect as this further develops it will be reduced to minutes.'"

Craig "Lazie" Lynch has been on the run from a U.K. prison since September. However, he continues to taunt police by updating his Facebook status. Now he is threatening to quit. From the article: "It seems, though, that late Sunday, Lynch began experiencing a little emotional pain. In what must have been an almost teary update, he posted: 'right I'm coming off this page as I have better things to do.' Who might have imagined that, in his mysterious hideaway, Lynch had something better to do than continue his run as a Facebook attraction?"

cowp writes "A Consumerist tipster couldn't get AT&T's website to sell him an iPhone when he shopped using an NYC ZIP code, but could when he tried other cities' ZIPs. Consumerist asked an AT&T CSR and seems to have gotten confirmation that this is carrier policy: 'Yes, this is correct the phone is not offered to you because New York is not ready for the iPhone. You don't have enough towers to handle the phone.' Considering Apple's gadget is currently the most popular handset in the US, its exclusive carrier's inability/unwillingness to support the device in the country's largest market is pretty huge news. If this proves true, I'd expect curtains for AT&T's exclusivity deal when it comes up for renewal." If you're in NYC, can you confirm or deny this outlandish-sounding claim? Updated 20091227 1:03 GMT by timothy: Headline, now corrected, inaccurately named Apple rather than AT&T. Mea culpa.

The Bears will be remembered as innovative rappers long after we've forgotten their footballing ways.

Noodlenose notes a thread up on the Ubuntu forums, where a user is questioning the practices of hardware manufacturer Foxconn. The user describes how his new Foxconn motherboard caused his Linux install to freeze and fire off weird kernel errors. He disassembles the BIOS and concludes that a faulty DSDT table is responsible for the errors. Even though the user makes Foxconn aware of the problem, they refuse to correct it, as 'it doesn't support Linux' and is only 'Microsoft certified.' The user speculates darkly on Foxconn's motives. Read the forum, read the code, and come to your own conclusions. "I disassembled my BIOS to have a look around, and while I won't post the results here, I'll tell you what I did find. They have several different tables, a group for Windows XP and Vista, a group for 2000, a group for NT, Me, 95, 98, etc. that just errors out, and one for LINUX. The one for Linux points to a badly written table that does not correspond to the board's ACPI implementation.' The worst part is Foxconn's insistence that the product is ACPI compliant because their tables passed to Windows work, and that Microsoft gave the the magic WHQL certification."