An anonymous reader writes "Right on the heels of Microsoft's adoption of the OpenID protocol by announcing their intention to enable OpenID authentication against all Live IDs, Google has announced their intention to join the growing list of OpenID authentication providers. Except it turns out they're using their own version of OpenID that is incompatible with everyone else. It seems that Google will be using their own 'improved' version of OpenID (based upon research and user feedback of the OpenID system) which isn't backwards compatible with OpenID 1.0/2.0, in hopes of improving end-user experience at the cost of protocol compatibility and complexity."

tjstork writes "Tesla Motors, the darling of technorati for its high performance electric car, may be about to go belly up. Venture capital is cut off, layoffs are under way, and construction plans are being stretched out. Elon Musk has ousted the CEO and taken the reins, blaming the global credit crunch."

David Gerard writes "Wikimedia, the organization that runs Wikipedia and associated sites, has moved its server infrastructure entirely to Ubuntu 8.04 from a hodge-podge of Ubuntu, Red Hat, and various Fedora versions. 400 servers were involved and the project has been going on for 2 years. (There's also a small amount of OpenSolaris on the backend. All open source!)"

jammag writes "According to Matt Hartley, many Linux desktop users don't like to admit that there's scads of closed source code commonly used with the Linux desktop. Hartley points to examples like proprietary drivers, the popularity of Skype among Linux users (in preference to the open source Ekiga), and the use of Wine. He concludes that, hey, if the code works, use it — a stance that won't sit well with purists. But his article raises the question: is it better to embrace some closed source fixes, and so create a larger user base, or to remain pure, and keep Linux for the specialists?"

tkrabec alerts us to a CERT advisory announcing a massive, multi-vendor DNS patch released today. Early this year, researcher Dan Kaminsky discovered a basic flaw in the DNS that could allow attackers easily to compromise any name server; it also affects clients. Kaminsky has been working in secret with a large group of vendors on a coordinated patch. Eighty-one vendors are listed in the CERT advisory (DOC). Here is the executive overview (PDF) to the CERT advisory — text reproduced at the link above. There's a podcast interview with Dan Kaminsky too. His site has a DNS checker tool on the top page. "The issue is extremely serious, and all name servers should be patched as soon as possible. Updates are also being released for a variety of other platforms since this is a problem with the DNS protocol itself, not a specific implementation. The good news is this is a really strange situation where the fix does not [immediately] reveal the vulnerability and reverse engineering isn't directly possible."