REVIEW: “The Quantum Thief”, Hannu Rajaniemi
“The Quantum Thief”, Hannu Rajaniemi, 2010, 978-1-4104-3970-3
%A Hannu Rajaniemi
%C 175 Fifth Avenue, New York, NY 10010
%G 978-1-4104-3970-3 0765367661
%I Tor Books/Tom Doherty Assoc.
%O firstname.lastname@example.org www.tor.com
%O Audience n Tech 1 Writing 2 (see revfaq.htm for explanation)
%P 466 p.
%T “The Quantum Thief”
This is the type of space opera that creates whole worlds, technologies, and languages behind it. The language or jargon makes it hard to read. The worlds are confusing, especially since some are real, and some aren’t. The technologies make it way too easy to pull huge numbers of deuses ex way too many machinas, which strain the ability to follow, or even care about, the plot. In this situation, the plot can be random, so the impetus for continued reading tends to rely on the reader’s sympathy for the characters. Unfortunately, in this work, the characters can also have real or imagined aspects, and can change radically after an event. It was hard to keep going.
Some of the jargon terms can be figured out fairly easily. An agora, as it was in Greece, is a public meeting place. Gogol wrote a book called “Dead Peasants,” so gogols are slaves. Gevulot is the Hebrew word for borders, and has to deal with agreed-upon privacy deals. But all of them have quirks, and a number of other terms come out of nowhere.
I was prompted to review this book since it was recommended as a piece of fiction that accurately represented some interesting aspects of information security. Having read it, I can agree that there are some cute descriptions of significant points. There is mention of a massive public/asymmetric key infrastructure (PKI) system. There is reference to the importance of social engineering in breaking technical protection. There is allusion to the increased fragility of overly complex systems. But these are mentions only. The asymmetric crypto system has no mention of a base algorithm, of course, but doesn’t even begin to describe the factors in the PKI itself.
If you know infosec you will recognize some of the mentions. If you don’t, you won’t learn them. (A specific reference to social engineering actually relates to an implementation fault.) Otherwise, you may or may not enjoy being baffled by the pseudo-creativity of the story.
copyright, Robert M. Slade 2012 BKQNTTHF.RVW 20120724