When a giant sperm whale rammed a whaling vessel in 1820, the deadly encounter inspired Herman Melville's classic novel, Moby Dick.

Melville's story, inspired by real-life man-versus-beast mayhem from the 1800s, made it to movie screens in the 1950s. Director John Huston's Moby Dick was evidence of Hollywood's growing fascination with giant, thrashing creatures.

Here are some of the best beasties ever captured on celluloid.

Left:

Captain Ahab (played by Gregory Peck) battles the great white whale in Moby Dick.

A giant squid battles Captain Nemo (played by James Mason) in Walt Disney's 1954 production, 20,000 Leagues Under the Sea.

Another great white terror of the deep surfaced in 1975's Jaws, directed by Steven Spielberg. The blockbuster scared beachgoers and spawned three sequels.

Not nearly as big as a whale, a giant squid or a great white shark, the Gill Man nevertheless emerged from murky waters to menace humans in 1954's Creature From the Black Lagoon, by director Jack Arnold.

In a battle of the box office titans, Godzilla battles King Kong in the 1962 Japanese film, Kingu Kongu tai Gojira. Only unlucky structures get between the behemoths in director Ishirô Honda's movie.

Bigger isn't always better. Suspense master Alfred Hitchcock turned seemingly innocuous seagulls into a giant, crowdsourced flying nightmare in 1963's The Birds.

A dinosaur foolishly liberated from the Forbidden Valley goes on a rampage in The Valley of Gwangi. Stop-motion animation great Ray Harryhausen created the creature for director Jim O'Connolly's 1969 flick.

Fussy intergalactic fat-ass Jabba the Hutt smokes out, Star Wars-style, in Return of the Jedi. The beast is known for his bad temper — and for keeping Princess Leia, dressed in her sexy slave girl outfit, on a chain.

Cuddly creatures turn into nightmarish beasts in 1984's Gremlins and again in 1990's sequel, Gremlins 2: The New Batch.

Creature-feature fans saw two classic extraterrestrials face off in 2004's AVP: Alien vs. Predator, by director Paul W.S. Anderson, and in Colin Strause's 2007 follow-up, AVPR: Aliens vs. Predator: Requiem.

A hideous beast from god knows where thrashes Manhattan in 2008's Cloverfield. Director Matt Reeves did a masterful job of unveiling the monster, one blurry bit at a time.

1820: The whaling ship Essex is rammed and sunk by a sperm whale 2,000 miles off the west coast of South America. The ordeal of the crew inspires Herman Melville's classic, Moby Dick.

The Essex was an aging vessel from Nantucket, which at the time possessed the largest whaling fleet in the world. The three-masted ship was 87 feet long and weighed 238 tons. She was captained by George Pollard Jr., at 28 already an experienced whaler.

By November 1820 the Essex had been at sea for over a year (three years out was not uncommon), surviving an early knockdown in an Atlantic squall and a rough passage around Cape Horn. Once the ship reached the fertile Pacific whaling grounds, however, things began looking up.

If the risks of whaling were many, the rewards could be great. Whale oil was prized as a lighting fuel. A successful voyage could make a captain wealthy, and meant a good payday for the crew as well. The Essex had taken its share of whales and on Nov. 20 appeared ready to take a few more when a pod was sighted off the starboard beam.

The ship's three remaining whaleboats — one had been destroyed by a whale's flukes during an earlier hunt — were dispatched for the kill. As the harpooning began, First Mate Owen Chase, commanding one of the whaleboats, looked back and saw a large sperm whale, which he estimated at 85 feet, approaching the Essex.

As he watched helplessly, the whale propelled itself into the ship with great force. Some crewmen on board were knocked off their feet by the collision, and Chase watched in disbelief as the whale drew back and rammed the ship again. This time the Essex was holed below the waterline, and doomed.

The crew organized what provisions they could and two days later abandoned ship aboard the three whaleboats. Twenty men left the Essex. Eight would ultimately survive the harrowing ordeal that played out over the next three months.

Fearing the "cannibalistic savages" of the South Seas islands (the irony of that reasoning will become apparent momentarily), Pollard decided to head for the more distant coastlines of Chile or Peru, first heading south to catch the expected favorable winds.

The winds, it turned out, weren't favorable at all, but Pollard was determined to reach South America. Eventually the three boats became separated from one another. One vanished and was never heard from again. The other two, one commanded by Pollard and the other by Chase, thrashed against the elements, and as the provisions dwindled and ran out, men began to die.

The first to go were given proper burials at sea, but as food ran out and the survivors on both boats became delirious from hunger, they turned to cannibalism. In Pollard's boat, straws were drawn to see who of the remaining four would be sacrificed so that the other three might survive. Pollard's young cousin, Owen Coffin, drew short straw. He was shot and eaten.

Only two men on that boat, Pollard and Charles Ramsdell, were alive when they were rescued by the whaling ship Dauphin after 95 days in an open boat. Chase and the survivors of his boat were picked up after 90 days. Three other men, who had chosen to remain on a small island shortly after the ordeal began, were also rescued.

What is known of the details of the ship's ill-fated voyage rests largely on Chase's memoir. He could offer no reason why the whale should attack the ship. But another young Nantucket whaleman, Herman Melville, drew his own conclusions. Moby Dick was a very, very smart whale.

Source: BBC

You might not have realized it, but the next great battle of cryptography began this month. It's not a political battle over export laws or key escrow or NSA eavesdropping, but an academic battle over who gets to be the creator of the next hash standard.

Hash functions are the most commonly used cryptographic primitive, and the most poorly understood. You can think of them as fingerprint functions: They take an arbitrary long data stream and return a fixed length, and effectively unique, string. The security comes from the fact that while it's easy to generate the fingerprint from a file, it's infeasible to go the other way and generate a file given a fingerprint.

Originally created to make digital signatures more efficient, hashes are now used to secure the very fundamentals of our information infrastructure: in password logins, secure web connections, encryption key management, virus and malware scanning, and almost every cryptographic protocol in current use. Without cryptographic hash functions, the internet would simply not work. At the same time, there isn't a good theory of hash functions. Unlike encryption algorithms, there are no secret keys involved; this makes it harder to mathematically define exactly what hash functions are.

The National Institute of Standards and Technology, NIST, is holding a competition to replace the SHA family of hash functions. "SHA" stands for "Secure Hash Algorithm." It was developed by the NSA in 1993 to replace the commercial MD4 and MD5 algorithms, and has been updated several times since then. All the SHA algorithms are very similar, and have been increasingly under attack, so NIST wants to replace them.

The competition is important because, unlike other technological standards, committee design — balancing the interests of diverse constituents — isn't conducive to good security. Security is best when it's designed by expert teams and then subjected to public review. And cryptography is best when it's chosen by competition.

In 1997, NIST held a competition for a block cipher to replace DES. Fifteen candidates and three-and-a-half years later, Rijndael became the new Advanced Encryption Standard — AES. NIST is doing the same thing for what it's calling SHA-3 (not, for some unexplained reason, the Advanced Hash Standard or AHS).

The deadline was October 31, and NIST received 64 submissions. This isn't surprising — I predicted 80 — as most of the 15 AES submitters were professors, whose students at the time have become professors themselves, with their own students. (If NIST does a stream cipher competition in another ten years, they should expect about 256 submissions.) These submissions came from academia, from industry, and from hobbyists. CIO magazine recently interviewed one of the submitters, who is 15. Twenty-eight submissions have been made public by the submitters, and six of those have been broken.

NIST is going through all the submissions right now, making sure they are complete and proper. Their goal is to publish all accepted submissions by the end of November, in advance of the First Hash Function Candidate Conference, to be held in Belgium right after the Fast Software Encryption workshop in February.

The group expects to quickly make a first cut of algorithms — hopefully to about a dozen — and give the community a year of cryptanalysis before making a second cut in 2010. After another year of cryptanalysis, NIST will choose a winner in 2011. Expect a final standard by 2012.

My advice for software developers is to let the process run its course. While it's tempting to use the new cool algorithms in your designs, it's far too soon to trust any of them. This process is likely to result in all sorts of new research results in hash function security, and some real cryptanalytic surprises. Give the community a few years to figure out which ones are good and which aren't.

I've previously called this sort of thing a cryptographic demolition derby: The last one left standing wins. But that's only partially true. Certainly all the groups will spend the next few years trying to cryptanalyze each other, but in the end there will be a bunch of unbroken algorithms. NIST will select one based on performance and features.

NIST has stated that the goal of this process is not to choose the best standard but to choose a good standard. I think that's smart; in this process, the best is the enemy of the good. While there's no rush to choose a new standard — the SHA-2 algorithms will remain secure for the foreseeable future — we don't want to analyze the candidates forever.

Personally, I was part of a group of eight cryptographers that submitted Skein to the competition. A decade ago, writing Twofish and participating in the AES process was the most fun I had ever had in cryptography. These next few years promise to be even more fun.

---

Bruce Schneier is chief security technology officer of BT. His new book is Schneier on Security.