oztiks writes with this excerpt from The H: "A vulnerability in the 32-bit compatibility mode of the current Linux kernel (and previous versions) for 64-bit systems can be exploited to escalate privileges. For instance, attackers can break into a system and exploit a hole in the web server to get complete root (also known as superuser) rights or permissions for a victim's system. According to a report, the problem occurs because the 32-bit call emulation layer does not check whether the call is truly in the Syscall table. Ben Hawkes, who discovered the problem, says the vulnerability can be exploited to execute arbitrary code with kernel rights. ... Hawkes says the vulnerability was discovered and remedied back in 2007, but at some point in 2008 kernel developers apparently removed the patch, reintroducing the vulnerability. The older exploit apparently only needed slight modifications to work with the new hole."

vlangber writes "Joel Spolsky wrote a famous blog post back in 2000 called 'Things You Should Never Do, Part I,' where he wrote the following: '[T]he single worst strategic mistake that any software company can make: They decided to rewrite the code from scratch.' Here is a story about a software company that decided to rewrite their application from scratch, and their experiences from that process."

lucidkoan writes "MIT researchers recently unveiled the world's first thin-film solar cell printed on a sheet of paper. The panel was created using a process similar to that of an inkjet printer, producing semiconductor-coated paper imbued with carbon-based dyes that give the cells an efficiency of 1.5 to 2 percent. That's not incredibly efficient, but the convenience factor makes up for it. And in the future, researchers hope that the same process used in the paper solar cells could be used to print cells on metal foil or even plastic. If they're able to gear efficiencies up to scale, the development could revolutionize the production and installation of solar panels."

stronghawk writes "The creator of the Nickel-O-Matic is back at it and has now built a Turing Machine from a Parallax Propeller chip-based controller, motors, a dry-erase marker and a non-infinite supply of shiny 35mm leader film. From his FAQ: 'While thinking about Turing machines I found that no one had ever actually built one, at least not one that looked like Turing's original concept (if someone does know of one, please let me know). There have been a few other physical Turing machines like the Logo of Doom, but none were immediately recognizable as Turing machines. As I am always looking for a new challenge, I set out to build what you see here.'"

An anonymous reader passes along this quote from a report at 24/7 Wall St.: "There have been over 3 billion downloads since the inception of the App Store. Assuming the proportion of those that are paid apps falls in the middle of the Bernstein estimate, 17% or 510 million of these were paid applications. Based on our review of current information, paid applications have a piracy rate of around 75%. That supports the figure that for every paid download, there have been 3 pirated downloads. That puts the number of pirate downloads at 1.53 billion. If the average price of a paid application is $3, that is $4.59 billion dollars in losses split between Apple and the application developers. That is, of course, assuming that all of those pirates would have made purchases had the application not been available to them for free. This is almost certainly not the case. A fair estimate of the proportion of people who would have used the App Store if they did not use pirated applications is about 10%. This estimate yields about $459 million in lost revenue for Apple and application developers." A response posted at Mashable takes issue with some of the figures, particularly the 75% piracy rate. While such rates have been seen with game apps, it's unclear whether non-game apps suffer the same fate.

Nate Anderson pens a fine historical retrospective for Ars Technica: a look at 100 years of Big Content's fearmongering, in their own words. There was John Philip Sousa in 1906 warning that recording technology would destroy the US pastime of gathering around the piano to sing music ("What of the national throat? Will it not weaken? What of the national chest? Will it not shrink?"). There was the photocopier after World War II. There was the VCR in the 1970s, which a movie lobbyist predicted would result in tidal waves, avalanches, and bleeding and hemorrhaging by the music business. He compared the VCR to the Boston Strangler — in this scenario the US public was a woman home alone. Then home taping of music, digital audio tape, MP3 players, and Napster, each of which was predicted to lay waste to entire industries; and so on up to date with DVRs, HD radio, and HDTV. Anderson concludes with a quote from copyright expert William Patry in his book Moral Panics and the Copyright Wars: "I cannot think of a single significant innovation in either the creation or distribution of works of authorship that owes its origins to the copyright industries."

jamie points out that Perl 5.11.0 was released yesterday, as well as a schedule for future 5.11.x releases, planned for the 20th of every month. Jesse Vincent encouraged testing of the new (development) version, saying, "If you write software in Perl, it is particularly important that you test your software against development releases. While we strive to maintain source compatibility with prior releases wherever possible, it is always possible that a well-intentioned change can have unexpected consequences. If you spot a change in a development release which breaks your code, it's much more likely that we will be able to fix it before the next stable release. If you only test your code against stable releases of Perl, it may not be possible to undo a backwards-incompatible change which breaks your code."

gpronger writes "Sticks and Stones May Break My Bones, but Glass Will Certainly Mend Them! The old schoolyard ditty may be changed to reflect developments using metallic glass that will dissolve in situ instead of the traditional stainless steel or titanium hardware, which require removal by surgery once the bone has healed. Physics World reports that researcher Jörg Löffler at ETH Zurich has created an alloy of 60% magnesium, 35% zinc, and 5% calcium, molded in the form of metallic glass. Through rapid cooling, the alloy forms a molecularly amorphous glass that slowly dissolves over time, supporting the injury long enough for healing, then slowly dissolving away."

I Don't Believe in Imaginary Property writes "Red Hat has filed a friend of the court brief with the Supreme Court in regards to the In Re Bilski case, which has become incredibly important due to the possibility that it could redefine the scope of patentable subject matter in a way that affects software patents. In the brief, Red Hat argues that software should not be considered patentable subject matter because it causes economic harm due to patents being granted with vague subject matter, which makes it impossible to say that a given piece of software doesn't arguably infringe upon someone's patent. They also point out Knuth's famous quote that you can't differentiate between 'numeric' and 'non-numeric' algorithms, because numbers are no different from other kinds of precise information." Read below for the submitter's thoughts on an earlier amicus brief filed in the Bilski case by Professor Lee Hollaar.

I Don't Believe in Imaginary Property writes "After the permanent injunction barring Microsoft from selling Microsoft Word, many armchair lawyers and pundits wondered how the ruling would affect OpenOffice. The company with the patent, i4i, believes that OpenOffice does not infringe upon it. But lest anyone think that therefore ODF will win out over OOXML, keep in mind that Microsoft has its own broad XML document patent, which issued just two weeks ago, having been filed in December 2004, and they're telling the Supreme Court to apply the Bilski ruling narrowly, so that it doesn't invalidate patents like theirs (and i4i's). After all, unlike most companies and individuals, Microsoft can afford $290 million infringement fines. Then again, given that Microsoft's new patent has only two independent claims (claim #1 and claim #12), and both of those claims 'comprise' something using an 'XML file format for documents associated with an application having a rich set of features,' maybe they wouldn't be that hard to work around if you just make sure any otherwise infringing format is only associated with an application lacking in the feature richness department."

Hugh Pickens writes "The NY Times reports that the Army began encouraging its personnel — from the privates to the generals — to go online and collaboratively rewrite seven of the field manuals that give instructions on all aspects of Army life, using the same software behind Wikipedia. The goal, say the officers behind the effort, is to tap more experience and advice from battle-tested soldiers rather than relying on the specialists within the Army's array of colleges and research centers, who have traditionally written the manuals. 'For a couple hundred years, the Army has been writing doctrine in a particular way, and for a couple months, we have been doing it online in this wiki,' said Col. Charles J. Burnett, the director of the Army's Battle Command Knowledge System. 'The only ones who could write doctrine were the select few. Now, imagine the challenge in accepting that anybody can go on the wiki and make a change — that is a big challenge, culturally.' Under the three-month pilot program, the current version of each guide can be edited by anyone around the world who has been issued an ID card that allows access to the Army Internet system. Reaction so far from the rank and file has been tepid, but the brass is optimistic; even in an open-source world, soldiers still know how to take an order."

Dave Knott writes "Entertainment Weekly reports that Universal Pictures has confirmed rumours of a Battlestar Galactica feature film. Directed by Bryan Singer, and co-produced by original series creator Glen Larson, the new movie will not be related to the recently concluded SyFy Network series. Rather, it will be a 'complete re-imagining of the sci-fi lore that was invented by Larson back in the '70s.'"

Hugh Pickens writes "In a few weeks, tens of thousands of creative people will make their yearly pilgrimage to Nevada's Black Rock desert for Burning Man, an annual art event and temporary community celebrating radical self expression, self-reliance, creativity and freedom, but EFF reports that the event's Terms and Conditions include 'a remarkable bit of legal sleight-of-hand.' As soon as 'any third party displays or disseminates' your photos or videos in a manner that the Burning Man Organization (BMO) doesn't like, those photos or videos become the property of the BMO. BMO's Terms and Conditions also limits your own rights to use your own photos and videos on any public websites obliging you to take down any photos to which BMO objects, for any reason; and forbidding you from allowing anyone else to reuse your photos. This 'we automatically own all your stuff' magic appears to be creative lawyering intended to allow the BMO to use the streamlined 'notice and takedown' process enshrined in the Digital Millennium Copyright Act (DMCA) to quickly remove photos from the Internet giving BMO the power of fast and easy online censorship. 'Burning Man strives to celebrate our individuality, creativity and free spirit,' writes Corynne McSherry. 'Unfortunately, the fine print on the tickets doesn't live up to that aspiration.'"