Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Analysis of CRU Files Concludes They Were Leaked

MyFirstNameIsPaul (1552283) writes | more than 4 years ago

3

MyFirstNameIsPaul (1552283) writes "Through an analysis of the files themselves, and not their content, Lance Levsen concludes that the CRU files were leaked. Here is his conclusion:

"It is most likely that the FOI Officer at the University put it on an anonymous ftp server or that it resided on a shared folder that many people had access to and some curious individual looked at it.

If as some say, this was a targeted crack, then the cracker would have had to have back-doors and access to every machine at UEA and not just the CRU. It simply isn't reasonable for the FOI Officer to have kept the collection on a CRU system where CRU people had access, but rather used a UEA system.

Occam's razor concludes that "the simplest explanation or strategy tends to be the best one". The simplest explanation in this case is that someone at UEA found it and released it to the wild and the release of FOIA2009.zip wasn't because of some hacker, but because of a leak from UEA by a person with scruples."

The significance being that a leak indicates a worker unhappy with the integrity of the organization. Or someone who likes ot make big messes."
Link to Original Source

cancel ×

3 comments

Sorry! There are no comments related to the filter you selected.

Suspicious article; it was a hack, NOT leak! (-1, Troll)

Anonymous Coward | more than 4 years ago | (#30360204)

It is evident that those hacked e-mails do not change anything in the climate change science.
The 'nature' journal says so,
http://www.nature.com/nature/journal/v462/n7273/full/462545a.html [nature.com]
thus it does not make sense to have those e-mails 'leaked', because there is no reason to have them leaked.

That pseudo-analysis rings some bells.
If you notice the home page of http://www.smalldeadanimals.com/ [smalldeadanimals.com]
you will see a reference to http://2008.weblogawards.org/ [weblogawards.org]
and the image http://www.smalldeadanimals.com/pictures/2008winner.jpg [smalldeadanimals.com]
Those WeblogAwards are phoney awards that get attributed if enough people 'vote' for them.
Other popular denier websites received the same award, including
http://www.climateaudit.org/ [climateaudit.org]
http://wattsupwiththat.com/ [wattsupwiththat.com]

Climate change information resources (Youtube) (0)

Anonymous Coward | more than 4 years ago | (#30360272)

Here are some amazing videos that explain climate change and what is going on.

In a few decades from now we will look back in 2009 and how the deniers, ExxonMobil and the conservatives tried to fix the climate change conference in Copenhagen.

http://greenfyre.wordpress.com/denier-vs-skeptic/denier-myths-debunked/climate-denial-crock-of-the-week/ [wordpress.com]

To read the latest overview on climate change, see the special report, Copenhagen Diagnosis,
http://www.copenhagendiagnosis.com/ [copenhagendiagnosis.com]

Re:Climate change information resources (Youtube) (0)

Anonymous Coward | more than 4 years ago | (#30360422)

Just as Microsoft managed to buy out ISO for OOXML, the same is happening with Exxon Mobil and the Republicans with the Climate Change conference in Copenhagen.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>