Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

+ - Analysis of CRU Files Concludes They Were Leaked-> 3

Submitted by MyFirstNameIsPaul
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

This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Analysis of CRU Files Concludes They Were Leaked

Comments Filter:

One can't proceed from the informal to the formal by formal means.

Working...