Slashdot Mirror
Digital Fortress
The premise
The first page ("Prologue") is enough to draw you right in. A Japanese man in Seville, Spain, is dying, and in his last act he attempts to communicate with fellow tourists. We immediately wonder, What is he trying to say? How does this relate to the premise of the book?
Flipping the page literally flips across the Atlantic Ocean, to the National Security Agency (NSA) and to beautiful, intelligent Susan Fletcher, head cryptographer at the NSA. She is involved with a university language professor named David Becker--a man who will figure deeply into the story.
A mysterious phone call sends David to Spain and a phone call from Susan's boss, Commander Strathmore, brings her to NSA headquarters. It's there that she learns of a potentially fatal threat to the NSA's codebreaking supercomputer, TRANSLTR--an unbreakable encryption. Strathmore briefs her that a disgruntled former employee, Ensei Tankado, has threatened to release this encryption scheme to the highest bidder. If Tankado does so, the NSA will be crippled--a fact proven by the revelation that TRANSLTR normally spends minutes decoding a message, but has spent more than half a day trying to break Tankado's algorithm.
Tankado isn't stupid--Strathmore says he has an accomplice who will release the code in the event that something happens to Tankado. Unfortunately, Tankado is the Japanese man who has died in Seville...and thus the NSA is running out of time to locate Tankado's pass key to break the encryption before his accomplice can release it to the world.
Meanwhile, Becker is still in Spain, under orders--from Strathmore, it turns out--to do just that. He realizes that Tankado's ring is the "key" to the mystery, and thus he begins a frantic search that leads him from a French-Canadian writer in the clinic, to a fat German tourist and his red-haired "escort," to a punk rock bar on the outskirts of town. Did I mention he's being followed by a deaf assassin the whole time?
What I likedAs I mentioned, Digital Fortress has all the elements that I was looking for. It had just the right amount of main characters, and everyone had a proper place in the book and in the story. I'm appreciative of the tidbits of technical information here and there--mentions of PGP, NSA history, and other such morsels were well placed.
There was also a smattering of sexual energy (although no real "sex scenes") and humor here and there. Who said computer geeks can't have a good time?!
I'm also a fan of subplots in books, that magically mesh together near the climax. Dan Brown deserves praise in this regard: minor characters who initially make you question their presence are brought nicely into the fold and given purpose.
In any book like this, little puzzles and questions come up as a matter of course. The reader is challenged to solve them just as the characters are. In this book, there are many such puzzles: What does the inscription on the ring mean? Who is Tankado working with, and how? What is the pass-code for the encryption scheme? Why is David Becker being hunted down? I delighted in trying to come up with answers to these questions as I read the book, and was pleasantly surprised to see I was wrong in many respects.
What I didn't likeIn any mystery or thriller, the idea is to keep the reader guessing as long as possible, through plot twists, diverging plot lines that reconnect later, and the like. Brown does a fairly good job here, but this is where the book has its weakest points. For example, it is revealed early on that Tankado and the dead Japanese man in Spain are the same person. While this is perhaps unavoidable to push the plot along, I found it strange to have this happen so quickly. Later in the book, the author flips back and forth between who could be Tankado's accomplice, and who has committed a murder in Crypto. This flip-flopping is done poorly and leaves the reader thinking, "I already have my mind made up and you're not doing very well dangling red herrings." I had the bad guy pegged a couple of chapters before it was revealed, although I will admit that I was surprised at a particular turn of events afterwards.
Although this book was published in the late '90s, the technology aspects are still relevant--but this book gets some technical facts incorrect, or at least a bit off. However, they're fairly minor and don't detract from the book too much.
Some plot points are just too far fetched to be believable. For example, Susan's fiance, David Becker, tries to outrun a taxi--driven by the deaf assassin--while on a motorbike. The professional assassin fires several shots at Becker and misses every time, even though the bike is significantly slower than the taxi and the shots hit the bike body itself on several occasions.
Finally, some of the people in the NSA seem too stupid to be working there. In an effort to not give away spoilers, I can't be too much more specific than that, but suffice it to say that the "solution" is something that a high school science student wouldn't have much trouble figuring out.
Final thoughtsI tore into this book with high expectations. I finished the book with mixed feelings. As I look back on it, I can't help but feel that there was a lot of untapped potential and some glaring mistakes that could have been avoided. But I'm also pleased to have read what I consider a fairly good book, one that has served to heighten my interest in the genre, and made me even more ready to read The DaVinci Code.
Of course, it wouldn't be fair to compare this book to any of Dan Brown's later works. An author matures as he or she writes more books, and thus I'm certain that many of my quibbles would have been ironed out in future books. I'll have to find that out when I read DaVinci.
While it might seem that I had more bad to say about the book than good, I'd say that the reverse is actually true--the "good" goes all through the book, but there isn't really a way to quantify it.
I'd wholeheartedly recommend this novel to anyone who has an interest in technological thrillers, spy novels, or thrillers in general. It's a very accessible and enjoyable read, and I'm glad I bought it.
You can purchase Digital Fortress from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Now that's good fiction.
I read this book about a year ago, and i have to admit it was definitely addicting in the beginning, but after about the halfway point the auther i think tries to outsmart himself with too many plot twists and other such tricks to mislead the reader. Overall a good read, and i'd recommend it, but the newer books such as The Davinci Code are much cleaner and a better overall read. On the other hand the author, while making a few glaring errors, does a fairly decent job of dumbing down all the tech for the average reader to understand while still getting the gist correct, which is a nice change :)
drunk chemists
It was exactly what I was looking for
No it wasn't. You were looking for The DaVinci Code. Remember now?
Helpin' out,
Letter
Digital Fortress was a very fast read. Much like The Da Vinci Code, it's a well-paced, by-the-books thriller that fans of the genre will find entertaining. But, the technical mistakes are so glaringly bad, that I just spent most of the book being annoyed. I thought a book with cryptography as a plot point would be interesting and maybe even challenging, but there's nothing about cryptography anywhere. There's only a giant brute-force-and-ignorance hammer, no real problem solving. It really surprised me how off he was with some of the plot points and technical aspects since TDVC was so well researched. If you liked TDVC, skip DF
got biv?
Doesn't sound like the author really understands cryptography or cryptology. It's the people that do the important work of breaking a code, not the uber machine that just automates the process once the system's been broken.
TZ
I was dissapointed by The Da Vinci Code which I read last year. Brown is pretty much a hack writer and seems to be more interested in a whiz-bang plot than developing anything deeper or more interesting. His characters are flat and don't really develop - the hero of Da Vinci Code is Indiana Jones without the bravery. The research behind the book seems very much like a bunch of vaguely-related conspiracy theories that the author read about and decided to write a pot-boiler around.
For a much more interesting book that uses similar material to go a lot further, try Umberto Eco's Foucault's Pendulum. Eco uses the background of holy grail consipracists to weave a tale rich in detailed historical research, amusing characters and that is layered with meaning. You get the what-is-going-to-happen plot and structural and metaphorical complexity. I suspect that Brown may have read Foucault's Pendulum before he wrote Da Vinci Code, because some of the similarities are noticeable.
Summary: Da Vinci Code is a fun enough airport novel. I enjoyed reading it but in the end didn't feel I'd gained anything for having read it.
Sailing over the event horizon
He realizes that Tankado's ring is the "key" to the mystery,
NSA Chief: Aha! The ring is mine! Now our supercomputer with the clever acronym can decode this vitally important document! (hands document to flunky) What does it say?
NSA Underling: (Turns ring and presses buttons on blinkenlights panel.) It says..."Be sure to drink your Ovaltine."
NSA Chief: Ovaltine? A crummy commercial? Son-of-a-bitch! Here, try it again! (hands new document to flunky.)
NSA Underling: (repeats procedure) It says..."All your base-"
NSA Chief: (pulls gun from holster and shoots his underling.)
NSA Underling: AIEEEEEE! (Underling expires.)
NSA Chief: (Shakes fist to heavens.) Curse you, fat German tourist and his red-haired "escort"!!! Cuuurrrse yoooouuu!!!!
Yes, the book is based on a pivotal plot point that is ludicrous. The plot revolves around a new encryption scheme that will render the NSA's super-secret weapon (a brute force crack machine that will decrypt anything within minutes) useless. The source code to this new encryption algorithm has been posted to the Internet and downloaded by crypto types worldwide. The catch -- it's encrypted with itself. The book is about the race for the key that can decrypt the algorithm so the source is accessible and can be used to create truly unbreakable encryption.
Well, the cryptography head comes up with a plan (repeatedly called "brilliant" in the book) to get the key first, modify the source to include a back-door so the NSA can read everything while the public thinks the code is unbreakable, re-encrypt the modified source and replace the version that's been posted to the web. Then they leak the key and the whole world starts using "Digital Fortress".
Does Brown really think that you can replace a file on the web that's been downloaded by thousands and that all the downloaded copies will be updated as well? He seems to -- he only explores the possibility that Tankado might have reviewed the code and found the changes, and quickly dismisses it. He doesn't even consider that most of the people would decrypt the version they already have, let alone consider that someone might compare the source between the version currently available and the one downloaded before the key was released.
The modifications to the source would be posted to Slashdot within 5 minutes of the key being released. But Brown believes no one would ever catch on, and this master plan drives the entire novel. It's utter drivel.
I totally agree - after reading DaVinci Code and Digital Fortress, I can pretty much sum up Dan Brown's formula as the following:
:(
- Start off with an interesting hook and quickly diverge into two (or more) concurrent plots. Minimal character development is necessary.
- Devote alternating chapters to each plot
- End each (short) chapter with a 'cliffhanger' style situation. This gives the 'page-turner' feel because there's always some unresolved situation that haunts you during reading.
- Don't worry about factual accuracy. Better yet, ignore accuracy altogether if it hampers the plot.
- Make the two concurrent plots collide during the last chapter or two of the book and tidy up the situation entirely too neatly.
It's not that either of the books is a bad read - I've read much worse... it's just the formulaic predictability that makes me want to stay away from anything else he might churn out