What do you think?
Rate this book
Ghost in the Wires: My Adventures as the World's Most Wanted Hacker
If they were a hall of fame or shame for computer hackers, a Kevin Mitnick plaque would be mounted the near the entrance. While other nerds were fumbling with password possibilities, this adept break-artist was penetrating the digital secrets of Sun Microsystems, Digital Equipment Corporation, Nokia, Motorola, Pacific Bell, and other mammoth enterprises. His Ghost in the Wires memoir paints an action portrait of a plucky loner motivated by a passion for trickery, not material game. (P.S. Mitnick's capers have already been the subject of two books and a movie. This first-person account is the most comprehensive to date.)
413 pages, Hardcover
First published August 15, 2011
About the author
Kevin D. Mitnick
11 books924 followersKevin David Mitnick, the world's most famous (former) computer hacker, had been the subject of countless news and magazine articles, the idol of thousands of would-be hackers, and a one-time "most wanted" criminal of cyberspace, on the run from the bewildered Feds. A security consultant, he had spoken to audiences at conventions around the world, been on dozens of major national TV and radio shows, and even testified in front of Congress. He was the author of The Art of Deception and The Art of Intrusion.
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 30 of 1,943 reviews
December 1, 2020
Ghost in the Wires: My Adventures as the World's Most Wanted Hacker
by Kevin D. Mitnick
Kevin Mitnick is not really a hacker. He’s more of a nerdy scam artist with a massive ego. Many other reviewers have described this book better than I can. They believe Kevin Mitnick is a sociopath and I agree. He is extremely proud of his “social-engineering” skills (his ability to lie to people convincingly).
All of his scams are fairly similar.
1. Mitnick calls an administrative office of a corporation, pretending to be an employee: “Hi Mr/Mrs________, I’m _______ from the _______ department….”
2. While on the phone, pretending to be a co-worker, he sweet talks a well meaning but naïve employee into giving him access codes, passwords, restricted phone numbers, etc… This is how he gains entry into their restricted system.
3. Once inside the system Mitnick often steals the identity of one or more employees in order to gain further access, while probably ruining several people’s careers in the process.
4. With the exception of his mom and grandmother (enablers who bail him out repeatedly) he expresses no remorse for his actions. He is convinced that what he does is completely harmless. In fact, he sees himself as the victim. He even blames his victims for being gullible enough to believe his lies.
5. When he is finally caught it is always because some trusted friend has betrayed and backstabbed him. (Notice: all of his friends are fraudulent con-men, just like him)
6. When the courts punish him, he blames the legal system for ruining his life by saddling him a criminal record, which makes it impossible for him to gain employment at companies where a high security clearances are needed.
7. Return to the beginning. Repeat cycle.
With the exception of a few amusing stories about his exploits as a teenager where he hacked the drive-through intercom of a McDonald’s drive-through and playing pranks on friends by screwing with their telephone numbers, the book is very repetitive. Save yourself a lot of time and just Google Kevin Mitnick’s name and you can get a cliff note version of his hacking escapades.
by Kevin D. Mitnick
Kevin Mitnick is not really a hacker. He’s more of a nerdy scam artist with a massive ego. Many other reviewers have described this book better than I can. They believe Kevin Mitnick is a sociopath and I agree. He is extremely proud of his “social-engineering” skills (his ability to lie to people convincingly).
All of his scams are fairly similar.
1. Mitnick calls an administrative office of a corporation, pretending to be an employee: “Hi Mr/Mrs________, I’m _______ from the _______ department….”
2. While on the phone, pretending to be a co-worker, he sweet talks a well meaning but naïve employee into giving him access codes, passwords, restricted phone numbers, etc… This is how he gains entry into their restricted system.
3. Once inside the system Mitnick often steals the identity of one or more employees in order to gain further access, while probably ruining several people’s careers in the process.
4. With the exception of his mom and grandmother (enablers who bail him out repeatedly) he expresses no remorse for his actions. He is convinced that what he does is completely harmless. In fact, he sees himself as the victim. He even blames his victims for being gullible enough to believe his lies.
5. When he is finally caught it is always because some trusted friend has betrayed and backstabbed him. (Notice: all of his friends are fraudulent con-men, just like him)
6. When the courts punish him, he blames the legal system for ruining his life by saddling him a criminal record, which makes it impossible for him to gain employment at companies where a high security clearances are needed.
7. Return to the beginning. Repeat cycle.
With the exception of a few amusing stories about his exploits as a teenager where he hacked the drive-through intercom of a McDonald’s drive-through and playing pranks on friends by screwing with their telephone numbers, the book is very repetitive. Save yourself a lot of time and just Google Kevin Mitnick’s name and you can get a cliff note version of his hacking escapades.
December 27, 2013
I had to read this book for school (Cybercriminology), and opted to listen to it so I could get some school work done while commuting and going about my daily life. I just wanted to smack the guy. All these tales of his exploits with periodic expressions of contrition that rang hollow for me (boo hoo, I'm so sad that I stressed out my mom and gram), and a lot of instances of the pot calling the kettle black (I don't get guys who have to brag about their sexual exploits. Next sentence...I'm sooooo smart.). He is clearly impressed with himself and wants the reader to be too, but then paints himself as this naif at times who is falling prey to untrustworthy and disloyal "friends"...um, ok...you're a grifter. Plain and simple. Yes, the man is talented, but he also an addict...He is smart, but he is a con-man. I had a hard time seeing him as a protagonist.
That said, a lot of the book is him re-hashing variations on a theme..."oh, there was this impenetrable system, and I got into it...just to see if I could. Hooray...next..." Watch the video of him being interviewed on The Colbert Report...it's the cliff notes, and save yourself the time and money of reading this book.
That said, a lot of the book is him re-hashing variations on a theme..."oh, there was this impenetrable system, and I got into it...just to see if I could. Hooray...next..." Watch the video of him being interviewed on The Colbert Report...it's the cliff notes, and save yourself the time and money of reading this book.
September 7, 2023
I’ve always wondered why hackers hack. Is it for the kick it gives them or for personal gain, or perhaps a combination of the two? For this reason I was attracted to this memoir of Kevin Mitnick, someone I’d never heard of but a man who became the most wanted hacker of his time, chased for years until his eventual capture by the FBI.
Mitnick was born in Van Nuys, California in 1963 and by the age of twelve he was already developing the art of ‘social engineering’ (or manipulation of individuals) to obtain information or get tasks completed. To supplement this, he also practiced ‘dumpster diving’ (searching bins for useful discarded items or information). In an early example of how these activities helped him, he talked a bus driver into providing him with some information and then sought out a supply of discarded but unused tickets in order to obtain free bus travel throughout the Los Angeles area. By the time he was in high school he had become an amateur radio operator and his fascination with the communications network started to take a hold on him.
Very soon his spare time was almost totally taken up with his exploration of the telephony infrastructure. He would use his skills to obtain passwords that would give him entry into seemingly secure systems and then compare notes and achievements with fellow hackers. It seems that Mitnick just loved the challenge of breaking into company systems and enjoyed the intellectual stimulus of gaining knowledge through his pastime. He and his cohort looked upon the capture of proprietary software as trophies and would seek out spare disk space in company systems to store their captures. Other than the satisfaction of achievement, the gaining of knowledge and the resulting increase in his ability to break into even more systems it seems that Mitnick really didn’t gain anything from these actions. He would sometimes capture huge hauls of credit card information but there is no evidence to suggest he ever did anything to exploit this.
As time passed he did occasionally get caught out and when this happened he’d lose his job and he even served some time in lock-up for his deeds. But he was addicted and he’d soon returned to hacking. He began to target bigger companies and harder to penetrate systems. By this time he was known to authorities and started using cloned cellular phones to hide his identity. In the end he was forced to go on the run, relocating around the country and changing his identity whenever he moved on, until he the FBI finally caught up with him in 1995. He was to spend 5 years in prison before his eventual release. And then, in a nice turn of events, he discovered he was in demand as an expert in the field of cyber security and developed a career as a speaker on security issues and consultant to technology companies – a case of poacher turned gamekeeper.
I loved the element of the chaser and they chased here, it’s an exciting tale and Mitnick shows himself to be resourceful in avoiding the chasing pack and demonstrates an appealing sense of humour along the way. For me the downside to this account is simply the amount of technical detail provided on precisely how he managed to access given systems. Long lists of code are recited as numerous similar events are walked through. This may be of interest to those who relish the fine technical detail but it was way over my head and proved to be a little tiresome.
Overall, it’s an enthralling tale of addiction overriding common sense but with something approaching a happy ending. And though I could have done without some of the fine detail it did add a sense of authenticity to events and certainly didn’t override the sense of tension and anticipation of ultimate disaster that runs throughout this account. Definitely recommended for anyone seeking an insight into this hidden world.
Mitnick was born in Van Nuys, California in 1963 and by the age of twelve he was already developing the art of ‘social engineering’ (or manipulation of individuals) to obtain information or get tasks completed. To supplement this, he also practiced ‘dumpster diving’ (searching bins for useful discarded items or information). In an early example of how these activities helped him, he talked a bus driver into providing him with some information and then sought out a supply of discarded but unused tickets in order to obtain free bus travel throughout the Los Angeles area. By the time he was in high school he had become an amateur radio operator and his fascination with the communications network started to take a hold on him.
Very soon his spare time was almost totally taken up with his exploration of the telephony infrastructure. He would use his skills to obtain passwords that would give him entry into seemingly secure systems and then compare notes and achievements with fellow hackers. It seems that Mitnick just loved the challenge of breaking into company systems and enjoyed the intellectual stimulus of gaining knowledge through his pastime. He and his cohort looked upon the capture of proprietary software as trophies and would seek out spare disk space in company systems to store their captures. Other than the satisfaction of achievement, the gaining of knowledge and the resulting increase in his ability to break into even more systems it seems that Mitnick really didn’t gain anything from these actions. He would sometimes capture huge hauls of credit card information but there is no evidence to suggest he ever did anything to exploit this.
As time passed he did occasionally get caught out and when this happened he’d lose his job and he even served some time in lock-up for his deeds. But he was addicted and he’d soon returned to hacking. He began to target bigger companies and harder to penetrate systems. By this time he was known to authorities and started using cloned cellular phones to hide his identity. In the end he was forced to go on the run, relocating around the country and changing his identity whenever he moved on, until he the FBI finally caught up with him in 1995. He was to spend 5 years in prison before his eventual release. And then, in a nice turn of events, he discovered he was in demand as an expert in the field of cyber security and developed a career as a speaker on security issues and consultant to technology companies – a case of poacher turned gamekeeper.
I loved the element of the chaser and they chased here, it’s an exciting tale and Mitnick shows himself to be resourceful in avoiding the chasing pack and demonstrates an appealing sense of humour along the way. For me the downside to this account is simply the amount of technical detail provided on precisely how he managed to access given systems. Long lists of code are recited as numerous similar events are walked through. This may be of interest to those who relish the fine technical detail but it was way over my head and proved to be a little tiresome.
Overall, it’s an enthralling tale of addiction overriding common sense but with something approaching a happy ending. And though I could have done without some of the fine detail it did add a sense of authenticity to events and certainly didn’t override the sense of tension and anticipation of ultimate disaster that runs throughout this account. Definitely recommended for anyone seeking an insight into this hidden world.
December 10, 2012
The bad: Mitnick's ego and lingering resentments sometimes get in the way and the story also gets dry and repetitive at points.
The good: Mitnick's story is legendary, and while I get the feeling he isn't always 100% honest, this is probably the closest we'll ever get to the true story without embellishments and ridiculous rumors. As Mitnick points out several times in his own story, his escapades are remarkable enough without the crazy rumors that grew around his legend over the years.
As a hacker and penetration tester myself, it is refreshing to read a story where second or third-hand accounts of hacking don't result in eye-rolling ridiculousness during the technical parts. I had known bits and pieces of Mitnick's story, but it was interesting to find out that most of his greatest successes were due, at least in part, to his natural skill as a social engineer. The result is a book that is not only entertaining and historic, but highly instructional also. As he states, the approaches he uses to get access to systems works nearly as well today as it did in the day of his exploits.
The good: Mitnick's story is legendary, and while I get the feeling he isn't always 100% honest, this is probably the closest we'll ever get to the true story without embellishments and ridiculous rumors. As Mitnick points out several times in his own story, his escapades are remarkable enough without the crazy rumors that grew around his legend over the years.
As a hacker and penetration tester myself, it is refreshing to read a story where second or third-hand accounts of hacking don't result in eye-rolling ridiculousness during the technical parts. I had known bits and pieces of Mitnick's story, but it was interesting to find out that most of his greatest successes were due, at least in part, to his natural skill as a social engineer. The result is a book that is not only entertaining and historic, but highly instructional also. As he states, the approaches he uses to get access to systems works nearly as well today as it did in the day of his exploits.
April 23, 2012
This unbelievably wild and crazy book describing the "adventures of the world's most wanted hacker" was captivating from start to finish.
Granted, I am a "technologically-inclined" sort of person, but this book appears to have been written to appeal to both "techies" and "non-techies" alike. Techies will appreciate the relative simplicity of the incredible hacks that Mitnick managed to pull off, while non-techies will gape in astonishment at the achievements and audacity that these hacks involved—and are also given quick, but understandable explanations of technical jargon whenever necessary (which is actually not often, as this isn't a technical manual).
No matter who you are, you will walk away from this book marveling at the extent of Mitnick's escapades (to give just one example: the way he was surveilling the FBI the entire time they were trying to surveil him!). This is the electronic equivalent of Frank Abagnale's story in Catch Me If You Can, and every bit as outrageous and entertaining.
I couldn't put this book down from beginning to end, and I highly recommend it to anyone looking for a thrilling non-fictional ride.
Granted, I am a "technologically-inclined" sort of person, but this book appears to have been written to appeal to both "techies" and "non-techies" alike. Techies will appreciate the relative simplicity of the incredible hacks that Mitnick managed to pull off, while non-techies will gape in astonishment at the achievements and audacity that these hacks involved—and are also given quick, but understandable explanations of technical jargon whenever necessary (which is actually not often, as this isn't a technical manual).
No matter who you are, you will walk away from this book marveling at the extent of Mitnick's escapades (to give just one example: the way he was surveilling the FBI the entire time they were trying to surveil him!). This is the electronic equivalent of Frank Abagnale's story in Catch Me If You Can, and every bit as outrageous and entertaining.
I couldn't put this book down from beginning to end, and I highly recommend it to anyone looking for a thrilling non-fictional ride.
July 16, 2013
I got to read this book as part of a buddy read group where we pick different genres and types of books to get us out of our comfort zone. I started with quite a lot of expectations for this book and i'd have to say overall, I was a little disappointed. Probably 2.5 stars. Reminded me a lot of Wolf of Wall St and Catch me if you can. Better than the first, but not up to the latter.
The subject matter was something I was looking forward to getting into, imagining a book of hacking adventure and intrigue, like the movie Hacker or swordfish, but it actually is an unfortunate series of events in hacking into the phone company systems.
The good:
I loved the social engineering side of this. Mitnick was brilliant at this and really shows how you can pretty much get anything you want out of people by being friendly, confident and clued up on the lingo.
The story behind the FBI was interesting, as they struggled to keep up with this new white collar crime they knew nothing about.
The bad:
Receptiveness, Mitnick is trying to recall things that happened twenty years ago and it seems he used a very similar Modus Operandi on each hacking job. But that meant as a reader, we got to read the same thing over and over again, with a change to his social engineering calls and the phone numbers he now had access to.
His attitude drove me nuts, dude, you're a hacker, you broke in and stole stuff. You broke into premises and stole from peoples desks, you stole dead babies identities, you racked up thousands of dollars of phone bills on half the population of Denver. You can't spend 500 pages trying to pull off the "it was all in a bit of fun, who did I rally hurt eh? Oh the FBI is hunting me like a dod, do I deserve this". I think in writing this book he really tried to down play what he did and that is disappointing considering what he then went on to do after being freed from prison. I didn't expect him to denounce hacking and try to warn you off doing it, but I also did not expect him to try and get sympathy for his plight.
I think this is summed up well when one of the phone companies who he stole the source code from for their new mobile system claimed he cost them $60million in damages (they had no idea what he was doing with their source code, who he was selling it too etc). Mitnick claims that was the equivalent of stealing a can of coke and having the company sue you for stealing the recipe. Now that is blinkered thinking.
Overall, I am glad I read it. I ended up really enjoying the hunt for his capture and how he was moving and trying to stay ahead. I feel like I learnt something from reading this book and enjoyed being out of my comfort zone. Since that was the object of the read, it was a success.
Would I recommend this? Yeah, to a phone phreaker, if I knew one.
The subject matter was something I was looking forward to getting into, imagining a book of hacking adventure and intrigue, like the movie Hacker or swordfish, but it actually is an unfortunate series of events in hacking into the phone company systems.
The good:
I loved the social engineering side of this. Mitnick was brilliant at this and really shows how you can pretty much get anything you want out of people by being friendly, confident and clued up on the lingo.
The story behind the FBI was interesting, as they struggled to keep up with this new white collar crime they knew nothing about.
The bad:
Receptiveness, Mitnick is trying to recall things that happened twenty years ago and it seems he used a very similar Modus Operandi on each hacking job. But that meant as a reader, we got to read the same thing over and over again, with a change to his social engineering calls and the phone numbers he now had access to.
His attitude drove me nuts, dude, you're a hacker, you broke in and stole stuff. You broke into premises and stole from peoples desks, you stole dead babies identities, you racked up thousands of dollars of phone bills on half the population of Denver. You can't spend 500 pages trying to pull off the "it was all in a bit of fun, who did I rally hurt eh? Oh the FBI is hunting me like a dod, do I deserve this". I think in writing this book he really tried to down play what he did and that is disappointing considering what he then went on to do after being freed from prison. I didn't expect him to denounce hacking and try to warn you off doing it, but I also did not expect him to try and get sympathy for his plight.
I think this is summed up well when one of the phone companies who he stole the source code from for their new mobile system claimed he cost them $60million in damages (they had no idea what he was doing with their source code, who he was selling it too etc). Mitnick claims that was the equivalent of stealing a can of coke and having the company sue you for stealing the recipe. Now that is blinkered thinking.
Overall, I am glad I read it. I ended up really enjoying the hunt for his capture and how he was moving and trying to stay ahead. I feel like I learnt something from reading this book and enjoyed being out of my comfort zone. Since that was the object of the read, it was a success.
Would I recommend this? Yeah, to a phone phreaker, if I knew one.
December 27, 2012
I know that many people love Ghost in the Wires, but this book really bothers me. It's very difficult to be sympathetic towards Kevin Mitnick, who continually prevails upon his readers to let him have it both ways.
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.
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.
April 4, 2016
The least of my complaints is that this guy, for all his alleged genius qualities, isn't a good writer. Which wouldn't bother me that much, except his "adventures" weren't that exciting.
I further felt mislead because the prologue was an incredibly interesting two-man B&E into a corporation that he was paid to infiltrate as a security consultant. Once the actual novel started, there wasn't another paragraph nearly as interesting as the prologue. More specifically, most of his hacking was phone "phreaking," where he cons the phone company into giving him free long distance in various ways. Which, in an era where I can make free video calls to other continents with Skype, is simply not compelling literature.
The way Mitnick got access to almost every single system he hacked was by conning a person into giving him access directly or information that would then get him access. We get it, the human element is the weakest in every computer system. This became incredibly repetitive very quickly. And I get the feeling that the repetitive nature of this novel is in part because it is filled with a number of lies by omission, as well as revisionist history to paint him in a better light -- if not outright blatant lies. e.g. I never did anything with the information I hacked, it was all solely for "fun."
Mitnick is quick to point out how he was betrayed by all his hacker friends, without taking any responsibility for himself or his actions -- which were, obviously, illegal, meaning any time he got caught, he deserved what he got. He was also a horrible son, grandson, boyfriend and husband, and again, doesn't take a lot of responsibility for how his actions affected the people that loved him while he kept hacking despite warnings from the police, FBI, and myriad companies that had been made aware of his exploits. On that note, the book jacket called him "elusive," except that by 1/4 of the way through this book, he had been caught multiple times, spending time in both juvie and adult prisons. Elusive? You keep using that word, I do not think it means what you think it means.
I could probably go on, but I think my opinion of this book and its author are pretty clear. The biggest mystery to me is how he got the legendary Steve Wozniak to write the foreword for him -- maybe he held Woz's long-distance service hostage from him?
I further felt mislead because the prologue was an incredibly interesting two-man B&E into a corporation that he was paid to infiltrate as a security consultant. Once the actual novel started, there wasn't another paragraph nearly as interesting as the prologue. More specifically, most of his hacking was phone "phreaking," where he cons the phone company into giving him free long distance in various ways. Which, in an era where I can make free video calls to other continents with Skype, is simply not compelling literature.
The way Mitnick got access to almost every single system he hacked was by conning a person into giving him access directly or information that would then get him access. We get it, the human element is the weakest in every computer system. This became incredibly repetitive very quickly. And I get the feeling that the repetitive nature of this novel is in part because it is filled with a number of lies by omission, as well as revisionist history to paint him in a better light -- if not outright blatant lies. e.g. I never did anything with the information I hacked, it was all solely for "fun."
Mitnick is quick to point out how he was betrayed by all his hacker friends, without taking any responsibility for himself or his actions -- which were, obviously, illegal, meaning any time he got caught, he deserved what he got. He was also a horrible son, grandson, boyfriend and husband, and again, doesn't take a lot of responsibility for how his actions affected the people that loved him while he kept hacking despite warnings from the police, FBI, and myriad companies that had been made aware of his exploits. On that note, the book jacket called him "elusive," except that by 1/4 of the way through this book, he had been caught multiple times, spending time in both juvie and adult prisons. Elusive? You keep using that word, I do not think it means what you think it means.
I could probably go on, but I think my opinion of this book and its author are pretty clear. The biggest mystery to me is how he got the legendary Steve Wozniak to write the foreword for him -- maybe he held Woz's long-distance service hostage from him?
December 14, 2016
From Professor Schmecker's Pop-up Book of Modern Irregular Conjugations Reflecting the Problems of Modern Society:
I hack, You betray, He accelerates the collapse of society.
which about sums up Ghost in the Wires.
A big shout-out, props, and whatever else the cool kids are saying nowadays when they want to show respect to William L. Simon, Mitnick's “co-author”. Mitnick shows no evidence of ever having read a book for the sheer joy of it, nor even writing a letter or a note on a refrigerator without the intention of deceiving someone. He seems complete uninterested in and unmotivated by concepts like beauty, devotion, faith, or justice, except to the extent that any of these ideas can help Mitnick to gain the confidence of others for his personal amusement or to leave prison earlier.
I believe that the lack of these qualities renders him incapable of writing a book this interesting, so the book's success is due to Simon. He makes Mitnick jump off the page, warts and all, investing him with a perverse vigor and vitality. Only people dedicated to the same ethos as Mitnick, i.e., every self-interested act I take is justified because it is a blow against “the man”, will find him remotely sympathetic. But you really want to see how he gets away with the next hack, the next escape, the next confidence-gaming of some poor sap whose only fault is the impulse to be kind to strangers. In short, a good read.
This book is probably safe to publish now because the social engineering scams of Mitnick and his ilk have caused such a great reduction in the level of trust in the world. The elementary-level trickstering describe herein no longer routinely take people in save for the hopelessly dopey, who will always be with us. So, like a magician whose tricks are now common knowledge, Mitnick takes what pride he can in fact that he was the first to think up mean ways to trick people.
Many people here and elsewhere have remarked on the unintentional hilarity which is caused when Mitnick takes information he gains by betraying the trust of others and then shares it with like-minded individuals who – can you guess? -- betray him. Mitnick is outraged! He clearly felt that he and other hackers were an elite brotherhood who had the right to exploit the rest of us poor saps but, being brothers-at-arms, not each other. But then he found out that there was no honor amongst thieves, a thing he could have probably have learned at much smaller cost to himself if he had read some books.
I have heard that there is a certain amount of debate as to what should be the correct dictionary definition of “hacker”. Should it be “person who likes to tinker with technology” or “person who accesses information without permission”? I propose a third definition: “person who with intentional malice fails to understand game theory since it conflicts with his/her sense of entitlement”. Specifically, game theory has shown fairly conclusively that, when people trust and cooperate with each other, the outcomes are overall better for everyone involved. If we lived in a society like that, everyday life might be less of a headache, with less two-step authentication and obligatory changing of passwords. Like life being a headache? Thank a hacker! Shake his hand, if you can find a moment when he'll stop using it to pat himself on the back.
I hack, You betray, He accelerates the collapse of society.
which about sums up Ghost in the Wires.
A big shout-out, props, and whatever else the cool kids are saying nowadays when they want to show respect to William L. Simon, Mitnick's “co-author”. Mitnick shows no evidence of ever having read a book for the sheer joy of it, nor even writing a letter or a note on a refrigerator without the intention of deceiving someone. He seems complete uninterested in and unmotivated by concepts like beauty, devotion, faith, or justice, except to the extent that any of these ideas can help Mitnick to gain the confidence of others for his personal amusement or to leave prison earlier.
I believe that the lack of these qualities renders him incapable of writing a book this interesting, so the book's success is due to Simon. He makes Mitnick jump off the page, warts and all, investing him with a perverse vigor and vitality. Only people dedicated to the same ethos as Mitnick, i.e., every self-interested act I take is justified because it is a blow against “the man”, will find him remotely sympathetic. But you really want to see how he gets away with the next hack, the next escape, the next confidence-gaming of some poor sap whose only fault is the impulse to be kind to strangers. In short, a good read.
This book is probably safe to publish now because the social engineering scams of Mitnick and his ilk have caused such a great reduction in the level of trust in the world. The elementary-level trickstering describe herein no longer routinely take people in save for the hopelessly dopey, who will always be with us. So, like a magician whose tricks are now common knowledge, Mitnick takes what pride he can in fact that he was the first to think up mean ways to trick people.
Many people here and elsewhere have remarked on the unintentional hilarity which is caused when Mitnick takes information he gains by betraying the trust of others and then shares it with like-minded individuals who – can you guess? -- betray him. Mitnick is outraged! He clearly felt that he and other hackers were an elite brotherhood who had the right to exploit the rest of us poor saps but, being brothers-at-arms, not each other. But then he found out that there was no honor amongst thieves, a thing he could have probably have learned at much smaller cost to himself if he had read some books.
I have heard that there is a certain amount of debate as to what should be the correct dictionary definition of “hacker”. Should it be “person who likes to tinker with technology” or “person who accesses information without permission”? I propose a third definition: “person who with intentional malice fails to understand game theory since it conflicts with his/her sense of entitlement”. Specifically, game theory has shown fairly conclusively that, when people trust and cooperate with each other, the outcomes are overall better for everyone involved. If we lived in a society like that, everyday life might be less of a headache, with less two-step authentication and obligatory changing of passwords. Like life being a headache? Thank a hacker! Shake his hand, if you can find a moment when he'll stop using it to pat himself on the back.
November 1, 2013
For most people, computers are magic. Which is to say, they are technology sufficiently advanced to the point of mystification. I include myself in this camp, for despite my comfort with computers and my fluency in programming, a great deal of mystery still surrounds them. With the emergence of the Internet into the public sphere and the rise of the Web, computers and the phone system are now fundamentally intertwined, and vast swathes of our infrastructure are dependent on them. The dangers of cyberwarfare are very real. At the same time, however, it's important that we don't exaggerate or misrepresent this threat. Movies and television sensationalize the abilities and proclivities of hackers for the sake of drama and entertainment. Real hackers are quite different, and their motives and actions are as diverse and varied as the people they hack. Real hacking is independent of platform and technology; it's often more of a case of appealing to the weakest element in the system: the human.
Ghost in the Wires is the autobiography of Kevin Mitnick, “the world's most wanted hacker”. His is a fascinating, even bizarre tale of the convergence of law enforcement, ego, and addiction. Thanks to Mitnick’s impressive abilities, equally impressive capacity for self-delusion and self-denial, and the media’s tendency to think the worst, exploits and escapades that start as harmless fun result in a years-long manhunt and nearly a decade of jail time.
Mitnick's gateway into hacking is “phone phreaking”, unauthorized access to the phone company’s systems. This was in the days before the Web, before even personal computers, when computing itself involved entering programs line-by-line into computer memory and watching the read-outs on a printer, not a screen. It’s an era utterly alien to someone of my generation, let alone younger readers—and I love reading about how people interacted with computers at that stage.
As computers and phones become more advanced, so too does Mitnick. He explains how he acquires the ability to clone cell phone numbers, and how he uses space in dormant accounts on university and company servers to store source code he steals from companies like Sun, Novell, and Motorola. He obtains access to the IRS and DMV records, which later becomes instrumental as he creates false identities and goes on the run.
Mitnick keeps the structure of the book strictly chronological, with just enough foreshadowing to whet our appetites in anticipation of future events. However, some common themes quickly emerge. After his first few brushes with law enforcement over his hacking, Mitnick attempts to “straighten out” and quit, only to relapse time and again. In this sense, hacking is an addiction—it’s a challenge that provides a cognitive reward. No matter how hard he tries to give it up, he returns to it. This inability to rein himself in, even when he recognizes the dangers and the possibility of overreaching, is one of the reasons he eventually gets caught and goes to jail.
Mitnick also faces a revolving door of betrayal. Best friends and confidantes turn coat and rat him out to get lighter punishments; people he thought he could rely on turn against him. I sympathize. However, these accounts are necessarily one-sided, and I get the sense from reading between the lines that there was a lot about Mitnick as a person that contributed to these changes of heart.
Ghost in the Wires is a hefty book, especially as a paperback, and the pace is very slow. Mitnick enjoys teasing out every detail of his latest hack or discovery. Yet I never tired of hearing about it; I seldom wanted to put this book down. I just wanted to know what happened next: what was the next hack, the next run-in with the law, the next problem Mitnick had to overcome? Even before he becomes a fugitive, there is a sense of danger always around the corner. Though he spends a lot of time celebrating his ability to outwit and evade security employees from the telephone companies, he also gives due credit to those people who manage to outwit him. Once in a while, a technician or sysadmin catches on and boots him out. My reading pace is different for every book, but I literally did not want to stop reading this, stealing every possible opportunity to read as much as I could each day. There is just never a dull moment in the book.
It’s also truly terrifying to see how quickly rumours become exaggerated and become part of the legal record. Mitnick stresses throughout the book that he never hacked for profit or out of malice. For him, it was merely an exercise in ego. That doesn’t excuse the actions, but it does mean that charges amounting to terrorism are unjust. The ignorance of the law enforcement and judicial officials involved in this case is staggering. The overreactions—not letting Mitnick have any access to a phone for national security reasons—are a sobering reminder of how easy it is to mislead people who are less informed. When those people are in positions of power, they can abuse or misuse that power unwittingly, under the impression they are acting in the interests of public safety.
Perhaps the most surprising revelation in this book isn’t a technical one at all. Rather, Mitnick accomplishes some of his most daring hacks through social engineering. It’s incredible how willing people are to help him cirumvent their own company’s security procedures. With a little research and some guile, Mitnick poses as an employee from another office, tells a plausible story, and gets remote access or other information that people shouldn’t be so ready to divulge.
The weakest link in our cybersecurity is not the technology. It’s us. The trusting operator, the cheerful colleague … these are all parts of being human and having positive interactions every day. But the best, most secure systems are worthless if all you need to do is sweet-talk someone into reseting an account’s password. Mitnick’s approach still works today. Just ask Mat Honan, who had his Amazon and Apple accounts hacked through social-engineering of customer support representatives, and from there, the hackers disassembled the rest of his digital existence.
Ghost in the Wires is that sweet spot of books about technology. It’s accessible to everyone. At times Mitnick’s terminology definitely becomes a little technical and specialized—I don’t know enough about how our phone system works to pretend to follow his explanations of how he tricks the system into rerouting calls and letting him listen into private conversations. But that didn’t affect my enjoyment of the book or my ability to follow what he was achieving. It also has a strong social message. Mitnick’s relationship with hacking is an addiction just as damaging to his life as an addiction to drugs or alcohol. Moreover, the book is a warning that unless we make sure people in positions of power are better-educated about the capabilities of technology, we run the risk of innocent lives being ruined by misinformed authorities.
The majority of Mitnick’s tale takes place in the 1980s and 1990s, in the infancy of the World Wide Web. There was no Facebook or Twitter, no Amazon or Google. Now we spend more and more of our lives online. Mitnick might have been the world’s first “most wanted hacker”, but I doubt he will be the last. And we’re all going to have to get a little more clued-in, or we will be in for a rough time.
Ghost in the Wires is the autobiography of Kevin Mitnick, “the world's most wanted hacker”. His is a fascinating, even bizarre tale of the convergence of law enforcement, ego, and addiction. Thanks to Mitnick’s impressive abilities, equally impressive capacity for self-delusion and self-denial, and the media’s tendency to think the worst, exploits and escapades that start as harmless fun result in a years-long manhunt and nearly a decade of jail time.
Mitnick's gateway into hacking is “phone phreaking”, unauthorized access to the phone company’s systems. This was in the days before the Web, before even personal computers, when computing itself involved entering programs line-by-line into computer memory and watching the read-outs on a printer, not a screen. It’s an era utterly alien to someone of my generation, let alone younger readers—and I love reading about how people interacted with computers at that stage.
As computers and phones become more advanced, so too does Mitnick. He explains how he acquires the ability to clone cell phone numbers, and how he uses space in dormant accounts on university and company servers to store source code he steals from companies like Sun, Novell, and Motorola. He obtains access to the IRS and DMV records, which later becomes instrumental as he creates false identities and goes on the run.
Mitnick keeps the structure of the book strictly chronological, with just enough foreshadowing to whet our appetites in anticipation of future events. However, some common themes quickly emerge. After his first few brushes with law enforcement over his hacking, Mitnick attempts to “straighten out” and quit, only to relapse time and again. In this sense, hacking is an addiction—it’s a challenge that provides a cognitive reward. No matter how hard he tries to give it up, he returns to it. This inability to rein himself in, even when he recognizes the dangers and the possibility of overreaching, is one of the reasons he eventually gets caught and goes to jail.
Mitnick also faces a revolving door of betrayal. Best friends and confidantes turn coat and rat him out to get lighter punishments; people he thought he could rely on turn against him. I sympathize. However, these accounts are necessarily one-sided, and I get the sense from reading between the lines that there was a lot about Mitnick as a person that contributed to these changes of heart.
Ghost in the Wires is a hefty book, especially as a paperback, and the pace is very slow. Mitnick enjoys teasing out every detail of his latest hack or discovery. Yet I never tired of hearing about it; I seldom wanted to put this book down. I just wanted to know what happened next: what was the next hack, the next run-in with the law, the next problem Mitnick had to overcome? Even before he becomes a fugitive, there is a sense of danger always around the corner. Though he spends a lot of time celebrating his ability to outwit and evade security employees from the telephone companies, he also gives due credit to those people who manage to outwit him. Once in a while, a technician or sysadmin catches on and boots him out. My reading pace is different for every book, but I literally did not want to stop reading this, stealing every possible opportunity to read as much as I could each day. There is just never a dull moment in the book.
It’s also truly terrifying to see how quickly rumours become exaggerated and become part of the legal record. Mitnick stresses throughout the book that he never hacked for profit or out of malice. For him, it was merely an exercise in ego. That doesn’t excuse the actions, but it does mean that charges amounting to terrorism are unjust. The ignorance of the law enforcement and judicial officials involved in this case is staggering. The overreactions—not letting Mitnick have any access to a phone for national security reasons—are a sobering reminder of how easy it is to mislead people who are less informed. When those people are in positions of power, they can abuse or misuse that power unwittingly, under the impression they are acting in the interests of public safety.
Perhaps the most surprising revelation in this book isn’t a technical one at all. Rather, Mitnick accomplishes some of his most daring hacks through social engineering. It’s incredible how willing people are to help him cirumvent their own company’s security procedures. With a little research and some guile, Mitnick poses as an employee from another office, tells a plausible story, and gets remote access or other information that people shouldn’t be so ready to divulge.
The weakest link in our cybersecurity is not the technology. It’s us. The trusting operator, the cheerful colleague … these are all parts of being human and having positive interactions every day. But the best, most secure systems are worthless if all you need to do is sweet-talk someone into reseting an account’s password. Mitnick’s approach still works today. Just ask Mat Honan, who had his Amazon and Apple accounts hacked through social-engineering of customer support representatives, and from there, the hackers disassembled the rest of his digital existence.
Ghost in the Wires is that sweet spot of books about technology. It’s accessible to everyone. At times Mitnick’s terminology definitely becomes a little technical and specialized—I don’t know enough about how our phone system works to pretend to follow his explanations of how he tricks the system into rerouting calls and letting him listen into private conversations. But that didn’t affect my enjoyment of the book or my ability to follow what he was achieving. It also has a strong social message. Mitnick’s relationship with hacking is an addiction just as damaging to his life as an addiction to drugs or alcohol. Moreover, the book is a warning that unless we make sure people in positions of power are better-educated about the capabilities of technology, we run the risk of innocent lives being ruined by misinformed authorities.
The majority of Mitnick’s tale takes place in the 1980s and 1990s, in the infancy of the World Wide Web. There was no Facebook or Twitter, no Amazon or Google. Now we spend more and more of our lives online. Mitnick might have been the world’s first “most wanted hacker”, but I doubt he will be the last. And we’re all going to have to get a little more clued-in, or we will be in for a rough time.
May 31, 2022
DNF ~25%
Fatphobic, misogynistic, and unbearably arrogant. Yeah, I'm gonna pass...
Fatphobic, misogynistic, and unbearably arrogant. Yeah, I'm gonna pass...
March 4, 2022
What a great book! I enjoyed every minute of it on Audible. I can say both that I learned a lot and that my fascination with the hacker culture from inception to present has increased. I've heard of Mitnick from his TED talk and was delighted to see he had several books on the market. For someone like me, Mitnick definitely has had one of the most intense, exciting and interesting life stories. This book has had all I was looking for: enough relevant information on the personal life and relationships (romantic, family, work, childhood), the thought process and motivation behind this type of pursuit and its consequences back when there was no legislation surrounding it, a solid narrative without excess of information, a technical narrative enough to satisfy my curiosity and maintain excitement, and much more. Everybody's journey is different, but for me this was a solid example of "what makes the mind of a hacker tick" and has brought me closer to technology and to understanding our relationship with it. Despite initial prejudice, I'm really glad to see how much this culture grew and came to form what we now know as cybersecurity, pentesting, ethical hacking and so on.
August 1, 2016
Executive Summary: I enjoyed this book, but it may only appeal to computer/phone geeks, or True Crime junkies.
Full Review
I ended up rereading this book with a few friends after attempting to pick something they would hopefully enjoy that they wouldn't have read otherwise. The jury is still out, but it looks like I might have done a poor job. I enjoyed the reread, but this book won't be for everyone.
I've always been fascinated by the early days of computers and the internet, especially where computer cracking is involved. The late 70s and the 80s were basically the wild west. The idea of networked computers was so new that government was slow to react to those who took advantage.
When they did finally react, it was often to an extreme, which I think is evident in some of the treatment Mr. Mitnick receives from law enforcement. Some of the rumors that developed around him over the years were pretty ludicrous. Not all of them however, and he could be a scary person to cross.
I've read many books on the subject over the years. It's one of the few non-fiction subjects I'm interested in enough to read on my own away from school assigned reading. I even wrote a term paper on it in High School. How I managed to convince my teacher to let me read a bunch of books on computer crime, I don't really remember at this point.
It's hard to read about computer crime and not come across Kevin Mitnick. He's arguably the most famous, or at least the most notorious computer "hacker" of his time.
I find it interesting that Mr. Mitnick has embraced the new definition of Hacker. In fact he doesn't even bother to explain the difference. Back when he was active he would have been considered more of a Phone Phreak (which he does cover a bit) or a Cracker.
Hacker used to be a nickname for obsessive computer types that would dig into depths of systems and code looking for the nooks and crannies.
Maybe he chooses to call himself a Hacker because he's trying to appeal to a wider audience that wouldn't know the difference. Or maybe it's because he doesn't seem to feel like what he did was all that wrong, and might self identify with the original definition.
While Mr. Mitnick's computer skills are no doubt impressive, I think most of his success can be attributed more to his Social Engineering skills rather than his technical ability. That and his ability to exploit the things he learns.
Social Engineering for those unfamiliar, can be defined as the art of manipulating people into performing actions or divulging confidential information.
It essentially a different way of saying to con someone, or the term used where computers and/or technology is involved. It relies heavily on knowledge of your targets security procedures and vulnerabilities. Often time people are the weakest link in computer security.
Most of what Mr. Mitnick does is built on the work of others, exploiting bugs found by other people and the trusting and/or lazy nature of people rather than discovering new flaws on his own.
He manages to obtain the source code for numerous operating systems over the years, but often time doesn't bother to spend any time looking at the code, he simply obtains it like a trophy.
I can only theorize that he's incredibly charismatic. Reading this book he doesn't come off as a very likable person to me, yet people seem to jump to help him, even as he abuses their trust and love. That's probably part of why he's so successful at Social Engineering.
One of my friends describe the book as repetitive. For someone not interested in the technology aspect, I can see how this is true. At a high level he used a lot of the same techniques to break into more and more complex systems, especially as the level of computer knowledge and security practices continued to evolve over the years.
He tries to explain the various technical terms as he goes, and I had no trouble following what he wrote, but I was already familiar with a lot of the stuff ahead of time.
It might get tedious or frustrating to those without any background. Similarly it might get tedious to those with more technical knowledge as he explains what may seem like basic concepts.
The book seems to toggle between him trying to elicit sympathy from the reader for his exploits, and apologizing to the people he wronged over the years, especially his mother and grandmother.
To be fair, a lot of incorrect and overly negative things were published about Mr. Mitnick over the years, while he was legally prevented from telling his side of things.
Like I said in my original review, I'm sure the truth is somewhere in the middle of the two extremes.
Despite the negatives, his story is an incredibly unique, and to me at least an interesting one. Parts of it read like it's straight from a spy novel. He uses his abilities not only to hide from his pursuers, but to spy on them to see how close they are getting.
In the end his ego, and his inability to stop breaking into computer systems proves to be his downfall. He may not think so, but considering the fear he elicited in those pursuing and prosecuting him, he was incredibly lucky to come away like he did, and now to have a successful business where people pay him to do the kinds of things he went to jail for.
------------------Original Review------------------
Forgot to add this book. I noticed after putting another book on my shelves.
I recall really enjoying this. After reading several books biased against Mitnick, it was nice to contrast that with something biased for him instead.
It's hard to know what really happened. I'm sure it lies somewhere in the middle.
Either way, it is a pretty interesting read and I'd recommend it to anyone interested in computers, or social engineering. It really is scary the kinds of things he can do.
Full Review
I ended up rereading this book with a few friends after attempting to pick something they would hopefully enjoy that they wouldn't have read otherwise. The jury is still out, but it looks like I might have done a poor job. I enjoyed the reread, but this book won't be for everyone.
I've always been fascinated by the early days of computers and the internet, especially where computer cracking is involved. The late 70s and the 80s were basically the wild west. The idea of networked computers was so new that government was slow to react to those who took advantage.
When they did finally react, it was often to an extreme, which I think is evident in some of the treatment Mr. Mitnick receives from law enforcement. Some of the rumors that developed around him over the years were pretty ludicrous. Not all of them however, and he could be a scary person to cross.
I've read many books on the subject over the years. It's one of the few non-fiction subjects I'm interested in enough to read on my own away from school assigned reading. I even wrote a term paper on it in High School. How I managed to convince my teacher to let me read a bunch of books on computer crime, I don't really remember at this point.
It's hard to read about computer crime and not come across Kevin Mitnick. He's arguably the most famous, or at least the most notorious computer "hacker" of his time.
I find it interesting that Mr. Mitnick has embraced the new definition of Hacker. In fact he doesn't even bother to explain the difference. Back when he was active he would have been considered more of a Phone Phreak (which he does cover a bit) or a Cracker.
Hacker used to be a nickname for obsessive computer types that would dig into depths of systems and code looking for the nooks and crannies.
Maybe he chooses to call himself a Hacker because he's trying to appeal to a wider audience that wouldn't know the difference. Or maybe it's because he doesn't seem to feel like what he did was all that wrong, and might self identify with the original definition.
While Mr. Mitnick's computer skills are no doubt impressive, I think most of his success can be attributed more to his Social Engineering skills rather than his technical ability. That and his ability to exploit the things he learns.
Social Engineering for those unfamiliar, can be defined as the art of manipulating people into performing actions or divulging confidential information.
It essentially a different way of saying to con someone, or the term used where computers and/or technology is involved. It relies heavily on knowledge of your targets security procedures and vulnerabilities. Often time people are the weakest link in computer security.
Most of what Mr. Mitnick does is built on the work of others, exploiting bugs found by other people and the trusting and/or lazy nature of people rather than discovering new flaws on his own.
He manages to obtain the source code for numerous operating systems over the years, but often time doesn't bother to spend any time looking at the code, he simply obtains it like a trophy.
I can only theorize that he's incredibly charismatic. Reading this book he doesn't come off as a very likable person to me, yet people seem to jump to help him, even as he abuses their trust and love. That's probably part of why he's so successful at Social Engineering.
One of my friends describe the book as repetitive. For someone not interested in the technology aspect, I can see how this is true. At a high level he used a lot of the same techniques to break into more and more complex systems, especially as the level of computer knowledge and security practices continued to evolve over the years.
He tries to explain the various technical terms as he goes, and I had no trouble following what he wrote, but I was already familiar with a lot of the stuff ahead of time.
It might get tedious or frustrating to those without any background. Similarly it might get tedious to those with more technical knowledge as he explains what may seem like basic concepts.
The book seems to toggle between him trying to elicit sympathy from the reader for his exploits, and apologizing to the people he wronged over the years, especially his mother and grandmother.
To be fair, a lot of incorrect and overly negative things were published about Mr. Mitnick over the years, while he was legally prevented from telling his side of things.
Like I said in my original review, I'm sure the truth is somewhere in the middle of the two extremes.
Despite the negatives, his story is an incredibly unique, and to me at least an interesting one. Parts of it read like it's straight from a spy novel. He uses his abilities not only to hide from his pursuers, but to spy on them to see how close they are getting.
In the end his ego, and his inability to stop breaking into computer systems proves to be his downfall. He may not think so, but considering the fear he elicited in those pursuing and prosecuting him, he was incredibly lucky to come away like he did, and now to have a successful business where people pay him to do the kinds of things he went to jail for.
------------------Original Review------------------
Forgot to add this book. I noticed after putting another book on my shelves.
I recall really enjoying this. After reading several books biased against Mitnick, it was nice to contrast that with something biased for him instead.
It's hard to know what really happened. I'm sure it lies somewhere in the middle.
Either way, it is a pretty interesting read and I'd recommend it to anyone interested in computers, or social engineering. It really is scary the kinds of things he can do.
December 28, 2011
Kevin Mitnick is a legendary figure in Internet culture for both his odyssey of justice and rightly revered social engineering skills. Despite his hacks being marked by being utterly meticulous, that rigor did not make it into this book. The stories are fun but too much of the text fails:
*Future events are given away sometimes chapters ahead of time like when he compares his flight from Denver to his flight from the South.
*A lot of crappy figures of speech like "hit me like a ton of bricks". You can do better.
*A goodly amount of self defense in the form of "this attack on me was false". These are superfluous as the reader that is paying attention knows which of the claims go which way.
*Random inclusion or exclusion of technical detail. How wildcard characters are explained twice in two disjoint chapters but in one between.
*Very little actual insight is offered. He talks at the end on how he's brought in to speak on how to make organizations safer but he makes no reference to these recommendations.
*A goodly number of "look how clever I am". Yes, we get it, you're smart.
Skip.
*Future events are given away sometimes chapters ahead of time like when he compares his flight from Denver to his flight from the South.
*A lot of crappy figures of speech like "hit me like a ton of bricks". You can do better.
*A goodly amount of self defense in the form of "this attack on me was false". These are superfluous as the reader that is paying attention knows which of the claims go which way.
*Random inclusion or exclusion of technical detail. How wildcard characters are explained twice in two disjoint chapters but in one between.
*Very little actual insight is offered. He talks at the end on how he's brought in to speak on how to make organizations safer but he makes no reference to these recommendations.
*A goodly number of "look how clever I am". Yes, we get it, you're smart.
Skip.
July 7, 2012
Read this, if for no other reason to understand, in a fun way, those sweet, early, open, pre-commercialized days of the Internet in the 1980s and 1990s. Don't knock it: nostalgia is a great motivator.
Full disclosure: I found 2600 magazine in high school (among the zines at a local indie record store, fortunately) and had several Free Kevin stickers. The downright illegal means used by law enforcement to pursue Mitnick, and the legal system's irrationality and unjust punishment of him, provided one of my earliest and most memorable lessons about corporate and government collusion and power, and I wanted a refresher course as well as more information than I had in the early 1990s. Hence, this book.
Mitnick does a terrific job describing technical concepts involved in hacking, that I think are easy enough for the lay person to understand, especially because most of his tactics involved social engineering: calling people up and asking for information outright. This is key, since most people's concepts of hacking is focused entirely online. I remember when I worked in technical support, for example, and ran into some fraud cases. For credit cards, it was easy to predict (down to the exact 2-3 days each month) when fraudulent purchases would spike, because we knew their statement cycles and thus when paper statements would arrive in mailboxes. (In the late 1990s, they still bore the full credit card number.) Almost all online purchase fraud at the time was due to simple mail theft.
Mitnick does not try to make what he did seem overly complicated or focus on the technical aspects of hacking to the exclusion of the social ones: he doesn't try to get the lay reader to admire him even more by belaboring these points, as he could have.
The book is just packed with great anecdotes and highly entertaining. As others have said, it very much reads like a suspense novel at times. Mitnick's honesty is refreshing, as it's there even when it doesn't cast him in a "glorified hacker" light: Mitnick is honest, for example, about the extent to which he depended on the kindness of others, and how he lived when he had little or no money. Hackers tend to be represented by the media as if they spend their days flying between Monaco and the Cayman Islands (and I'm sure some of them do), but it's a myth that Mitnick does a nice job of busting with detail about his life. It's strip malls, Kinko's and Sizzler rather than Corsica and Durban.
Mitnick has always maintained his innocence, so I expected a lot of "I did not do this," but that's not what you get. He very much describes what he did, but is also very clear about what he did not do.
The book is very much a public service because it provides specific, well documented detail on the lengths to which law enforcement officials will go to frame someone, essentially, and put them in jail simply because they want, "feel" or "believe" they belong there, even when there is no evidence. There was, in the Mitnick case, tremendous lack of responsibility and professionalism on the part of the FBI and several police departments, and the public should know the specifics. The FBI needing to, and illegally hiring a civilian to, catch Mitnick, for instance, indicates that he most likely would not have been caught by law enforcement alone. While this does, yes, cast Mitnick in a more sympathetic light, it's much more valuable than that.
Finally, it was simply nice to hear Kevin's voice. It's a nice balance between personal, memoir style content and technical stories. It definitely makes me want to attend one of his talks.
Full disclosure: I found 2600 magazine in high school (among the zines at a local indie record store, fortunately) and had several Free Kevin stickers. The downright illegal means used by law enforcement to pursue Mitnick, and the legal system's irrationality and unjust punishment of him, provided one of my earliest and most memorable lessons about corporate and government collusion and power, and I wanted a refresher course as well as more information than I had in the early 1990s. Hence, this book.
Mitnick does a terrific job describing technical concepts involved in hacking, that I think are easy enough for the lay person to understand, especially because most of his tactics involved social engineering: calling people up and asking for information outright. This is key, since most people's concepts of hacking is focused entirely online. I remember when I worked in technical support, for example, and ran into some fraud cases. For credit cards, it was easy to predict (down to the exact 2-3 days each month) when fraudulent purchases would spike, because we knew their statement cycles and thus when paper statements would arrive in mailboxes. (In the late 1990s, they still bore the full credit card number.) Almost all online purchase fraud at the time was due to simple mail theft.
Mitnick does not try to make what he did seem overly complicated or focus on the technical aspects of hacking to the exclusion of the social ones: he doesn't try to get the lay reader to admire him even more by belaboring these points, as he could have.
The book is just packed with great anecdotes and highly entertaining. As others have said, it very much reads like a suspense novel at times. Mitnick's honesty is refreshing, as it's there even when it doesn't cast him in a "glorified hacker" light: Mitnick is honest, for example, about the extent to which he depended on the kindness of others, and how he lived when he had little or no money. Hackers tend to be represented by the media as if they spend their days flying between Monaco and the Cayman Islands (and I'm sure some of them do), but it's a myth that Mitnick does a nice job of busting with detail about his life. It's strip malls, Kinko's and Sizzler rather than Corsica and Durban.
Mitnick has always maintained his innocence, so I expected a lot of "I did not do this," but that's not what you get. He very much describes what he did, but is also very clear about what he did not do.
The book is very much a public service because it provides specific, well documented detail on the lengths to which law enforcement officials will go to frame someone, essentially, and put them in jail simply because they want, "feel" or "believe" they belong there, even when there is no evidence. There was, in the Mitnick case, tremendous lack of responsibility and professionalism on the part of the FBI and several police departments, and the public should know the specifics. The FBI needing to, and illegally hiring a civilian to, catch Mitnick, for instance, indicates that he most likely would not have been caught by law enforcement alone. While this does, yes, cast Mitnick in a more sympathetic light, it's much more valuable than that.
Finally, it was simply nice to hear Kevin's voice. It's a nice balance between personal, memoir style content and technical stories. It definitely makes me want to attend one of his talks.
January 12, 2017
The ONLY reason I kept listening to this audiobook was so I could write a scathing review of it. I kept reminding myself that soon it would be over, soon I could rant about how awful this book is, soon I would be able to warn others not to waste their time on this story... but this book is so bad that even my raging spite almost wasn't enough to get me through it. The first 5 hours or so (the first third of the book) were fine; nothing great, but interesting enough. After that point, though, I'd had it with this selfish, boastful, whiny, condescending, unkind manchild. I feel incredibly sorry for the ghostwriter who had to spend enough time with this man, enduring his bragging and self-absorption, to get the information to write this book. Most of this book is KM repeating the same trick over and over, gloating about how easily duped his marks are and how superior he is to them (although when he quickly gets his way then he's disappointed that there was no challenge, and when things are hard then he's frustrated by how difficult they are), each time either getting caught or almost getting caught, oftentimes because he's been ratted out by a friend (and yet he's constantly shocked when his friends --all of them hackers who, like KM, rely on lying to people in order to get information they are not supposed to have-- repeatedly betray him), which brings on a wave of panic and cursing and lamenting about how his loving grandmother and mother are having to bear so much stress. Wash, rinse, repeat. Never does he express any remorse for his actions, choosing instead to slam "the Feds" for slandering him, the justice system for failing to understand him, and his associates for ratting him out or making mistakes that get him caught. Not once does he say anything about how it's HIS fault that his grandmother and mother are under stress, not once does he acknowledge that if he stopped hacking then he wouldn't have to worry about being arrested and imprisoned, not once does he own up to the immorality of his actions or accept that actions have consequences. No, he's just a curious guy who hacks for the thrill of it, and really, what's so bad about that? Apparently the law doesn't apply to KM, because HE never hurt anyone (what about the people whose trust he broke? The people he social-engineered who were potentially fired or demoted for having compromised their companies? The time, energy, and money he cost hundreds --thousands?-- of people by tricking them into sending him information?), so obviously he's not a bad guy, he's a poor widdle misunderstood hacker, deserving of your sympathy as the big bad government chases him down. He compares himself multiple times to wrongfully accused protagonists in various man-vs.-government stories and complains at length about the way he is prosecuted and sentenced and treated when he is caught-- although he gets away with most of the crimes he committed, because no one knew the extent to which he had been stealing private information. He is desperate to reassure us that he is not the bad guy, repeating ad nauseam that he never used his information for monetary gain. He repeats this so often, in fact, that it begins to feel like a case of "the lady doth protest too much." His concern for his mother and grandmother amounts to repeated assertions that he felt terrible they were experiencing such stress, but that trite line is it. His purported love and concern never stop him from involving them in his various schemes to evade and outwit law enforcement. He praises them for their love and support and gets frustrated with his dad for the lack of that same love and support, but it seems to me like he's mistaking love for enabling, particularly because, despite how much he asserts that he loves his mom and grandmother, he never swears off the hacking --> arrest --> jail --> repeat cycle that is causing them so much pain or acknowledges that when he is arrested and sent to jail it is because he spends most of his time voluntarily, blatantly, repeatedly, and without any sort of provocation or mitigating circumstances whatsoever, breaking the law. He also goes on at length about how much he works out and how fit he is, and once he gets in shape, he reports regularly on how attracted women are to him and how he has to keep them at a distance because he can't risk accidentally telling them about his fugitive status while in the throes of passion. Although --naturally-- he is a glowing specimen, the plebeians surrounding him are anything but; he describes everyone else in the memoir either in completely flat terms (e.g. his mom & grandmother, who have no personality or defining characteristics besides KM reporting them --and it's always telling, never showing-- as being loving and supportive of KM) or disparaging terms (he makes fun of people's accents, weight, clothing, voices, personalities, the whole shebang). KM speaks kindly of people only when they are useful to him; everyone else earns his disdain. He also has a highly annoying penchant for including what seems to be every last goshdarn phone number he has ever dialed. I mean, fine, that's a hyperbole, but there are an awful lot of phone numbers in this book. Hmm, that's a little odd, isn't it? Telephone numbers don't make for good reading. How necessary are these phone numbers, anyway? Oh, they're critical-- after all, without these phone numbers, KM wouldn't be able to tell you multiple times that this is the exact number he dialed twenty years ago! Look how good he is at remembering phone numbers! Aren't you impressed? How about now? Here's another number, what about now? You're impressed, right? ...Right? It's especially priceless to hear him slam other people for being arrogant, as this book is a massive paean to him and his technological prowess. And if after 350 pages you aren't convinced of his brilliance, then make sure to read the last chapter, because he spends it rattling off all of the talk shows he's been on, the famous people he's friends with, how successful his radio show is, how he's a rock star in Poland, how well his previous book sold, how he does this and that and wow isn't he just phenomenal and glorious and oh my gosh KM is great and we should all worship him now. You'll want to drink ipecac after reading this book. It is that nauseating. At least I didn't spend any money on it, because not only is the book just plain bad, but also the idea of financially supporting this man is repugnant. Still, I'd be even happier if I hadn't read it in the first place, because although I enjoyed writing this review, I did not enjoy writing it enough to make it worth my 14 hours worth of audiobook listening time that I will never get back. We may be only 12 days into 2017, but this is already a very strong contender for worst book I read this year. Definitely avoid reading it.
October 5, 2011
Year ago before Tech TV morphed into G4 (and we were treated to endless repeats of Cops and Cheaters), I happened to tune in one afternoon to see an interview with notorious hacker Kevin Mitnick. At the time, Mitnick promoted his book The Art of Deception and discussion in general terms how he wasn't necessarily a hacker so much as a social engineer. Mitnick went on to say that part of his sentence was a gag order that prevented his specifically discussing his crimes and life as a hacker for the next decade or so, but he promised that we'd eventually get a book detailing his early days.
I was intrigued enough to pick up The Art of Deception and quickly read through it. It's a must-read for anyone interesting in making sure you keep your personal or company information out of the hands of people who either enjoy the thrill of collecting it as Mitnick did or want to do something more nefarious with it.
A decade or so later, we've finally reached the day when Mitnick can come clean and detail his life as the most wanted hacker in America. His autobiography Ghost in the Wires is every bit as fascinating as I'd hoped it would be when I first heard from Mitnick all those years ago. At long last, we could finally see inside the world Mitnick hinted at in that interview and in his previous two books.
Mitnick's story of how he learned how to hack various phone systems and social engineer his way into the databases of multiple phone companies is a fascinating one. Mitnick repeatedly asserts that he wasn't interested in committing any kind of criminal act so much as he enjoyed the thrill of seeing if he could do something and how it could be done. At times, the book is a page-turner as we see inside Mitnick's world of how his life of hacking consumed him at times, while at others he tried to walk away and not hack any more. There are some technical discussions of what Mitnick did or various software programs he was interested in seeing that, quite frankly, I just skimmed. It may be interesting to those with a detailed knowledge of these things, but what I found more compelling was the human story Mitnick tells.
At times, Mitnick is a bit short-sighted in things and that comes across. His repeated surprise that anyone would be interested in what he was doing, much less want to arrest and prosecute him is amusing.
Reading Ghost in the Wires I kept thinking that Mitnick's story is one that is just begging to be turned into a movie--assuming you can get the right creative team behind the project. Last year, audiences watched the creation of Facebook on the big screen. I'd argue the story Mitnick has to tell is far more Hollywood ready than that one.
I was intrigued enough to pick up The Art of Deception and quickly read through it. It's a must-read for anyone interesting in making sure you keep your personal or company information out of the hands of people who either enjoy the thrill of collecting it as Mitnick did or want to do something more nefarious with it.
A decade or so later, we've finally reached the day when Mitnick can come clean and detail his life as the most wanted hacker in America. His autobiography Ghost in the Wires is every bit as fascinating as I'd hoped it would be when I first heard from Mitnick all those years ago. At long last, we could finally see inside the world Mitnick hinted at in that interview and in his previous two books.
Mitnick's story of how he learned how to hack various phone systems and social engineer his way into the databases of multiple phone companies is a fascinating one. Mitnick repeatedly asserts that he wasn't interested in committing any kind of criminal act so much as he enjoyed the thrill of seeing if he could do something and how it could be done. At times, the book is a page-turner as we see inside Mitnick's world of how his life of hacking consumed him at times, while at others he tried to walk away and not hack any more. There are some technical discussions of what Mitnick did or various software programs he was interested in seeing that, quite frankly, I just skimmed. It may be interesting to those with a detailed knowledge of these things, but what I found more compelling was the human story Mitnick tells.
At times, Mitnick is a bit short-sighted in things and that comes across. His repeated surprise that anyone would be interested in what he was doing, much less want to arrest and prosecute him is amusing.
Reading Ghost in the Wires I kept thinking that Mitnick's story is one that is just begging to be turned into a movie--assuming you can get the right creative team behind the project. Last year, audiences watched the creation of Facebook on the big screen. I'd argue the story Mitnick has to tell is far more Hollywood ready than that one.
January 4, 2013
This book gives a glimpse into the mind of a true obsessive. And as long as this book is (overly long for the content), I suspect it only tells about half the real story. *Never* (once) used a hacked credit card? Come on. Never took any money for stolen source code? Very doubtful. The true obsessive will try to justify and try to paint their activities in a positive light later in order to self-justify their sociopathic behavior. But, I rated this book highly, not because it's all true, or because I sympathize with Kevin, or even because it's well written (not particularly), but because it's fascinating. Like many reviewers here, I had heard the stories during the time, but did not remotely understand the extent of the social engineering Kevin performed. It's breathtaking, really, the audacity of the impersonation he did. The book spends the majority of its time detailing such attacks. It spends comparably much less detailing the actual computer and phreaking hacking that he did. I suspect there was a great deal more of it than the book details, but this is left out, I'm sure for liability and self-incrimination reasons. But to a programmer, it really feels missing. Sure, he described the .rhost attacks (a little), but most of the zero-day exploits we the reader are left to guess at. It's a bit annoying that his sociopathy is being rewarded with book revenue, but this is a story that needed to be told, as a cautionary tale, if nothing else.
December 18, 2012
Kevin Mitnick is an arrogant jerk. But since I'm still processing my affection for arrogant jerks that doesn't really interfere with my enjoyment of his book. Though it's hard not to roll my eyes hard and how super-fantastic everything turns out for him in the end.
The story of Mitnick's hacking, his two and a half year evasion of the police and FBI and his subsequent trial is constantly engaging and occasionally exciting, filled with tips, quirky asides, and the occasional bit of jargon pitched just above my competence.
The audiobook's narrator Ray Porter does a good job, but is sometimes a little too glib.
The story of Mitnick's hacking, his two and a half year evasion of the police and FBI and his subsequent trial is constantly engaging and occasionally exciting, filled with tips, quirky asides, and the occasional bit of jargon pitched just above my competence.
The audiobook's narrator Ray Porter does a good job, but is sometimes a little too glib.
January 6, 2012
I was forced to read this by my Hubby. Needless to say, he's a bit of a computer geek. This was the first book he read cover to cover since finishing law school so I did feel somewhat obligated to pick it up.
The book is by Kevin Mitnick about his adventures in hacking. I would definitely not call the book well written but I did find his life fascinating. He started hacking as a teenager and never stopped. He's as addicted to it as one might be to heroine. No exaggeration. Despite being arrested and thrown in solitary confinement, the man could not stop hacking. Even when he crossed the line and his crimes delved into federal territory, he kept at it. Despite being double-crossed by nearly all his friends, losing his wife and breaking his Mother's heart over and over again, he still could not stop. He's an addict through and through. I don't know how else to describe him.
While I found his selfishness detestable, I did appreciate his skills and his ability to thumb his nose at authority. The best part of the book is by far when he discovers his own investigation. He's able to eavesdrop on investigators that are eavesdropping on him. I can't help but respect him for that. His skills are amazing.
If you are technically minded this book is for you. If computer lingo bores you to tears steer clear. It is definitely not for the light reader.
The book is by Kevin Mitnick about his adventures in hacking. I would definitely not call the book well written but I did find his life fascinating. He started hacking as a teenager and never stopped. He's as addicted to it as one might be to heroine. No exaggeration. Despite being arrested and thrown in solitary confinement, the man could not stop hacking. Even when he crossed the line and his crimes delved into federal territory, he kept at it. Despite being double-crossed by nearly all his friends, losing his wife and breaking his Mother's heart over and over again, he still could not stop. He's an addict through and through. I don't know how else to describe him.
While I found his selfishness detestable, I did appreciate his skills and his ability to thumb his nose at authority. The best part of the book is by far when he discovers his own investigation. He's able to eavesdrop on investigators that are eavesdropping on him. I can't help but respect him for that. His skills are amazing.
If you are technically minded this book is for you. If computer lingo bores you to tears steer clear. It is definitely not for the light reader.
September 3, 2020
First, I bow down to the legend.
Second, OH MY GOD, what an awesome life he has lived!
His expertise, knack for finding out how things work and talent has made him worthy of the amount of luck he had in his adventurous days and in his new life.
I wish I had one per cent of anything he had :(
But this book made me elated, made me think about technology and security :D
Second, OH MY GOD, what an awesome life he has lived!
His expertise, knack for finding out how things work and talent has made him worthy of the amount of luck he had in his adventurous days and in his new life.
I wish I had one per cent of anything he had :(
But this book made me elated, made me think about technology and security :D
May 8, 2012
شبح في الأسلاك: مغامراتي كأهم هاكر مطلوب عالمياً
أعرف أن ترجمتي للعنوان غير جذابة، ولكن الكتاب ممتع ومثير، وشخصية كيفن ميتنك وما مر به من أحداث، تجذب القارئ لمتابعة القصة التي تبدو كأحد أفلام هوليود، وقد تحولت بالفعل إلى فيلم فيما بعد وإن كان غير مرضٍ لميتنك لأن الفيلم قام بشيطنته، وكان سيسبب له الكثير من المشاكل لولا تدخله، لحذف بعض المشاهد التي كانت ستخلده في الذاكرة كأحد أسوأ الشخصيات على الإطلاق.
الهاكر هو قاطع الطريق الالكتروني، نسخة العصر الحديث الذي يمكنه الوصول إلى معلوماتك أو أموالك، سرقتها أو تدميرها، ميتنك كان مختلفاً، في أنه كان يؤكد طيلة الكتاب أنه لم يفعل شيئاً من هذا، لم يقم بأعمال الاختراق التي قام بها إلا من أجل متعة التحدي فقط، لم يحصل على أموال، لم يضر بأحد بشكل مباشر، نعم كان محتالاً، وخدع الكثيرين بما كان يسميه (الهندسة الاجتماعية)، والتي يعني بها التلاعب بالضحية، من خلال إيهامه بأن ميتنك زميل أو شخص مسئول، ومن خلال هذا يكلفه بأعمال، أو يحصل منه على معلومات، تسهل له اختراق الشركات.
أهداف ميتنك كانت دائماً، شركات الهواتف والانترنت، ودائماً كان له أصدقاء، تساقطوا مع الوقت، وخانوه، حتى وصل إلى اللحظة التي فر فيها هارباً تطارده الـ FBI، ولكنه كان ذكياً جداً، قادراً على تغيير شخصيته، استصدار أوراق مزيفة، بل حتى الحصول على عمل في شركات في مدن أمريكية مختلفة، والعمل هناك تحت ستار، مواصلاً أعماله الخاصة ليلاً.
قصة ميتنك كما قلت تبدو ��فيلم هوليودي بالفعل، ملاحقات بالهليوكوبتر، هروب متواصل، وتغيير للشخصية، بل تصل القصة إلى ذروتها عندما تستعين الـ FBI، بخبير أمني شاب من أصل ياباني يدعى (تسوتومو شيمومورا)، كان ميتنك قد اخترقه، فلذا صارت المعركة ساموراية، معركة شرف بالنسبة إلى شيمومورا، تضيق الحلقة على ميتنك، حتى لحظة اعتقاله سنة 1995 م، والضجة الإعلامية التي صاحبت ذلك، وأيام سجنه العصيبة التي حرم فيها من بعض حقوقه، ووجد نفسه وقد تحول في نظر الإعلام والقضاة إلى خطر قومي، حيث تسربت فكرة غير صحيحة عنه أنه اخترق الـ FBI، والـ CIA، وأنظمة الدفاع، وهي صورة كادت تؤدي به إلى السجن لسنوات طويلة.
الكتاب ممتع، وميتنك يجذبك من الصفحات الأولى، بقصصه الطريفة، صحيح أن تفاصيل الاختراق طويلة، وقد تبدو مملة للبعض، وقد يتوه القارئ قليلاً مع التفاصيل التي لا يلم بها، ولكن روح ميتنك ومغامراته تبقي القارئ حتى نهاية الكتاب.
سأورد كمثال قصة طريفة أوردها ميتنك في بداية الكتاب، كيف أنه وأحد أصدقائه في فترة المراهقة قاموا، باختراق الموجة اللاسلكية لمطعم ماكدونالدز، مما جعلهم قادرين على استقبال طلبات الزبائن من خلال خدمة السيارات، وقد قاموا بعدد من المقالب، كان من أطرفها أنهم كانوا يقولون للعميل حال وصوله أنهم يقدمون اليوم عصير تفاح مجاني، والعميل بالطبع يوافق على الحصول عليه، عندها كانوا يقومون بتشغيل تسجيل لصوت شخص يتبول في كأس، بعدها كانوا يقولون للعميل: تفضل عصيرك جاهز :)
أعرف أن ترجمتي للعنوان غير جذابة، ولكن الكتاب ممتع ومثير، وشخصية كيفن ميتنك وما مر به من أحداث، تجذب القارئ لمتابعة القصة التي تبدو كأحد أفلام هوليود، وقد تحولت بالفعل إلى فيلم فيما بعد وإن كان غير مرضٍ لميتنك لأن الفيلم قام بشيطنته، وكان سيسبب له الكثير من المشاكل لولا تدخله، لحذف بعض المشاهد التي كانت ستخلده في الذاكرة كأحد أسوأ الشخصيات على الإطلاق.
الهاكر هو قاطع الطريق الالكتروني، نسخة العصر الحديث الذي يمكنه الوصول إلى معلوماتك أو أموالك، سرقتها أو تدميرها، ميتنك كان مختلفاً، في أنه كان يؤكد طيلة الكتاب أنه لم يفعل شيئاً من هذا، لم يقم بأعمال الاختراق التي قام بها إلا من أجل متعة التحدي فقط، لم يحصل على أموال، لم يضر بأحد بشكل مباشر، نعم كان محتالاً، وخدع الكثيرين بما كان يسميه (الهندسة الاجتماعية)، والتي يعني بها التلاعب بالضحية، من خلال إيهامه بأن ميتنك زميل أو شخص مسئول، ومن خلال هذا يكلفه بأعمال، أو يحصل منه على معلومات، تسهل له اختراق الشركات.
أهداف ميتنك كانت دائماً، شركات الهواتف والانترنت، ودائماً كان له أصدقاء، تساقطوا مع الوقت، وخانوه، حتى وصل إلى اللحظة التي فر فيها هارباً تطارده الـ FBI، ولكنه كان ذكياً جداً، قادراً على تغيير شخصيته، استصدار أوراق مزيفة، بل حتى الحصول على عمل في شركات في مدن أمريكية مختلفة، والعمل هناك تحت ستار، مواصلاً أعماله الخاصة ليلاً.
قصة ميتنك كما قلت تبدو ��فيلم هوليودي بالفعل، ملاحقات بالهليوكوبتر، هروب متواصل، وتغيير للشخصية، بل تصل القصة إلى ذروتها عندما تستعين الـ FBI، بخبير أمني شاب من أصل ياباني يدعى (تسوتومو شيمومورا)، كان ميتنك قد اخترقه، فلذا صارت المعركة ساموراية، معركة شرف بالنسبة إلى شيمومورا، تضيق الحلقة على ميتنك، حتى لحظة اعتقاله سنة 1995 م، والضجة الإعلامية التي صاحبت ذلك، وأيام سجنه العصيبة التي حرم فيها من بعض حقوقه، ووجد نفسه وقد تحول في نظر الإعلام والقضاة إلى خطر قومي، حيث تسربت فكرة غير صحيحة عنه أنه اخترق الـ FBI، والـ CIA، وأنظمة الدفاع، وهي صورة كادت تؤدي به إلى السجن لسنوات طويلة.
الكتاب ممتع، وميتنك يجذبك من الصفحات الأولى، بقصصه الطريفة، صحيح أن تفاصيل الاختراق طويلة، وقد تبدو مملة للبعض، وقد يتوه القارئ قليلاً مع التفاصيل التي لا يلم بها، ولكن روح ميتنك ومغامراته تبقي القارئ حتى نهاية الكتاب.
سأورد كمثال قصة طريفة أوردها ميتنك في بداية الكتاب، كيف أنه وأحد أصدقائه في فترة المراهقة قاموا، باختراق الموجة اللاسلكية لمطعم ماكدونالدز، مما جعلهم قادرين على استقبال طلبات الزبائن من خلال خدمة السيارات، وقد قاموا بعدد من المقالب، كان من أطرفها أنهم كانوا يقولون للعميل حال وصوله أنهم يقدمون اليوم عصير تفاح مجاني، والعميل بالطبع يوافق على الحصول عليه، عندها كانوا يقومون بتشغيل تسجيل لصوت شخص يتبول في كأس، بعدها كانوا يقولون للعميل: تفضل عصيرك جاهز :)
February 1, 2017
Very simply, this is the best book I've ever read in my whole life. Nothing describes it less than amazing. I haven't finishing reading it yet, not even half the way of it, but still, when you read it, you feel that you cannot stop reading. If you decided that a certain page is the last page you'll read for today, you'll find yourself unconsciously turning over the next page. You quickly become addicted to this book!
You value, and appreciate the fact why Kevin was - and according to me, he is still - the #1 hacker/security professional in the world through the acute experiences he went into, and how he intelligently handled them.
Hacking is curiosity. As you get into it. You trace your intuition and you have your intuition tracing you back to delve, dig dipper into things, and hack them. Hacking will, in most cases, teach you the whole fundamentals you need from programming and best practices, algorithms, operating systems' internals and the list follows. This is a brief of what Kevin went into. He was learning gradually, and progressively, but not learning in its abstract sense. But rather, the curiosity that was increasing and pushing him to hack more and solidify his technical knowledge.
His story is narrated with adequate details, that you can simply extract (or save) the techniques, methods, and stuff he uses/d in order to go ahead and expand in learning them (That's what I simply do).
If you came across a definition or such which you don't know, don't be content with getting the meaning only, a simple technique is to google it, pick the Wikipedia page of it, and read it fully; I believe this is how you start to learn.
If you do so, you'll be automatically equipping yourself with the fundamental weapons in computers and tech in general, network, telecoms, even programming, that pave the way for you to become a security professional.
In short, I highly recommend this book.
You value, and appreciate the fact why Kevin was - and according to me, he is still - the #1 hacker/security professional in the world through the acute experiences he went into, and how he intelligently handled them.
Hacking is curiosity. As you get into it. You trace your intuition and you have your intuition tracing you back to delve, dig dipper into things, and hack them. Hacking will, in most cases, teach you the whole fundamentals you need from programming and best practices, algorithms, operating systems' internals and the list follows. This is a brief of what Kevin went into. He was learning gradually, and progressively, but not learning in its abstract sense. But rather, the curiosity that was increasing and pushing him to hack more and solidify his technical knowledge.
His story is narrated with adequate details, that you can simply extract (or save) the techniques, methods, and stuff he uses/d in order to go ahead and expand in learning them (That's what I simply do).
If you came across a definition or such which you don't know, don't be content with getting the meaning only, a simple technique is to google it, pick the Wikipedia page of it, and read it fully; I believe this is how you start to learn.
If you do so, you'll be automatically equipping yourself with the fundamental weapons in computers and tech in general, network, telecoms, even programming, that pave the way for you to become a security professional.
In short, I highly recommend this book.
October 18, 2011
Let's start with the good: This book is well written, entertaining, and nicely paced. It's a brisk read, and you won't put it down. Very interesting look into the computer world of the 80's and 90's. Clearly the writer is incredibly smart and has led an exciting life. 3 stars for that.
All of these good aspects put the worst part of the book in sharp relief: Mitnick is a sociopath. I'd sooner read the sympathetic diaries of John Wayne Gacy than revisit Mr. Mitnick. On top of which he spends most of the book trying to convince you, the innocent reader, that he is the put-upon party - that he is the victim of friends and the law and the system. There's even a chapter entitled "I'm a scapegoat", which, if you can elicit any empathy for his victims, makes it all the more galling that he categorically rejects that anyone could have been hurt by this con artist. (Also, he seems to get the definition of scapegoat wrong. Don't worry - in this chapter of mixed metaphors, he also compares himself to a wizard.) He preyed on people's best intentions, trust and goodwill. So -2 stars for being an autobiography of someone I'm saddened to know exists.
If I can recommend it to anyone, I'd recommend it to people who are interested in a non-fiction example of the "unreliable narrator". In that aspect it's fantastic. The challenge is reading through the book and trying to determine what other people might have felt while he cheated them. It would have made a great work of fiction, if only.
(Commence hacking into my bank account in 3, 2, ...)
All of these good aspects put the worst part of the book in sharp relief: Mitnick is a sociopath. I'd sooner read the sympathetic diaries of John Wayne Gacy than revisit Mr. Mitnick. On top of which he spends most of the book trying to convince you, the innocent reader, that he is the put-upon party - that he is the victim of friends and the law and the system. There's even a chapter entitled "I'm a scapegoat", which, if you can elicit any empathy for his victims, makes it all the more galling that he categorically rejects that anyone could have been hurt by this con artist. (Also, he seems to get the definition of scapegoat wrong. Don't worry - in this chapter of mixed metaphors, he also compares himself to a wizard.) He preyed on people's best intentions, trust and goodwill. So -2 stars for being an autobiography of someone I'm saddened to know exists.
If I can recommend it to anyone, I'd recommend it to people who are interested in a non-fiction example of the "unreliable narrator". In that aspect it's fantastic. The challenge is reading through the book and trying to determine what other people might have felt while he cheated them. It would have made a great work of fiction, if only.
(Commence hacking into my bank account in 3, 2, ...)
July 24, 2023
This book was fantastic. I'm ten years younger than the subject but even with my Commodore 64 age 9-15 WAY pre-World Wide Web my friend and I were on our hot 300-2400 baud modems calling all over the world to swap games & interact on BBSs local and foreign.
We were self taught and had written software to call AT&T all day while we were at school that called 1-800-DIAL-ATT to randomly try the whatever digit calling card number.
Invariably we'd return home to 3 or more numbers logged that worked. Our parents had literally zero understanding of what we were doing, hell, WE barely understood the things we were doing. I think it really felt like open season and there were clearly way better hackers with seemingly malicious motives.
We were just curious kids dipping our toes into the big world at a time it took 8 hours to share one game of any quality over those taxed phone lines, hopefully with a clean enough line to not screw up a single bit or byte. Watching the live, realtime buffer on our 40 column screens until it was time to close it and save it to disk.
Then it was time to see if it worked. But we really didn't care: the fun was in the challenge & comradeship.
I totally buy Kevin's do no harm plea. Curious kids trying to understand their world better the way we did everything else: climbing the tree, fixing the lawnmower, how to crash our bikes in the least painful way!
Give this a read.
We were self taught and had written software to call AT&T all day while we were at school that called 1-800-DIAL-ATT to randomly try the whatever digit calling card number.
Invariably we'd return home to 3 or more numbers logged that worked. Our parents had literally zero understanding of what we were doing, hell, WE barely understood the things we were doing. I think it really felt like open season and there were clearly way better hackers with seemingly malicious motives.
We were just curious kids dipping our toes into the big world at a time it took 8 hours to share one game of any quality over those taxed phone lines, hopefully with a clean enough line to not screw up a single bit or byte. Watching the live, realtime buffer on our 40 column screens until it was time to close it and save it to disk.
Then it was time to see if it worked. But we really didn't care: the fun was in the challenge & comradeship.
I totally buy Kevin's do no harm plea. Curious kids trying to understand their world better the way we did everything else: climbing the tree, fixing the lawnmower, how to crash our bikes in the least painful way!
Give this a read.
September 14, 2011
Well, I try to think of myself as a smart guy. I try. But there are plenty of areas where I am not. Computer stuff especially. Thus, I am very impressed by this story. The guy that wrote it is a computer hacker and a sophisticated one. I guess at one point he was on the cover of Newsweek magazine with his face super-imposed over Darth Vader's head, and was maybe the most wanted guy in the country. He is a huge nerd, very arrogant until he gets caught, which he does a lot. Then he breaks down and cries and calls his mother. Literally. Every time breaks down and cries and calls his mom. One time he ditches his elderly, senile grandma to run in fear and save his own ass. Also kind of funny every time the law is after him he is like "Why are they after me? Poor me? This is crazy! All I did was break into Bank of America!" One of the more interesting combos of huge balls and running I have ever heard of, though who can blame a man for running from the law. Anybody would. Anyway, he is brilliant and despite being deeply bored by a lot of the technical talk (because I don't understand it) this was a great read.
July 6, 2013
The autobiography of Kevin Mitnick, the world's most wanted hacker. He relates how he became a hacker, his run in with the law, the cat and mouse cyber games while he was on the run from the FBI and the circumstances around his eventual capture and subsequent release.
I'm not that much into biographies but I gave this a go as a group read. It had some interesting elements but overall the subject matter didn't interest me. I think it would appeal to people like software engineers and other hackers maybe or maybe computer geeks in general.
2 stars is probably a little harsh because I know there are people who would be really interested in Kevin's "exploits" which involved a lot of hacking into phone companies and computer systems via a combination of social engineering and computer know how. I found it a little repetitive at times as we go from how he hacked into one system after another after another. It was interesting how he hacked in to monitor the FBI guys that were monitoring him even subverting there phone systems to field calls coming from other FBI agents.
The audio narrator Ray Porter did an OK job. Good enough to keep me listening anyway.
2.5 stars
I'm not that much into biographies but I gave this a go as a group read. It had some interesting elements but overall the subject matter didn't interest me. I think it would appeal to people like software engineers and other hackers maybe or maybe computer geeks in general.
2 stars is probably a little harsh because I know there are people who would be really interested in Kevin's "exploits" which involved a lot of hacking into phone companies and computer systems via a combination of social engineering and computer know how. I found it a little repetitive at times as we go from how he hacked into one system after another after another. It was interesting how he hacked in to monitor the FBI guys that were monitoring him even subverting there phone systems to field calls coming from other FBI agents.
The audio narrator Ray Porter did an OK job. Good enough to keep me listening anyway.
2.5 stars
October 7, 2018
I loved it. As a nerdy kid Kevin Mitnick was surrounded in mystery; I idolized his crazy exploits even though many of them he refuted in the book. However, he detailed several more, crazier exploits in this book. Worth it!
Reads like a fast-paced mystery thriller cop chase novel with insane levels of meta-deception. A great read for anyone geeky and nerdy.
Reads like a fast-paced mystery thriller cop chase novel with insane levels of meta-deception. A great read for anyone geeky and nerdy.
July 13, 2023
Not as interesting as I thought it'd be. It is er...boring.
June 10, 2022
Amazing book! Really interesting story about a computer hacker in the 80's and 90's who used social engineering and the phone system to hack some of the biggest companies in the world at the time. This was a riveting book from page one. If you enjoyed Catch Me if You Can then you will also like this book!
Displaying 1 - 30 of 1,943 reviews