What do you think?
Rate this book
Kuckucksei
Das Kuckucksei, eines unserer auserkorenen Lieblingsbücher, hat eine ganze Reihe von Titeln nach sich gezogen, in denen Jagd auf Computerkriminelle gemacht wird. Doch selbst Jahre nach der Erstausgabe von Kuckucksei und vielen Nachahmungen, ist das Buch mit seiner packenden Handlung und seinem kritischen Blickwinkel immer noch guter Lesestoff. Clifford Stoll wird eher unfreiwillig zur Einmann-Sicherheitskraft als er versucht, einige gesichtslose Kriminelle aufzuspüren, die in die Universitätsrechner eindringen, die er verwaltet. Was zunächst aussieht wie ein kleiner Fehler in einem Computer-Logfile, führt schließlich dank Stolls Ausdauer und intellektueller Hartnäckigkeit zur Entdeckung eines Industriespionagerings.
Ist dies ein Buch über Computernetzwerke? Ein Spionageroman? Oder ist dieses Buch der wahre Bericht, wie Clifford Stoll, heute eine Netzlegende, im Jahr 1989 Markus Hess und den Chaos Computer Club zur Strecke brachte? Stoll war Astronom und Systemadministrator am Lawrence Berkeley Labor, als ihn ein scheinbar ganz normaler Buchhaltungsfehler einfach nicht mehr losließ -- wer war der unbefugte Benutzer in seinem System? Stoll drehte den Spieß gegenüber den Spionen in seinen Computern um und brachte eine internationale Suche ins Rollen, an der sich schließlich das FBI, der CIA und die Deutsche Bundespost beteiligten und versuchten, die Hacker aufzuspüren. Die Geschichte ist immer noch so frisch und faszinierend wie damals. Mehr als das: Sie macht viel Spaß.
457 pages, Paperback
First published January 1, 1989
1009 people are currently reading
23471 people want to read
About the author
Clifford Stoll
3 books108 followersClifford Paul "Cliff" Stoll is an astronomer, author and teacher. He is best known for his investigation in 1986, while working as a systems administrator at the Lawrence Berkeley National Laboratory, that led to the capture of hacker Markus Hess, and for Stoll's subsequent book The Cuckoo's Egg, in which he details the investigation.
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 30 of 1,350 reviews
September 10, 2012
I really enjoyed this book. Loved the references to Berkeley, the hacker chase, but most interestingly, it takes you back to an earlier time in computing (in 1989)- which I thought was a fascinating reminder of what things were like. For example, I love the explanation of 'electronic mail.' At this point, I think most people have forgotten what the 'e' in email stands for.
Also, a favorite passage, as he explains what the "Internet" is:
100,000 computers! Just for comparison, I did a quick search. Analysts predict there to be more mobile devices connected to the Internet then humans alive in 2016 - that's more than 7.6 billion mobile devices - that doesn't include desktop and laptop computers. (source: Cisco VNI Index). Wonder what it will be like in another 20 years?
The story is also fascinating. Shows how one guy in a computer lab in Berkeley was able to track down a ring of international hackers and awaken some of the US top security agencies to the dawn of a new form of espionage. It was amazing how lax computer security was before this - and how it took an incident like this to awaken these agencies to the threat of cyber espionage.
Only reason it gets 4 instead of 5 starts is that while the beginning and end are very interesting, about mid-book it starts to get pretty repetitive. E.g.
Overall, really liked it. I think you need to be a bit of a computer geek to enjoy this one. But would definitely recommend to anyone who wants to reminisce a bit who enjoys a good spy chase laden with UNIX commands.
Also, a favorite passage, as he explains what the "Internet" is:
"At first, DARPA's network [the Internet] was simply a testbed to prove computers could be linked together. Since it was seen as an unreliable experiment, universities and laboratories used it, and main stream military people ignored it. After eight years, only a few hundred computers were connected into the Arpanet, but gradually, others were attracted by the network's reliability and simplicity. By 1985 the network directory listed tens of thousands of computers; today, there must be over one hundred thousand."
100,000 computers! Just for comparison, I did a quick search. Analysts predict there to be more mobile devices connected to the Internet then humans alive in 2016 - that's more than 7.6 billion mobile devices - that doesn't include desktop and laptop computers. (source: Cisco VNI Index). Wonder what it will be like in another 20 years?
The story is also fascinating. Shows how one guy in a computer lab in Berkeley was able to track down a ring of international hackers and awaken some of the US top security agencies to the dawn of a new form of espionage. It was amazing how lax computer security was before this - and how it took an incident like this to awaken these agencies to the threat of cyber espionage.
Only reason it gets 4 instead of 5 starts is that while the beginning and end are very interesting, about mid-book it starts to get pretty repetitive. E.g.
Overall, really liked it. I think you need to be a bit of a computer geek to enjoy this one. But would definitely recommend to anyone who wants to reminisce a bit who enjoys a good spy chase laden with UNIX commands.
February 17, 2025
I read this in 1994. I'd met my first boyfriend who worked as a database administrator. I had just started working as an IT consultant (really had NO clue what that meant until I actually got on the job - only got this job because of a college alumna who took pity on me). I graduated with a double liberal arts major. All my peers came in with more practical majors, like MIS (what we used to call IT - management information systems), accounting, programming, and business. I had no idea what anything meant in my new job. This book helped me pull a lot together. It was exciting to connect a lot of dots (finally) and to understand a lot of what was expected of me.
It was also extra fun for me to read because it was my first thriller - until then, I'd only ever read classics, both as part of my major and because of what seemed appropriately accessible to me at the public library. I was hooked from then onwards.
I reread it decades later. It was fun to see all the changes in technology since then. My rating is based on my first reading.
It was also extra fun for me to read because it was my first thriller - until then, I'd only ever read classics, both as part of my major and because of what seemed appropriately accessible to me at the public library. I was hooked from then onwards.
I reread it decades later. It was fun to see all the changes in technology since then. My rating is based on my first reading.
March 19, 2008
I read this book first around sixth grade and again last month. It was wicked good the first time and so-so the second time. I think as I've gotten older and wiser and more discerning, and as technology has progressed, this book hasn't aged well.
Here's the synop: Cliff Stoll is an astrophysicist who knows just a little something about computers (obviously a lot). He's living at UC Berkeley in the early days of the internets. One day he discovers a 75 cent accounting error (this is back before AOL charged you by the minute), and kablammo! he's discovered a hacker. Now all he needs to do is catch him...
When I read this at 12 going on 13, this book seemed like a bleeding edge thrill-a-minute technological game of cat and cuckoo. And now, at 26 going on 27, it's still kinda neat. Cliff is obviously a brilliant guy, and he does really well in 1) explaining his maneuvers to keep the hacker at bay and 2) downplaying how smart he was. What annoyed me was all the personal stuff in this book and how intrusive it is. I don't care about Cliff the person. I want to read about Cliff the cyber-battler, the Cliffinator sent back from 2008 to 1986 to battle the West German hacker Markus Hess. Or simply Cliff the research paper.
Here's the personal shit I don't like: Cliff's a hippie cliche who hates the government, wears tie-dye, likes the Dead, and lives and works in Berkeley. His girlfriend/fiancee is built like a sumo wrestler (this is subtly alluded to). Her old college roommate is a butch lesbian who hates the government. Their present roommate is a violinist who's always brining home a new crazy man.
Cliff's sooo frustrated that no government agency will help him. Why won't they help him?! And what about the future of the internet, and the need for open networks to foster scientific intercourse and shit like that?? Waaaa, waaaa, why don't you cry about it, you big hippie baby?
OK, so I'm being hard on Cliff and his wacky teammates in life. What can I say, though? They're all boring. Cliff and his entire life is boring. Except for the hunt. So Cliff, focus on the hunt.
If you've made it this far through this self-indulgent review, you might wonder why I gave this book 4 stars. I'll tell you why: I loved it the first time, and the second time, last month, was still pretty good. Cliff Stoll - he can keep you up at night past your bedtime. His book's good in bed.
Here's the synop: Cliff Stoll is an astrophysicist who knows just a little something about computers (obviously a lot). He's living at UC Berkeley in the early days of the internets. One day he discovers a 75 cent accounting error (this is back before AOL charged you by the minute), and kablammo! he's discovered a hacker. Now all he needs to do is catch him...
When I read this at 12 going on 13, this book seemed like a bleeding edge thrill-a-minute technological game of cat and cuckoo. And now, at 26 going on 27, it's still kinda neat. Cliff is obviously a brilliant guy, and he does really well in 1) explaining his maneuvers to keep the hacker at bay and 2) downplaying how smart he was. What annoyed me was all the personal stuff in this book and how intrusive it is. I don't care about Cliff the person. I want to read about Cliff the cyber-battler, the Cliffinator sent back from 2008 to 1986 to battle the West German hacker Markus Hess. Or simply Cliff the research paper.
Here's the personal shit I don't like: Cliff's a hippie cliche who hates the government, wears tie-dye, likes the Dead, and lives and works in Berkeley. His girlfriend/fiancee is built like a sumo wrestler (this is subtly alluded to). Her old college roommate is a butch lesbian who hates the government. Their present roommate is a violinist who's always brining home a new crazy man.
Cliff's sooo frustrated that no government agency will help him. Why won't they help him?! And what about the future of the internet, and the need for open networks to foster scientific intercourse and shit like that?? Waaaa, waaaa, why don't you cry about it, you big hippie baby?
OK, so I'm being hard on Cliff and his wacky teammates in life. What can I say, though? They're all boring. Cliff and his entire life is boring. Except for the hunt. So Cliff, focus on the hunt.
If you've made it this far through this self-indulgent review, you might wonder why I gave this book 4 stars. I'll tell you why: I loved it the first time, and the second time, last month, was still pretty good. Cliff Stoll - he can keep you up at night past your bedtime. His book's good in bed.
December 9, 2016
Super fun book - the story of a sysadmin chasing a hacker during the early internet, but it reads almost like a thriller - fun and fast.
I think I learned more about the early internet from this book than anything I've ever read before. I had heard of the words Arpanet and Milnet, but really didn't know what they were - simple networks of computers. And apparently, with very poor security! Impressive how easy it was for the hacker to get root access back then.
Internet security has come a long ways since those days (and has a very long way to go) - but you can really get a sense of how it started and where it's going by reading this.
I think I learned more about the early internet from this book than anything I've ever read before. I had heard of the words Arpanet and Milnet, but really didn't know what they were - simple networks of computers. And apparently, with very poor security! Impressive how easy it was for the hacker to get root access back then.
Internet security has come a long ways since those days (and has a very long way to go) - but you can really get a sense of how it started and where it's going by reading this.
January 3, 2014
Interesting book, especially since I worked at MITRE at the time, and had first-hand knowledge of the method the hacker used to go through the systems. Also met him at a security conference -- he gave a nice presentation.
March 17, 2011
(5.0) So much fun! (may need to be a little computer-geeky to really love it)
Crazy cool true story about an astronomer-turned-sysadmin at Berkeley in the 1980s who decides to track down a 75 cent accounting discrepancy in server usage, and turns into a year-long hunt to track down a sneaky computer spy operating for the KGB. Covers several severe holes in Unix security, but emphasizes that the weakest link in security is almost always from human operators.
Very engaging read, tore right through it. It almost reads like a mystery, detective or spy novel, but it's so much more exciting because it's all true. Told by Cliff Stoll, the self-appointed cybersecurity guard who was investigated the discrepancy and eventually tracked the spy/hacker. He got little/no help from many law enforcement agencies who owe him a huge debt of gratitude. Really appreciated hearing his thought process, his approach and reaction to what found.
I recommend this to almost every computer geek I meet or hire (or try to). Strongly recommended and really wish I could read it again for the first time. :)
Crazy cool true story about an astronomer-turned-sysadmin at Berkeley in the 1980s who decides to track down a 75 cent accounting discrepancy in server usage, and turns into a year-long hunt to track down a sneaky computer spy operating for the KGB. Covers several severe holes in Unix security, but emphasizes that the weakest link in security is almost always from human operators.
Very engaging read, tore right through it. It almost reads like a mystery, detective or spy novel, but it's so much more exciting because it's all true. Told by Cliff Stoll, the self-appointed cybersecurity guard who was investigated the discrepancy and eventually tracked the spy/hacker. He got little/no help from many law enforcement agencies who owe him a huge debt of gratitude. Really appreciated hearing his thought process, his approach and reaction to what found.
I recommend this to almost every computer geek I meet or hire (or try to). Strongly recommended and really wish I could read it again for the first time. :)
July 24, 2012
Great book. The FBI was incredibly frustrating to read about. Not many people would have been persistent enough to stick with this. I'm impressed with how diligently the author worked to track this guy down.
One small gripe though - the author seemed way too self conscious about his political identity add a result of cooperating with the guys in suits. Was he trying to spin it as an internal struggle between who he was, and who this experience made him become? Not buying it, Cliff.
One small gripe though - the author seemed way too self conscious about his political identity add a result of cooperating with the guys in suits. Was he trying to spin it as an internal struggle between who he was, and who this experience made him become? Not buying it, Cliff.
July 22, 2021
update on the author....
https://alumni.berkeley.edu/californi...
https://alumni.berkeley.edu/californi...
August 31, 2008
The first "infosec true crime" book I ever read, and thus possibly a major influence on my life's work to this point (although surely not so much as WarGames). It's not as good as Sterling's The Hacker Crackdown, but better than most anything else along these lines. Cliff Stoll, astronomer-turned-network-monitor, is still around (last I checked, writing the abominable Silicon Valley Snake Oil), but let's be honest: he was never a computer scientist at heart, ignored decade's-old methods in this hunt for DDR-borne hackers (Bro, widely regarded as the world's first IDS, had been developed and published as early as 1980 by Denning and the InfoSec group at LBNL), and filled this book up with pants-wetting ramblings about "whether to help the Feds". Worth reading for its insights into the early period of academic/industrial internetworking and the fact that it's referenced everywhere.
August 8, 2016
Update August 2016: Here's an amazing video of the author showing off his self-built warehouse of Klein bottles including self-built trash warehouse robot
I've seen this book pop up a few times on lists like "recommended reads for programmers" and always wondered why - I didn't know it was such a extremely fascinating read! I tried to read it in one evening but had to stop at 4am.
It's the story of how one US astronomer turned computer programmer ("astroinformatician"?) found a 75 cents bill for computing time he couldn't make sense of, how he traced that bill, found an intruder on his system, and how it took him months to untangle the web of systems the hacker used to disguise himself.
Stoll had a very interesting scientific way in which he approached the problem of an intruder, which resonated with me strongly: he kept neat lab-books of everything that happened, he thought clearly about each step, and all the little details they used to infer more about the hacker are splendid.
For example, on login the hacker kept on using "ps -eafg" to see who was logged in, but "-f" was superfluous under Berkeley Unix, which indicated that the hacker was used to AT&T Unix, which wasn't used on the US West Coast. Therefore it was more likely that the intruder was from the US East Coast, or from abroad.
(Another fun thing about the age of this book - it's clearly written for the layman in 1989, so things that are completely basic today are explained in long terms - "electronic mail", for example)
It becomes a fun cat and mouse game - it's always the same intruder (who turned out to be ), Stoll tried to get the US government involved, but no agency wanted to have anything to do with it - neither the FBI, nor the CIA, nor the NSA had anything to do with computer break-ins, there were no laws yet, nothing (the events in this book happen around 1986-87, I was just a few months old).
It's great fun to read how each step in the plan worked out, how Stoll laid traps, each step in his thinking is detailed (the joys of writing everything down!).
You'll especially love this if you (like me) grew up fascinated with German "hacker culture" of the late 80s, early 90s, back when the Chaos Computer Club started to become a name. I got the biggest smile from this little dialogue:
I'm pretty sure every German "computer person" knows who hagbard was. We've all seen the movie "23", and if you haven't, you greatly owe it to yourself, it's one of my favorite German movies (even Robert Anton Wilson, who co-wrote "Illuminatus!", has a small part playing himself). It portrays the KGB hacks from hagbard alias Karl Koch and his friends, which is closely connected to the story of this book, but the movie focuses on Koch, while the book focuses on the systems Hess broke in. I guess focusing on Koch made for a more interesting story - he had a relatively large cocaine habit, and he was found burned to death, with no suicide note.
Stoll didn't like the CCC at all - in the book he repeatedly calls them vandals, I guess because back then, it was just a couple of kids messing around, not particularly knowing what they were doing. Nowadays the CCC advises the German government on technical security matters. The Chaos Communication Congress is one of the best and biggest technology conferences in Germany (I'm proud that I once held a little talk there at an ungodly hour together with Bastian Greshake/@gedankenstuecke).
Another interesting side-note is that some currently very famous "computer people" appear shortly - such as Paul Graham and Robert T. Morris, who have since then founded several companies and are now known for ycombinator, one of the biggest Internet startup seed funding companies (possible more for ycombinator's social news site, Hacker News)
If you want to read a more technical side of this, Stoll first published a paper: Stalking The Wily Hacker.
I wonder how much the events in this book, and the book itself, made Snowden's revelations possible... Would the NSA ever have started to try and control the entire Internet if the Soviet Union had never started to pay hackers for information?
Recommended for: Computer people, those interested in the history of the Internet, those who enjoyed playing Uplink
Not recommended for: People who want to think that the Internet is Facebook
I've seen this book pop up a few times on lists like "recommended reads for programmers" and always wondered why - I didn't know it was such a extremely fascinating read! I tried to read it in one evening but had to stop at 4am.
It's the story of how one US astronomer turned computer programmer ("astroinformatician"?) found a 75 cents bill for computing time he couldn't make sense of, how he traced that bill, found an intruder on his system, and how it took him months to untangle the web of systems the hacker used to disguise himself.
Stoll had a very interesting scientific way in which he approached the problem of an intruder, which resonated with me strongly: he kept neat lab-books of everything that happened, he thought clearly about each step, and all the little details they used to infer more about the hacker are splendid.
For example, on login the hacker kept on using "ps -eafg" to see who was logged in, but "-f" was superfluous under Berkeley Unix, which indicated that the hacker was used to AT&T Unix, which wasn't used on the US West Coast. Therefore it was more likely that the intruder was from the US East Coast, or from abroad.
(Another fun thing about the age of this book - it's clearly written for the layman in 1989, so things that are completely basic today are explained in long terms - "electronic mail", for example)
It becomes a fun cat and mouse game - it's always the same intruder (who turned out to be ), Stoll tried to get the US government involved, but no agency wanted to have anything to do with it - neither the FBI, nor the CIA, nor the NSA had anything to do with computer break-ins, there were no laws yet, nothing (the events in this book happen around 1986-87, I was just a few months old).
It's great fun to read how each step in the plan worked out, how Stoll laid traps, each step in his thinking is detailed (the joys of writing everything down!).
You'll especially love this if you (like me) grew up fascinated with German "hacker culture" of the late 80s, early 90s, back when the Chaos Computer Club started to become a name. I got the biggest smile from this little dialogue:
"Can you identify who's breaking in?"
"One guy uses the pseudonym Hagbard. Another, Pengo."
I'm pretty sure every German "computer person" knows who hagbard was. We've all seen the movie "23", and if you haven't, you greatly owe it to yourself, it's one of my favorite German movies (even Robert Anton Wilson, who co-wrote "Illuminatus!", has a small part playing himself). It portrays the KGB hacks from hagbard alias Karl Koch and his friends, which is closely connected to the story of this book, but the movie focuses on Koch, while the book focuses on the systems Hess broke in. I guess focusing on Koch made for a more interesting story - he had a relatively large cocaine habit, and he was found burned to death, with no suicide note.
Stoll didn't like the CCC at all - in the book he repeatedly calls them vandals, I guess because back then, it was just a couple of kids messing around, not particularly knowing what they were doing. Nowadays the CCC advises the German government on technical security matters. The Chaos Communication Congress is one of the best and biggest technology conferences in Germany (I'm proud that I once held a little talk there at an ungodly hour together with Bastian Greshake/@gedankenstuecke).
Another interesting side-note is that some currently very famous "computer people" appear shortly - such as Paul Graham and Robert T. Morris, who have since then founded several companies and are now known for ycombinator, one of the biggest Internet startup seed funding companies (possible more for ycombinator's social news site, Hacker News)
If you want to read a more technical side of this, Stoll first published a paper: Stalking The Wily Hacker.
I wonder how much the events in this book, and the book itself, made Snowden's revelations possible... Would the NSA ever have started to try and control the entire Internet if the Soviet Union had never started to pay hackers for information?
Recommended for: Computer people, those interested in the history of the Internet, those who enjoyed playing Uplink
Not recommended for: People who want to think that the Internet is Facebook
August 1, 2016
Executive Summary: A truly excellent and fascinating tale of hacking in the early days of the internet.
Full Review
I'm fascinated with computer crime. I have for as long as I can remember being interested in computers. Somehow I had never managed to read this book.
I'm glad I finally got around to it. It might be my new favorite. Cliff Stoll tells an engaging and personal story of his discovery of computer networks, security exploits and computer crime that reads more like a spy novel than a technical manual.
I think Mr. Stoll does a good job of making things easy to understand for the non-technical person. It has just enough detail to follow the story without being overwhelming. Of course being a computer person myself, I may not be the best to judge how technical this book gets.
This book overlaps with some other stories of computer crime I've read and re-sparked my interest in reading some others I have on my backlog, along with rereading one I read back in high school that seems to overlap with this one a bit.
It's hard for me to judge how non-techies will enjoy this book, but anyone who wants to see what things were like in the early days of the internet should find this fascinating.
The most remarkable thing was how little the various law enforcement agencies seemed to care. It was really the wild-wild west of computer crime. To the FBI, unless they physically stole something, destroyed something or cost your millions of dollars, it wasn't worth pursuing.
How do you quantify computer time? Especially back then when computers weren't affordable and resources were limited. What about the time Cliff Stoll spend tracking the hacker? Time he should have spent doing his job. Everyone wanted him to keep at, and to keep them in the loop, but no one was willing to do anything about it, or cough up funds to support him.
It would take a few more years and some bigger crimes to finally wake them up and change how computer crime ranked in importance. Then again, most people are inundated with malware, spyware, viruses, scams and phishing emails on an almost daily basis. So in some ways it feels like nothing has really changed. You're not going to call the FBI because someone tried to steal your password.
Computer crime is big business these days, and if you want to see how it was in the early days, this is a must read.
Full Review
I'm fascinated with computer crime. I have for as long as I can remember being interested in computers. Somehow I had never managed to read this book.
I'm glad I finally got around to it. It might be my new favorite. Cliff Stoll tells an engaging and personal story of his discovery of computer networks, security exploits and computer crime that reads more like a spy novel than a technical manual.
I think Mr. Stoll does a good job of making things easy to understand for the non-technical person. It has just enough detail to follow the story without being overwhelming. Of course being a computer person myself, I may not be the best to judge how technical this book gets.
This book overlaps with some other stories of computer crime I've read and re-sparked my interest in reading some others I have on my backlog, along with rereading one I read back in high school that seems to overlap with this one a bit.
It's hard for me to judge how non-techies will enjoy this book, but anyone who wants to see what things were like in the early days of the internet should find this fascinating.
The most remarkable thing was how little the various law enforcement agencies seemed to care. It was really the wild-wild west of computer crime. To the FBI, unless they physically stole something, destroyed something or cost your millions of dollars, it wasn't worth pursuing.
How do you quantify computer time? Especially back then when computers weren't affordable and resources were limited. What about the time Cliff Stoll spend tracking the hacker? Time he should have spent doing his job. Everyone wanted him to keep at, and to keep them in the loop, but no one was willing to do anything about it, or cough up funds to support him.
It would take a few more years and some bigger crimes to finally wake them up and change how computer crime ranked in importance. Then again, most people are inundated with malware, spyware, viruses, scams and phishing emails on an almost daily basis. So in some ways it feels like nothing has really changed. You're not going to call the FBI because someone tried to steal your password.
Computer crime is big business these days, and if you want to see how it was in the early days, this is a must read.
June 22, 2018
The Cuckoo's Egg" by Clifford Stoll was fascinating the first time I read it in 1989, and when I saw it on one of the “books to read” lists on Goodreads, I eagerly reexamined it. It is still compelling today, just in a different manner. The technology has changed, but the crime and the chase have remained the same. The incredibly cat and mouse chase through what was then just the beginnings of the internet still kept me on the edge of my seat, remembering dial-up, dot matrix printers, and long distance phone bills.
In the end, “The Cuckoo’s Egg” is computer hacking at its beginning, and it serves to remind us of the benefits and detriments of a cyber-dependent society. Today, internet crime is rampant on so many levels and it still takes skilled and observant people to combat it.
Read and remember, and if you do not remember, read and learn.
In the end, “The Cuckoo’s Egg” is computer hacking at its beginning, and it serves to remind us of the benefits and detriments of a cyber-dependent society. Today, internet crime is rampant on so many levels and it still takes skilled and observant people to combat it.
Read and remember, and if you do not remember, read and learn.
September 13, 2018
Excellent book about hackers and computer security told in a way that you do NOT have to be a geek to understand. Amazing that so much has changed since the early 80's in terms of technology, yet the tactics for both hackers and security are fundamentally unchanged.
This book is told as a humorous narrative of Cliff's life helping track down a computer hacker. Being an astronomer working at Berkley, and being a self-described "left wing nut", he ends up brushing shoulders with the FBI, CIA, NSA, and other "three-letter agencies" on a common mission to track down and lock out a hacker.
I debated between 4 and 5 stars. My dilemma is that while it's not dry by any means, it did get a little long-winded in the middle and I switched and read another book in the meantime to get a break before coming back to finish. Well worth the read, though, and I've started other people (who are not computer geeks) reading it as well who seem to be thoroughly enjoying it. For this reason, I'm leaving it at 5 stars.
This book is told as a humorous narrative of Cliff's life helping track down a computer hacker. Being an astronomer working at Berkley, and being a self-described "left wing nut", he ends up brushing shoulders with the FBI, CIA, NSA, and other "three-letter agencies" on a common mission to track down and lock out a hacker.
I debated between 4 and 5 stars. My dilemma is that while it's not dry by any means, it did get a little long-winded in the middle and I switched and read another book in the meantime to get a break before coming back to finish. Well worth the read, though, and I've started other people (who are not computer geeks) reading it as well who seem to be thoroughly enjoying it. For this reason, I'm leaving it at 5 stars.
July 22, 2021
I read this back in the 1990s, I believe. I remember enjoying it a lot more than I expected, but I was a computer programmer and there weren't many books like this back then.
The author is a true Berkeleyite, smart and a little crazy. He was an astronomer doing something like making lenses for the well known Lawrence Labs, a high-tech haven. Now, he makes bottles that don't hold anything and are of interest mainly to mathematical nerds, etc. He pretty much lived in his own world, but for a while, he was pulled out into a stint of international intrigue involving all the 3-letter agencies around then - the FBI, CIA, NSA, etc.
Michael Perkins posted a link to an article about the author that was interesting and tells a bit about the book and his life: https://www.goodreads.com/review/show...
The author is a true Berkeleyite, smart and a little crazy. He was an astronomer doing something like making lenses for the well known Lawrence Labs, a high-tech haven. Now, he makes bottles that don't hold anything and are of interest mainly to mathematical nerds, etc. He pretty much lived in his own world, but for a while, he was pulled out into a stint of international intrigue involving all the 3-letter agencies around then - the FBI, CIA, NSA, etc.
Michael Perkins posted a link to an article about the author that was interesting and tells a bit about the book and his life: https://www.goodreads.com/review/show...
February 8, 2012
Cliff is an excellent storyteller and has done a great job sharing this true story. Perhaps too good of a job. Although it's consistently well-written, it is frustratingly slow at times. I don't hold that against him because it happens to be appropriate for conveying a hint of what he felt as he went through this. Like him, I kept feeling like there was a breakthrough or resolution just around the corner, only to find myself strung along to a longer road ahead.
As someone who's been through more than a fair share of dealing with hackers, spammers, buggy software, and poorly-designed hardware, I didn't need this story in book-length. Reading it was another chore caused by delinquent computer users (even if indirectly).
As someone who's been through more than a fair share of dealing with hackers, spammers, buggy software, and poorly-designed hardware, I didn't need this story in book-length. Reading it was another chore caused by delinquent computer users (even if indirectly).
October 2, 2008
Por razones laborales he estado revisando temas de seguridad informática, eso me llevó a releer un texto que escribí y publiqué en Revista Red hace como diez años. Los temas de seguridad han evolucionado y hoy estamos inmersos en temas muy interesantes de biometría para autenticación de usuarios, como platicaba hace unos días con mi amigo Enrique Daltabuit, experto nacional en el tema. Sin embargo el texto de hace diez años tiene vigencia en la medida en la que comenta un libro fascinante, uno de esos que se siente inmediata necesidad de compartir.
Se trata del libro de Cliff Stoll, The Cuckoo'segg, es decir El Huevo del Cuclillo, ese pájaro que los suizos han puesto a vivir dentro de sus relojes y que tiene el hábito de parasitar los nidos que construyen otras aves. No se si exista una traducción al español de este libro tan ilustrativo, pero sería una lástima que no fuera accesible a más personas.
Stoll era en 1986, año en el que inicia la historia, un estudiante graduado de astronomía en Berkeley, donde también administraba una de las computadoras del laboratorio Lawrence. A partir de una diferencia de 75 centavos de dólar en la contabilidad de la computadora, cifra que es pequeña, por más fluctuaciones de la moneda que haya, descubre que ha estado ocurriendo un acceso no autorizado a su máquina.
Ahí arranca una obsesiva, desesperada, desesperante y muy ingeniosa persecución del intruso a través del laberinto de conexiones entre las computadoras. La persecución se hará a través de líneas telefónicas locales, cables trasatlánticos, satélites y desde luego varios países en América, Europa y Asia.
El libro, construido con base en la bitácora que Stoll fue escribiendo conforme se desarrollaban los hechos, no es una novela, narra acontecimientos reales, pero su lectura es sumamente adictiva. Uno empieza a pasar página tras página con la angustia de querer saber qué va a ocurrir, en que momento y cómo será descubierto el intruso. Tampoco es un libro de texto pero enseña muchas cosas acerca de la seguridad en cómputo, quizás la más importante es que si bien no existen —y quizás no puedan existir— sistemas de cómputo seguros en 100 por ciento, en muchos casos el principal responsable de la falta de seguridad en una máquina es su administrador.
Muchas veces, quien se dedica a ingresar de manera subrepticia en computadoras a las que no tiene permitido el acceso puede hacerlo si conoce magistralmente las fortalezas y debilidades del software que se utiliza para adminsitrar la máquina, quien quiera evitárselo deberá hacerlo también usando el mismo software. Una especie de guerra de inteligencias se establece entonces, haciendo por eso tan atractivo el asunto. Sumemos a eso que los delitos computacionales pueden ser buen negocio e iremos entendiendo porque el ataque a los sistemas de cómputo se va volviendo un tema de nuestros días.
Esta lucha entre dos cerebros, que emula el placer del juego del ajedrez queda muy clara en el relato de Stoll. El intruso ha descubierto una debilidad en el editor de textos creado por Richard Stallman, Gnu-Emacs. La flaqueza consistía en que el programa permitía llevar archivos a las áreas protegidas de la computadora.
Cuando un equipo de cómputo es utilizado por varias personas, cada uno de ellos tiene distintos derechos. Cada uno puede leer y escribir en sus registros, pero no en los de los demás. El administrador del sistema tiene permisos especiales para colocar archivos en áreas protegidas para acceder a los archivos de todos los usuarios.
Valiéndose del Gnu Emacs el hacker de Stoll lograba colocar en un área privilegiada de la computadora un programa que le daba privilegios de super usuario, es decir de administrador del sistema, con posibilidades de crear o destruir cuentas de usuarios y leer archivos confidenciales. En una palabra se volvía dueño de la máquina.
Esta forma de convertirse en superusuario es la que da origen al título del libro: En palabras de Stoll: "El cuclillo pone sus huevos en los nidos de otros pájaros. Es un parásito de nidos... Nuestro misterioso visitante dejó un programa-huevo en nuestra computadora, permitiendo al sistema empollarlo y alimentarle privilegios".
Pero si el intruso tiene recursos para hacerse con la máquina, Stoll los tiene también para vigilarlo y rastrearlo. Lo observa desde una computadora en la que no puede ser detectado, conecta una impresora a la máquina para registrar cada teclazo que el intruso efectúa cuando está en sesión, construye software para hacer sonar una alarma cada vez que hay una introducción no autorizada. El soft¬ware da incluso, en clave Morse, la inicial de la letra de la clave del acceso no autorizado. Stoll duerme varias noches en la oficina a la espera del hacker, contacta a todas las oficinas de las tres letras, como él llama a la FBI, CIA, DOE, FCI, etc. que pueden intervenir en el caso. Avisa a los administradores de los sistemas, que están siendo vulnerados, de la presencia —muchas veces ignorada por ellos mismos— del hacker.
Algunos administradores reaccionan simplemente cerrando el hueco de sus sistemas, que había permitido el acceso del extraño. Stoll no lo hace; sabe que si eso no resuelve el problema, el fisgón encontraría otra ruta a través de otras máquinas para seguir espiando dentro de los sistemas militares de los Estados Unidos. Stoll decide dejar abierta la puerta de su computadora para que el intruso pase y poder saber que hace.
Cuando en alguna ocasión, el hacker, está obteniendo información indebida, Stoll que lo observa, produce con sus llaves corrientes espurias en las conexiones, para que el espía reciba caracteres ininteligibles en su máquinas. En muchos casos el hacker logra el ingreso a las computadoras mediante un tedioso procedimiento de ensayo y error. Hace la llamada para la conexión y cuando le preguntan nombre y clave en el sistema propone algunos obvios como Quest o Field y Service en las computadoras Vax.
Por increíble que parezca esto le funciona —por descuido de los administradores claro. Algunas veces visita 60 o más máquinas sin éxito y de pronto, ábrete sésamo, ingresa como superusuario. Stoll compara esto con andar deambulando por las calles, moviendo las perillas de las puertas para ver quien olvido echar llave.
Una vez dentro de alguna computadora, el espía coloca su programa-huevo, se vuelve superusuario, lee los archivos y ahí encuentra claves para otras computadoras o copia el archivo donde están las claves de los usuarios o siembra un programa que los lea en el momento en que se conectan.
Stoll que es un estudiante de Berkeley, recordemos que esta universidad es famosa además por la rebeldía de sus estudiantes, encuentra difícil hablar y colaborar con los agentes federales, pero lo hace por un profundo sentimiento de que el hacker está destruyendo lo más importante de las redes de computo: la posibilidad de comunicarse. Los hackers destruyen la confianza de las personas en los sistemas de cómputo y pueden llevarnos a aislar nuestros sistemas en busca de la seguridad.
Stoll logró localizar a su hacker y poner en perspectiva que la irrupción no autorizada en sistemas de cómputo no sólo es como un duelo de inteligencias, no es algo inocuo como el ajedrez, es una actividad que daña la confianza de los usuarios de las redes de cómputo.
Se trata del libro de Cliff Stoll, The Cuckoo'segg, es decir El Huevo del Cuclillo, ese pájaro que los suizos han puesto a vivir dentro de sus relojes y que tiene el hábito de parasitar los nidos que construyen otras aves. No se si exista una traducción al español de este libro tan ilustrativo, pero sería una lástima que no fuera accesible a más personas.
Stoll era en 1986, año en el que inicia la historia, un estudiante graduado de astronomía en Berkeley, donde también administraba una de las computadoras del laboratorio Lawrence. A partir de una diferencia de 75 centavos de dólar en la contabilidad de la computadora, cifra que es pequeña, por más fluctuaciones de la moneda que haya, descubre que ha estado ocurriendo un acceso no autorizado a su máquina.
Ahí arranca una obsesiva, desesperada, desesperante y muy ingeniosa persecución del intruso a través del laberinto de conexiones entre las computadoras. La persecución se hará a través de líneas telefónicas locales, cables trasatlánticos, satélites y desde luego varios países en América, Europa y Asia.
El libro, construido con base en la bitácora que Stoll fue escribiendo conforme se desarrollaban los hechos, no es una novela, narra acontecimientos reales, pero su lectura es sumamente adictiva. Uno empieza a pasar página tras página con la angustia de querer saber qué va a ocurrir, en que momento y cómo será descubierto el intruso. Tampoco es un libro de texto pero enseña muchas cosas acerca de la seguridad en cómputo, quizás la más importante es que si bien no existen —y quizás no puedan existir— sistemas de cómputo seguros en 100 por ciento, en muchos casos el principal responsable de la falta de seguridad en una máquina es su administrador.
Muchas veces, quien se dedica a ingresar de manera subrepticia en computadoras a las que no tiene permitido el acceso puede hacerlo si conoce magistralmente las fortalezas y debilidades del software que se utiliza para adminsitrar la máquina, quien quiera evitárselo deberá hacerlo también usando el mismo software. Una especie de guerra de inteligencias se establece entonces, haciendo por eso tan atractivo el asunto. Sumemos a eso que los delitos computacionales pueden ser buen negocio e iremos entendiendo porque el ataque a los sistemas de cómputo se va volviendo un tema de nuestros días.
Esta lucha entre dos cerebros, que emula el placer del juego del ajedrez queda muy clara en el relato de Stoll. El intruso ha descubierto una debilidad en el editor de textos creado por Richard Stallman, Gnu-Emacs. La flaqueza consistía en que el programa permitía llevar archivos a las áreas protegidas de la computadora.
Cuando un equipo de cómputo es utilizado por varias personas, cada uno de ellos tiene distintos derechos. Cada uno puede leer y escribir en sus registros, pero no en los de los demás. El administrador del sistema tiene permisos especiales para colocar archivos en áreas protegidas para acceder a los archivos de todos los usuarios.
Valiéndose del Gnu Emacs el hacker de Stoll lograba colocar en un área privilegiada de la computadora un programa que le daba privilegios de super usuario, es decir de administrador del sistema, con posibilidades de crear o destruir cuentas de usuarios y leer archivos confidenciales. En una palabra se volvía dueño de la máquina.
Esta forma de convertirse en superusuario es la que da origen al título del libro: En palabras de Stoll: "El cuclillo pone sus huevos en los nidos de otros pájaros. Es un parásito de nidos... Nuestro misterioso visitante dejó un programa-huevo en nuestra computadora, permitiendo al sistema empollarlo y alimentarle privilegios".
Pero si el intruso tiene recursos para hacerse con la máquina, Stoll los tiene también para vigilarlo y rastrearlo. Lo observa desde una computadora en la que no puede ser detectado, conecta una impresora a la máquina para registrar cada teclazo que el intruso efectúa cuando está en sesión, construye software para hacer sonar una alarma cada vez que hay una introducción no autorizada. El soft¬ware da incluso, en clave Morse, la inicial de la letra de la clave del acceso no autorizado. Stoll duerme varias noches en la oficina a la espera del hacker, contacta a todas las oficinas de las tres letras, como él llama a la FBI, CIA, DOE, FCI, etc. que pueden intervenir en el caso. Avisa a los administradores de los sistemas, que están siendo vulnerados, de la presencia —muchas veces ignorada por ellos mismos— del hacker.
Algunos administradores reaccionan simplemente cerrando el hueco de sus sistemas, que había permitido el acceso del extraño. Stoll no lo hace; sabe que si eso no resuelve el problema, el fisgón encontraría otra ruta a través de otras máquinas para seguir espiando dentro de los sistemas militares de los Estados Unidos. Stoll decide dejar abierta la puerta de su computadora para que el intruso pase y poder saber que hace.
Cuando en alguna ocasión, el hacker, está obteniendo información indebida, Stoll que lo observa, produce con sus llaves corrientes espurias en las conexiones, para que el espía reciba caracteres ininteligibles en su máquinas. En muchos casos el hacker logra el ingreso a las computadoras mediante un tedioso procedimiento de ensayo y error. Hace la llamada para la conexión y cuando le preguntan nombre y clave en el sistema propone algunos obvios como Quest o Field y Service en las computadoras Vax.
Por increíble que parezca esto le funciona —por descuido de los administradores claro. Algunas veces visita 60 o más máquinas sin éxito y de pronto, ábrete sésamo, ingresa como superusuario. Stoll compara esto con andar deambulando por las calles, moviendo las perillas de las puertas para ver quien olvido echar llave.
Una vez dentro de alguna computadora, el espía coloca su programa-huevo, se vuelve superusuario, lee los archivos y ahí encuentra claves para otras computadoras o copia el archivo donde están las claves de los usuarios o siembra un programa que los lea en el momento en que se conectan.
Stoll que es un estudiante de Berkeley, recordemos que esta universidad es famosa además por la rebeldía de sus estudiantes, encuentra difícil hablar y colaborar con los agentes federales, pero lo hace por un profundo sentimiento de que el hacker está destruyendo lo más importante de las redes de computo: la posibilidad de comunicarse. Los hackers destruyen la confianza de las personas en los sistemas de cómputo y pueden llevarnos a aislar nuestros sistemas en busca de la seguridad.
Stoll logró localizar a su hacker y poner en perspectiva que la irrupción no autorizada en sistemas de cómputo no sólo es como un duelo de inteligencias, no es algo inocuo como el ajedrez, es una actividad que daña la confianza de los usuarios de las redes de cómputo.
November 9, 2024
absolutely my favorite book of the year. I feel like AI generated a book of my interests. do I recommend it? if you like computers and berkeley, yes. if not, you'll probably find it tedious. but it was such a good spy novel and love letter to his wife. perfection, no notes. thank you sarah for the rec
December 1, 2022
A good read but a bit lackluster for me
March 29, 2020
The good
* Very fun read about chasing hackers... Including deep-dives on how to monitor the hacker (printing their sessions on... paper... seriously), actual scenes of tracing calls ("keep him on the line, we've almost got him!"), and run-ins with the FBI, CIA, and NSA.
* Written in 1989, it's a wonderful throwback to an era when the Internet and email had just started to appear. Amazing to see how many of the technologies and decisions from more than 30 years ago are still with us: lots of fun chatter about Unix, vim, emacs, telnet, ps, viruses, worms, password management, superusers, privilege escalation, and so on.
* Good writing. An impressive mix of spy thriller and nerdy programming concepts (explained for non tech audiences via clear analogies).
* Interesting insights about how the government agencies didn't used to take hacking seriously (FBI, CIA, NSA basically ignored it) and how diversity in the computing system (i.e., different operating systems, networks, etc) protects it, as a single vulnerability or flaw won't affect them all (similar to the protection provided by biological diversity).
The not so good
* Somewhat weird, slightly underwhelming ending. Not that the outcome wasn't crazy, but after all the excitement of the chase, the finale wasn't as satisfying as it should've been.
* The ending also had an odd part where the author wishes people wouldn't hack, wouldn't attack computers, wouldn't exploit vulnerabilities, etc. Given all that he had seen, that seems a bit naive, and about as effective as wishing people wouldn't steal or do other crimes in the real world. The reality is that this stuff will happen, and as computers carry more and more valuable information, it'll only happen more and more often... If we're going to spend time wishing for anything, we should wish for the knowledge and ability to create more secure systems.
Overall
A delightful read. Highly recommended to any programmer and anyone in the tech industry.
* Very fun read about chasing hackers... Including deep-dives on how to monitor the hacker (printing their sessions on... paper... seriously), actual scenes of tracing calls ("keep him on the line, we've almost got him!"), and run-ins with the FBI, CIA, and NSA.
* Written in 1989, it's a wonderful throwback to an era when the Internet and email had just started to appear. Amazing to see how many of the technologies and decisions from more than 30 years ago are still with us: lots of fun chatter about Unix, vim, emacs, telnet, ps, viruses, worms, password management, superusers, privilege escalation, and so on.
* Good writing. An impressive mix of spy thriller and nerdy programming concepts (explained for non tech audiences via clear analogies).
* Interesting insights about how the government agencies didn't used to take hacking seriously (FBI, CIA, NSA basically ignored it) and how diversity in the computing system (i.e., different operating systems, networks, etc) protects it, as a single vulnerability or flaw won't affect them all (similar to the protection provided by biological diversity).
The not so good
* Somewhat weird, slightly underwhelming ending. Not that the outcome wasn't crazy, but after all the excitement of the chase, the finale wasn't as satisfying as it should've been.
* The ending also had an odd part where the author wishes people wouldn't hack, wouldn't attack computers, wouldn't exploit vulnerabilities, etc. Given all that he had seen, that seems a bit naive, and about as effective as wishing people wouldn't steal or do other crimes in the real world. The reality is that this stuff will happen, and as computers carry more and more valuable information, it'll only happen more and more often... If we're going to spend time wishing for anything, we should wish for the knowledge and ability to create more secure systems.
Overall
A delightful read. Highly recommended to any programmer and anyone in the tech industry.
October 1, 2019
Clifford narrates something as boring as tracking an intruder by patiently recording his every keystroke and simultaneously going through a frustrating ordeal of convincing all the three-lettered agencies to take action, scintillatingly and keeps our attention unwavering for 400 pages. There are some aww-inducing sentences like "And the :-) is a crude smiley face. You look at it sideways, and it smiles at you.", reminding you how old this book is. Beyond the hide and seek that unravels between the hacker and the pursuer, its Clifford's constant questioning and moral dilemma that keeps the book relevant even today. Despite a sluggish period where you too feel Clifford's frustration on how things do not move when he keeps narrating his same ordeal over and over, the book's an overall winner.
December 23, 2006
Good old school hacker tale. If you are a techno geek and familiar with the likes of emacs, dot matrix printers and old school bbs boards, this is for you.
Its also a really interesting breakdown of intrusion techniques, much of which holds true today.
Its also a really interesting breakdown of intrusion techniques, much of which holds true today.
March 6, 2020
This book was a mixed bag for me. I found the hacking investigation interesting, but didn’t care about the author’s personal life. Also, if I never hear the phrases “be serious” or “bailiwick” again, it’ll be too soon.
September 22, 2009
Here is the story of how I came to read The Cuckoo’s Egg: I purchased it at a library book sale because it looked interesting, tossed it in a box because I didn’t have time to read it, and promptly forgot about it.
Then I got married, and we got real bookshelves instead of boxes, and I put the book on the shelf because it was hardbound and hardbound books show that you are a serious, thoughtful person.
Then my Uncle Steve came over from Florida and started telling me about a book he had read, a true story of a guy tracking down a hacker in the 80s. “Wait a sec,” I said, “is it this book?” And I pulled down my dusty copy of The Cuckoo’s Egg. It was, in fact, that book, and I decided that it didn’t deserve space on the shelf if I hadn’t actually read it.
The Cuckoo’s Egg is written by an astronomer who had been put in charge of some computers. He’d been trying to track down a 75-cent accounting error–this was back when you had to pay for every cycle of computer time–and, almost entirely by accident, found a hacker in his system, using it as a stepping-stone to attack other computer systems around the country.
That all happens in the first twenty-five pages. Rather than closing the hole the hacker was using to get in, however, Stoll decided he wanted to catch the guy, and that’s where the real story begins, because tracking a communications link backwards is not very easy. None of the three-letter government agencies take him seriously, his relationship with his girlfriend is rather strained, and the three weeks his boss gave him to investigate the problem stretch into months. It’s tedious work (and, in parts, tedious reading) analyzing every move the hacker makes and trying to piece together enough information to catch him.
This book isn’t for everyone. It’s a spy story, but it’s been pieced together from Stoll’s logbook and the man is a scientist–you’ll find no melodrama or embellished details here, just the facts. The author doesn’t assume a technical audience but if you’ve ever used Unix (or its successor on PCs, Linux), you will understand a lot more of what’s going on inside the systems. There’s just enough real-human stuff to break up the technical monotony–Cliff has an active social life, sews his own Pope costume, and at one point microwaves his shoes–but in the end this book is great reading mostly for those interested in computers and security.
I also recommend it if you want to know what the Internet was like in its Wild West days, before the personal computer and the World Wide Web brought it to the masses. Scientists, military networks, and archaic file transfer protocols are all present and accounted for. It’s a fascinating how old everything seems even though the book’s events happened only a little more than twenty years ago.
In closing, here’s a number sequence puzzle that a three-letter-agency spook gave Cliff in the book that–at the time of the book’s publishing–Cliff hadn’t figured out yet. Can you? Hint: It requires very little math.
1, 11, 21, 1211, 111221, ….
Then I got married, and we got real bookshelves instead of boxes, and I put the book on the shelf because it was hardbound and hardbound books show that you are a serious, thoughtful person.
Then my Uncle Steve came over from Florida and started telling me about a book he had read, a true story of a guy tracking down a hacker in the 80s. “Wait a sec,” I said, “is it this book?” And I pulled down my dusty copy of The Cuckoo’s Egg. It was, in fact, that book, and I decided that it didn’t deserve space on the shelf if I hadn’t actually read it.
The Cuckoo’s Egg is written by an astronomer who had been put in charge of some computers. He’d been trying to track down a 75-cent accounting error–this was back when you had to pay for every cycle of computer time–and, almost entirely by accident, found a hacker in his system, using it as a stepping-stone to attack other computer systems around the country.
That all happens in the first twenty-five pages. Rather than closing the hole the hacker was using to get in, however, Stoll decided he wanted to catch the guy, and that’s where the real story begins, because tracking a communications link backwards is not very easy. None of the three-letter government agencies take him seriously, his relationship with his girlfriend is rather strained, and the three weeks his boss gave him to investigate the problem stretch into months. It’s tedious work (and, in parts, tedious reading) analyzing every move the hacker makes and trying to piece together enough information to catch him.
This book isn’t for everyone. It’s a spy story, but it’s been pieced together from Stoll’s logbook and the man is a scientist–you’ll find no melodrama or embellished details here, just the facts. The author doesn’t assume a technical audience but if you’ve ever used Unix (or its successor on PCs, Linux), you will understand a lot more of what’s going on inside the systems. There’s just enough real-human stuff to break up the technical monotony–Cliff has an active social life, sews his own Pope costume, and at one point microwaves his shoes–but in the end this book is great reading mostly for those interested in computers and security.
I also recommend it if you want to know what the Internet was like in its Wild West days, before the personal computer and the World Wide Web brought it to the masses. Scientists, military networks, and archaic file transfer protocols are all present and accounted for. It’s a fascinating how old everything seems even though the book’s events happened only a little more than twenty years ago.
In closing, here’s a number sequence puzzle that a three-letter-agency spook gave Cliff in the book that–at the time of the book’s publishing–Cliff hadn’t figured out yet. Can you? Hint: It requires very little math.
1, 11, 21, 1211, 111221, ….
August 22, 2022
I'm usually super into tales about the early days of computers, technology, the internet, and gaming, but I think this one was a miss for me. The author was an astrophysics student at UC Berkeley who accidentally discovers a hacker while trying to explain a 75 cent(!!!) discrepancy in the computer time books. Rather than shut the guy out, Stoll spends months meticulously tracking the hacker's moves through the early 'net and creating a web of connections within basically every letter agency active at the time. Nobody wants to be the one agency to act, so there's a lot of back-and-forth between agencies at various points of the book, until someone finally loses patience, blinks, and the hacker gets caught.
I had a few issues with the book. I understand it's basically a computer period piece of how technology was at the time, but it still got super repetitive about halfway through. The beginning was really interesting, the end was similarly compelling, but the middle was basically a series of "I see the hacker in my systems, here's what he's doing, I wish I could stop him" short segments. I also was mildly annoyed at the author's massive Main Character Syndrome, where he turns the hacker information over to the proper authorities, and then gets all shocked/angry/annoyed at not being immediately privvy to whatever the government does with the information. Long segments of the book are dedicated to the author waxing philosophical about how he's working with The Man and how much he hates not knowing what's going on. It gets kind of annoying.
I did like the glimpse into the computer technology from the period, though. I liked reading about the innovative ways the author used to track the hacker, determine his location, and mess with him to keep him on the line long enough to be traced. Well done in that respect.
Just kind of a mixed bag of a book all around, honestly.
I had a few issues with the book. I understand it's basically a computer period piece of how technology was at the time, but it still got super repetitive about halfway through. The beginning was really interesting, the end was similarly compelling, but the middle was basically a series of "I see the hacker in my systems, here's what he's doing, I wish I could stop him" short segments. I also was mildly annoyed at the author's massive Main Character Syndrome, where he turns the hacker information over to the proper authorities, and then gets all shocked/angry/annoyed at not being immediately privvy to whatever the government does with the information. Long segments of the book are dedicated to the author waxing philosophical about how he's working with The Man and how much he hates not knowing what's going on. It gets kind of annoying.
I did like the glimpse into the computer technology from the period, though. I liked reading about the innovative ways the author used to track the hacker, determine his location, and mess with him to keep him on the line long enough to be traced. Well done in that respect.
Just kind of a mixed bag of a book all around, honestly.
November 21, 2020
I think it's probably unfair to judge, rate, and/or characterize this book outside of its context and setting, but here we are. It's 2020, and I just don't think this story holds up. I can imagine someone reading this story in 1990 without much background in computers (but also with a burgeoning interest) being completely enthralled with this story. For its time, the hacking techniques outlined were somewhat clever, and the personal aspect of it kept everything grounded. That being said, Stoll beats the reader over the head with the idea that ideologies cannot be so black and white. At least three or four times, we read as Cliff - a liberal-leaning astronomer - meta-analyzes his ironic working relationships with "spooks" from all the three letter agencies. Apart from that, the story-loop gets worn out fast: track hacker, hit a wall, talk to new people, track hacker a little bit further, hit a wall, talk to new people, etc. I would advise anyone with a moderate to advanced technical background to stay away from this one, unless it's from a historical context. In that case, I could see this being an intriguing read. For everyone else, I can't really say.
-----
My scale:
1/5 - Bad. Sometimes did not finish.
2/5 - Not good / meh. Would not recommend.
3/5 - Good. Enjoyable. May or may not recommend.
4/5 - Very good. Memorable story and character.
5/5 - Excellent! Resonates deeply. Often elicits externalized emotional response (laughing out loud, crying/tearing, shouting, etc.)
-----
My scale:
1/5 - Bad. Sometimes did not finish.
2/5 - Not good / meh. Would not recommend.
3/5 - Good. Enjoyable. May or may not recommend.
4/5 - Very good. Memorable story and character.
5/5 - Excellent! Resonates deeply. Often elicits externalized emotional response (laughing out loud, crying/tearing, shouting, etc.)
July 9, 2012
For some years after its 1989 debut, The Cuckoo's Egg was the book to read about computer hacking (or, more specifically, counter-hacking). But this superb read is much more than the memoir of an astronomer who followed a 75-cent accounting "error" to a Soviet spy and sudden fame as the world's top computer security expert.
It's the story of a sincere Berkeley liberal who came to see conservative establishment types as fellow human beings, to the confusion of those closest to him. Candid, thoughtful, and funny, perhaps it can help other liberals - and conservatives - to similarly bridge the culture gap.
(An interesting side note: By 1995, Stoll had all but completely sworn off computers, pooh-poohing the idea of e-commerce and suggesting that computers should not have a place in the classroom. He became a stay-at-home dad and, today, his main concession to computing seems to be the Web 1.0 site where he hawks glass "Klein bottles" he blows in his spare time - including a beautiful mug or "Klein stein.")
It's the story of a sincere Berkeley liberal who came to see conservative establishment types as fellow human beings, to the confusion of those closest to him. Candid, thoughtful, and funny, perhaps it can help other liberals - and conservatives - to similarly bridge the culture gap.
(An interesting side note: By 1995, Stoll had all but completely sworn off computers, pooh-poohing the idea of e-commerce and suggesting that computers should not have a place in the classroom. He became a stay-at-home dad and, today, his main concession to computing seems to be the Web 1.0 site where he hawks glass "Klein bottles" he blows in his spare time - including a beautiful mug or "Klein stein.")
May 7, 2015
Cliff Stoll is an astronomer at Berkley who has been assigned to the IT department. His first assignment is to reconcile a 75 cent variance in their billing records. Astoundingly, this leads into a year long search for hackers trying to steal military secrets. And it's all true.
It happened during the mid-1980's, so the technology is a bit dated at this point, but it doesn't really distract from this fascinating story. fifty pages into the book, I assumed that the 75 cent mystery would be solved in quick order and the rest of the book would be about other tales of hackery in and amongst the interwebbs. But I was wrong. This 300+ page book is about this single encounter with a hacker and boy! what a page turner. I found myself engrossed in the details of Stoll's efforts to learn who was doing the snooping and why.
Great book! Read it if you can get hold of a copy.
It happened during the mid-1980's, so the technology is a bit dated at this point, but it doesn't really distract from this fascinating story. fifty pages into the book, I assumed that the 75 cent mystery would be solved in quick order and the rest of the book would be about other tales of hackery in and amongst the interwebbs. But I was wrong. This 300+ page book is about this single encounter with a hacker and boy! what a page turner. I found myself engrossed in the details of Stoll's efforts to learn who was doing the snooping and why.
Great book! Read it if you can get hold of a copy.
February 7, 2019
This one is a must read for all Unix and Linux fans! It's not just very interesting to read the vivid descriptions of hacker-hunting through Unix commands, but one also learns about the inner working of early computer networks and communication technology. What I liked best about the book, is that Cliff is such a sympathetic person, which is described to the reader by little tales of him and his girlfriend ('sweetheart') sewing together, planting tomatoes or by him burning his shoes accidentally in the microwave. The author concludes with a moral message about privacy, trust, and open source technology, which are even more important values nowadays.
September 1, 2015
Overall it was a great book. It had every element I wanted. It was non-fiction about computers and hacking that was written like fiction. Perfect! The book is an excellent read for anyone interested in a good detective story or has any interests in computers. My only complaint would be that the book gets a bit repetitive and monotonous in the middle. But this is to be expected, as that's likely how any real investigation goes. Would definitely recommend. I can't believe I hadn't heard of this book until just a couple weeks ago.
June 2, 2011
I read this in 1998... My dad had given me a copy so I could understand better what he did for work. It was weird to read...I kept thinking of the gifts he had brought me from his business trips to San Francisco and New Mexico when i was a kid. Anyway, it's a good book. Not the most literary writing, but that doesn't really matter. It's a real-life thriller about one of the first major hacking cases of the Information Age. It's intense. I won't tell you whodunnit. You have to read it yourself.
Displaying 1 - 30 of 1,350 reviews