Ghost in the Wires: My Adventures As the World's Most Wanted Hacker (Anglais) CD – Livre audio, 15 août 2011
|Neuf à partir de||Occasion à partir de|
Les clients ayant consulté cet article ont également regardé
Descriptions du produit
Revue de presse
Présentation de l'éditeur
Driven by a powerful urge to accomplish the impossible, Mitnick bypassed security systems and blazed into major organizations including Motorola, Sun Microsystems, and Pacific Bell. But as the FBI's net began to tighten, Kevin went on the run, engaging in an increasingly sophisticated cat and mouse game that led through false identities, a host of cities, plenty of close shaves, and an ultimate showdown with the Feds, who would stop at nothing to bring him down.
Ghost in the Wires is a thrilling true story of intrigue, suspense, and unbelievable escape, and a portrait of a visionary whose creativity, skills, and persistence forced the authorities to rethink the way they pursued him, inspiring ripples that brought permanent changes in the way people and companies protect their most sensitive information. --Ce texte fait référence à une édition épuisée ou non disponible de ce titre.
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Détails sur le produit
En savoir plus sur les auteursDécouvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Commentaires en ligne
Meilleurs commentaires des clients
Si vous n'êtes pas technophile ou informaticien de formation, ce livre est quand même accessible : les auteurs ont pris soin d'expliquer simplement certains termes ou de simplifier certains détails, sans que cela en enlève au charme des histoires. Du coup, même si votre anglais (en particulier l'anglais technique lié aux télécommunications) est un peu rouillé, c'est un ouvrage accessible, et vous pourrez profiter d'une histoire de chasse à l'homme tout bonnement surprenante !
Cette simplification peut s'avérer frustrante dans le dernier tiers ou quart du livre pour les technophiles, si comme moi vous espériez de nombreux détails sur certains évènements. Le livre est complété par quelques photos en son milieu, qui sont assez jolies dans l'ensemble.
L'histoire est plutot sympa même si l'auteur fait preuve d'un égocentrisme insupportable : "tout petit déjà, j'étais plus intelligent que la moyenne"...
Côté livraison / prix / état du livre, vous pouvez y aller les yeux fermés !
Commentaires client les plus utiles sur Amazon.com (beta)
Ghost in the Wires doesn't reach the level of audacity of Catch Me if You Can - impersonating technicians over the phone doesn't rise to the sheer nerve of a teenager impersonating an airline pilot or a doctor, as Abagnale did, and getting away with it. But Ghost in the Wires goes well beyond the adolescent bragfest of phone hacks that it could have been.
I think this is largely due to the co-writer, William L. Simon. Kevin Mitnick describes in his acknowledgments, how he and Simon argued over how detailed and technical the book should be, and apparently Simon prevailed. There's enough detail to explain how the scams were possible, but not so specific as to send the non-programmer into a hexadecimal stupor.
Another big plus is that many of the hacks depended as much on what Mitnick calls "social engineering" as on specialist knowledge. Unlike the stereotypical computer nerd, Mitnick was as comfortable and proficient at schmoozing people as he was writing code - he could talk his way into places that were restricted and convince people he was entitled to classified information. These were scams anyone can understand.
Mitnick also succeeds at not crossing the line from confident to insufferable, which is another pitfall of true crime tell-alls. Perhaps we can once again thank William Simon for this achievement.
I expected to skim this 400-page book but ended up reading every word. Mitnick was unbelievably audacious, and he says he never profited from his exploits. Knowing the risks (especially after he had already spent an unpleasant stretch in jail), how could he continue to risk getting caught again? He claims he was addicted to hacking, and while that seemed to me a sorry excuse for criminal behavior, it started to seem like the only possible explanation.
Whatever Mitnick's reasons, Ghost in the Wires is as much fun to read as any summer thriller.
I can't help but enjoy reading about someone who has the adept social engineering of a film noir gumshoe, or the undercover detective, who applied it growing up and getting into trouble. Like Kevin, I knew The Three Days of the Condor. I learned it was a favorite of his, and I clung to this fact which fell through the sieve of newspaper myth. Free Kevin!
Now read Kevin's story, where you'll find enough detail to keep any heart racing. Whether or not you have enough awareness for some of the bits, or rely on the plain language, the story can strike sheer terror in the hearts of those who don't know much of anything about bits and bytes. For those who do, this book contains updated method nomenclature and references to security protocol that it's valuable from that perspective.
Kevin possesses the kind of curiosity to dig and uncover gems of hidden info for esoteric purposes in order to unlock a power only a successful hacker knows about. Social engineering is akin to the confidence game, but different all the same when it involves computer networks. The best hackers are never caught, never known about. Kevin has a different distinction: The first and the grandest adventure story, ever.
You don't need to be a hacker or security professional to appreciate and learn from it. Today, security is serious business and hackers typically have bad or misguided intent. Kevin's motivation was harmless fun at the expense of a system, and honest curiosity which was not rewarded with a government security detail. Fear prevailed then, as hacking was an unknown phenomenon. An innocent motive seemed totally suspect in a court setting.
One frequent result of being a trail blazer is its potential costs. When playing around with the law, this can end in time set aside from society. The NYTimes columnist ironically exercised his own opportunistic free market exploit to establish a mythology around Kevin that ruined any chance for freedom. Kevin emerged from lock down to write the correction that I hold in my hands. The highest adventure possible for any security professional.
I will leave whatever social sickness the brilliant Kevin Mitnick has to the mental health professionals, but suffice it to say that his writing in Ghost in the Wires is a terrific nonfiction example of an "unreliable narrator." Throughout the book, Mitnick does the same things over and over again and is surprised when he repeatedly gets caught. He hurts his mother, grandmother, wife, and friends over and over again with his illegal hacking activities, says he regrets doing it each time, but then turns around and does it to them again. Mitnick is upset when he is blamed for things he "didn't do" and when he is "double crossed," but he freely admits to dozens of other computer break ins and instances where he compromises the trust of others using "social engineering" techniques, ridicules them for trusting him, and then betrays that trust. Mitnick says he never took money from hacking, but now of course he's making money from writing this and other books as well as from promoting his computer security company based on his (illegally obtained) skills. Mitnick is all over the place.
In one scene Mitnick is severely critical of prosecutors who use "dirty tactics" to put him behind bars, but then he continues to use his own dirty tactics while behind those bars. For instance, Mitnick is contemptuous of being put in solitary confinement so he can't "phone freak" (a form or hacking using an ordinary telephone), but then uses his severely limited (and monitored) prison pay phone time to phone freak anyway by dialing behind his back as a guard watches, apparently just for the thrill of it and with complete disregard for any consequences.
Even after he is apprehended multiple times, Mitnick still doesn't "get it." He is condescending to and openly critical of the FBI, local law enforcement, and the media throughout the book for their lax procedures, but still doesn't seem to understand why breaking and entering highly sensitive computer systems is wrong and dangerous. When they find his stolen database of thousands of credit card numbers, he doesn't understand why he should be prosecuted for possessing them because he didn't actually use them to steal money. "That would be wrong," he says. Another instance: he spends most of the book using cloned cell phones to make "free" calls all over the world, which are billed to unaware random consumers. This form of theft, as well as repeated breaking and entering, both electronically and physically, seems to be viewed as no problem.
While on the run Mitnick takes great pains to steal and set up new identities in Las Vegas, Denver, Seattle, and Raleigh NC, but each time he goes back to his old hacking and cell phone tricks only to get discovered again and again. In one scene he finally figures out that he is being tracked electronically by the authorities when he uses his cell phone, and is actually being followed by a helicopter that zeroes in on him every time he makes a call. Does he then stop making cell calls? No. Does he stop hacking? No. Even when he is suspicious of being compromised on the phone, he still keeps calling and talking "for hours" to the informant, and yet feels betrayed when they turn over what they have to the authorities.
Mitnick seems to blame everyone but himself most of the time for having the unmitigated gall to trust him through his so called "Social Engineering," which he both repeatedly relies on and harshly criticizes his marks for falling for. He even blames others who actually create the computer systems he feels compelled to compromise. It is much more difficult to create than it is to tear down, and instead of compromising these networks for "trophies," one is left wondering what the incredibly talented Mitnick could have done if he had spent as much time and energy building systems instead of breaking into and stealing information from them.
Mitnick's behavior is deeply disturbing. He writes, "It always seems strange to me that my captors had such trouble grasping the deep satisfaction that could be derived from a game of skill....what it was worth didn't matter to me. So what was the nature of my crime, that I allegedly had access?" It is not a game, and Mitnick completely misses the point, even now, after serving years in prison and being released. Mitnick is obsessive about his own privacy, and yet is utterly indignant about others' attention to and expectation of theirs? It just doesn't wash.
For people outside of security this is a great introduction for anyone who is worried about how hackers commonly steal information and break into systems. The book will never leave you with eyes glazed over in getting down to the really techie details. A lot of people have views of hackers that they see from the movies which is really crazy nerds with crazy monitors who can break into anything in minutes (think swordfish). This is far from the case with real attacks often taking months to years. The book really does a good job at making users understand that they are the most critical asset when it comes to securing their organizations data as well as their own. The crazy software products are important, but in the end it comes down to the users and what they will do.
I managed to briefly meet Kevin Mitnick at Derbycon (a security conference) this year and he was nice enough to sign my book which is really a nice added bonus!