Just another news site
Wir sind mitten in einem neuen atomaren Wettrüsten. Neun Atommächte (USA, Russland, China, England, Frankreich, Israel, Nordkorea, Indien und Pakistan) bedrohen sich gegenseitig und “modernisieren” ihre Atomarsenale.
Ist ein Szenario denkbar, in dem die Befunde sowohl des Omsker Krankenhauses als auch der Charité und sogar des Bundeswehrlabors korrekt sind? – Ein Versuch
Medienkritik zum Corona-Journalismus – Teil 1
Statistische Berechnungen von Wissenschaftlern geben uns nur wenige Jahrzehnte bis zur Apokalypse der Menschheit
“The Dark Man grows stronger every day. Soon he’ll destroy all who stand against him. “
James Marsden, Whoopi Goldberg and Alexander Skarsgård star in the new CBS All Access limited miniseries The Stand, based on the Stephen King novel of the same name.
It's Stephen King's world; we're just living in it. During New York Comic Con, CBS All Access dropped the first official trailer for its ten-episode limited miniseries of The Stand, an adaptation of King's sprawling 1978 post-apocalyptic fantasy novel about the aftermath of a deadly pandemic that wipes out most of the world's population.
(Some spoilers for the Stephen King novel below.)
The Stand is widely considered to be among King's best work, with a sprawling cast of characters and multiple storylines. It's also his longest, with the 1990 Complete and Uncut Edition surpassing even It in page count. King has said he wanted to write an epic dark fantasy akin to The Lord of the Rings, only with a contemporary American setting. "Instead of a hobbit, my hero was a Texan named Stu Redman, and instead of a Dark Lord, my villain was a ruthless drifter and supernatural madman named Randall Flagg," King wrote in his 1981 nonfiction book, Danse Macabre. "The land of Mordor ('where the shadows lie,' according to Tolkien) was played by Las Vegas."
Read 9 remaining paragraphs | Comments
Apple is set to announce its new iPhones next week. But according to a new report, the company will introduce its next MacBook a month later… and it’ll be the company’s first to feature an Apple-made processor based on ARM technology…
Apple is set to announce its new iPhones next week. But according to a new report, the company will introduce its next MacBook a month later… and it’ll be the company’s first to feature an Apple-made processor based on ARM technology. Meanwhile, gaming company Razer has unveiled an upgrade to its Razer Blade Stealth 13 […]
The post Lilbits: Razer’s Tiger Lake gaming laptop, Apple’s ARM MacBooks & Pine64’s open source communicator appeared first on Liliputing.
Last month there was excitement when the source code for Windows XP was leaked online. The big question, however, was how quickly Microsoft would act to have it disappeared from the web. The partial answer is that the company took 10 days to have one public repository taken down. And that was hosted on Github, a platform owned by Microsoft itself.
From: TF, for the latest news on copyright battles, piracy and more.
When Microsoft’s Windows XP launched in 2001, it was somewhat of a revelation.
Built on Windows NT and a clear step up from the consumer variants of Windows that preceded it, the OS reigned for years after being installed on millions of machines.
It’s currently estimated that around 0.8% of Windows PCs are still running Windows XP, despite Microsoft offering zero support for the relatively ancient OS. Nevertheless, there was mild euphoria among coders last month when it was confirmed that the source code for XP, among other things, had been leaked online, presumably to the dismay of Microsoft.
For the vast majority of interested onlookers, the leak probably meant very little in practical terms. With no support from Microsoft, running Windows XP is already a security gamble, regardless of any additional leaks.
However, when Microsoft confirmed it was actively investigating the leak, some presumed the company would act very quickly to have the code disappeared from the web. Quite when the upload to MEGA was taken down is unclear but it didn’t take long for the file to be removed following a complaint.
Torrents, of course, are much more complicated. While it is possible to have some torrent sites respond to takedown requests, sites such as The Pirate Bay will happily index pretty much anything – including the source code leak.
Predictably, the leaked content is available via the site today and not even the mighty Microsoft can do much about that. However, when checking the hash value in Google search and scouring the DMCA notice archive hosted by Lumen Database, there appears to have been little or even no effort to have links to the source code removed from Google or Twitter.
Granted, most of the sites mentioning the content have taken care not to link directly to the leaked source itself, with many preferring to post unclickable but entirely usable magnet links instead. Nevertheless, just days after the leak was reported, a very public repository of the code appeared much closer to home and nothing was done about that either.
On September 29, a handful of days after the leak reportedly appeared on 4chan, someone called ‘shaswata56’ thought it would be a good idea to post the source code for Windows XP on Github, for the world to see and download. The interesting thing here is that Github is owned by Microsoft, so the computing giant was effectively hosting its own leak.
Given the presumed sensitive nature of the source code, one might conclude that it would be spotted and deleted quickly. However, despite all the publicity, it took a full 10 days for Microsoft to do anything about it, at which point it had to serve its own company with a DMCA notice requesting that the code be taken down.
“I work in Microsoft Security Incident Response. The code in question is from a Windows XP source code leak,” the DMCA notice dated October 8 and filed with Github reads.
“The GitHub content is pulled directly form [sic] a torrent (that was also taken down),” it continues.
The notice originally contained a hash value for the source but that was censored by Github, presumably to stop any additional infringement. However, archive copies of the now-removed repository show that hash value in full, which can be easily converted to a torrent, one that is very much alive and being shared by many people.
Clearly, Microsoft’s claim that the torrent was somehow taken down was incorrect but that’s not a huge surprise since once a torrent is being spread, stopping people with access to magnet links or even a hash is incredibly difficult.
That being said, it would’ve been trivial to remove the source from Github on the day it was published. Instead, it took exactly 10 days, a lifetime where leaks are concerned and a little bit embarrassing when it’s your own site doing the distribution.
Quite why a rapid removal wasn’t executed isn’t clear but coupled with what appears to be a lack of enthusiasm to remove links still available via Google, it makes one wonder how concerned Microsoft is about the leak after all.
Or, just possibly, the company realizes just how futile it all is.
The DMCA notice is available here
From: TF, for the latest news on copyright battles, piracy and more.
Mit einer Politik der Angst werden Freiheitsrechte eingeschränkt, die Linke spielt bislang weitgehend mit
Es ist eine besondere Art der Vorratsdatenspeicherung: Google hilft US-Behörden umfangreich bei der Suche nach Verdächtigen. (Datenschutz, Smartphone)
Es ist eine besondere Art der Vorratsdatenspeicherung: Google hilft US-Behörden umfangreich bei der Suche nach Verdächtigen. (Datenschutz, Smartphone) Supply was down while demand was up, which is mathematically inconvenient.
Enlarge / August 14 and 15 saw a heatwave drive rolling blackouts. And then on August 16, a station in Death Valley hit 130°F... (credit: NASA EO)
In mid-August, just before dry lightning storms ignited a series of fires that would break records in California, an intense heatwave resulted in rolling blackouts on two consecutive days. The trouble came in the evening, when solar generation drops off, leading some to claim this was the consequence of relying on renewable electricity. But it’s not that simple, as the outages could have been avoided. A new “preliminary root cause analysis” report from two state commissions and the California Independent System Operator that runs the grid presents a clearer picture of what went wrong.
The rolling outages affected a few hundred thousand people starting around 6:30pm on both August 14 and 15. They were actually the result of the grid's rules: once the remaining reserve generation falls below six percent of current demand, the grid operator is required to institute rolling blackouts.
The report blames the need for outages on three things: extreme and widespread hot weather, a failure to update peak-demand forecasting practices as solar generation grows, and mistakes on the grid market that led to some plants exporting power when it was actually needed in-state.
Read 10 remaining paragraphs | Comments
You must be logged in to post a comment.