Become a fan of Slashdot on Facebook


Forgot your password?

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).


+ - Google CENSORS Adrian Crenshaw. Operation-Irongeek fights back... #opirongeek 2

Submitted by richi
richi (74551) writes "Google massively raised the ire of the infosec community yesterday. Its utterly-reliable YouTube moderators nuked the account of the infamous Irongeek (Adrian Crenshaw). It surely couldn't have been a simple false-positive mistake, right? Because Google says it already "reviewed" the "repeated or severe violations" that led to the censorship.

So, that's all right then. No evil done here. Move along."

Why Improbable Things Really Aren't 166

Posted by Unknown Lamer
from the learn-to-count dept.
First time accepted submitter sixoh1 writes "Scientific American has an excellent summary of a new book 'The Improbabilty Principle: Why Coincidences, Miracles, and Rare Events Happen Every Day' by David J. Hand. The summary offers a quick way to relate statistical math (something that's really hard to intuit) to our daily experiences with unlikely events. The simple equations here make it easier to understand that improbable things really are not so improbable, which Hand call the 'Improbability Principle:' 'How can a huge number of opportunities occur without people realizing they are there? The law of combinations, a related strand of the Improbability Principle, points the way. It says: the number of combinations of interacting elements increases exponentially with the number of elements. The 'birthday problem' is a well-known example. Now if only we could harness this to make an infinite improbability drive!"

Comment: Re:More HDMI dongle devices coming (Score 2) 104

by Shemmie (#46145513) Attached to: Chromecast Now Open To Developers With the Google Cast SDK

I used Plex and Chromecast all over Christmas. It streamed very well indeed. It'd occasionally crash (as in the movie would stop playing suddenly), but it'd usually remember where the movie got to, and pick up where it left off - and I never needed to restart the media server.

All in all, very impressed with how Plex and Chromecast play together - mixture of file formats / quality were attempted, and all played at first time of asking.

As a by the by, I'm British, and got mine via the grey-market; if you're considering it, I can highly recommend it. All I need now is an UltraViolet player for Flixster, which will hopefully come with the SDK out, and my movie needs are completely sorted.

Comment: Jesus Christ (Score 5, Insightful) 224

by Shemmie (#45784459) Attached to: Snowden Gives Alternative Christmas Message On Channel 4

The majority of posts, on /. of all places, slamming Snowden for "blah blah blah, PR, narcissist, looking to make money off this."

This guy has effectively destroyed his own life, and the lives of those around him, to tell us, the plebs of the world, the truth that our Governments have been hiding from us.

And you're tearing a strip off him?

Comment: Re:I like the idea (Score 3, Informative) 292

by Shemmie (#44729979) Attached to: Lockbox Aims To NSA-Proof the Cloud

Another service offering:

SpiderOak uses AES256 in CFB mode and HMAC-SHA256. SpiderOak uses a nested series of key scopes: a new key for each folder, version of a file, and the individual data blocks that versions of files are composed from. Having keys with such limited scope allows for selective sharing of chosen portions of your data while keeping the remainder private.

        Most importantly, however, the keys are never stored plaintext on the SpiderOak server. They are encrypted with 256 bit AES, using a key created from your password by the key derivation/strengthening algorithm PBKDF2 (using sha256), with a minimum of 16384 rounds, and 32 bytes of random data ("salt"). This approach prevents brute force and pre-computation or database attacks against the key. This means that a user who knows her password can generate the outer level encryption key using PBKDF2 and the salt, then decipher the outer level keys, and be on the way to decrypting her data. Without knowledge of the password, however, the data is unreadable.

        SpiderOak accounts also include a 3072 bit public/private RSA key pair. This is currently not used for anything, but is included with all accounts with the expectation that SpiderOak will add multi-user private collaborative and sharing features which would necessitate the use of the the public/private keys. .

When you don't know what to do, walk fast and look worried.