Slashdot Mirror
Hacker Culture
Let me first recapitulate two brief preludes that figure prominently in Hacker Culture:
- Around 1970 John Draper discovered that a freebie whistle included with Captain Crunch cereal sounded a tone that allowed him, as a literal whistle-blower, to take control of the phone line. Sounding the frequency of 2600 Hz, the high-pitched toy quickly sprouted a cottage industry of small electronic devices called "blue boxes" (first built by Draper) that emitted the commanding tune. Shortly thereafter, in 1971, Steven Jobs and Steven Wozniak built hordes of the boxes and sold them to students in the Berkeley dorms. Jobs and Wozniak would go on to build and found Apple computers by employing the same principle: take existing knowledge and turn it to profit by, eventually, making appropriation proprietary. (Slashdot readers are no doubt familiar with the fact that Mac OS X is not much more than an "aqualicious" -- and expensive -- wrap of FreeBSD.)
- The first personal computer was arguably the Altair. It came as a raw DIY kit that required soldering for assembly and programming to make it work. An early success in coding came in the form of Altair BASIC, a programming language adopted from mainframe systems by Paul Allen and Bill Gates. Unlike other hobbyists who shared their exploits freely, Allen and Gates decided to charge for their adaptation, but were quickly thwarted in their race to the goldmine by the sharing of software at computer clubs, an action that prompted Gates to call fellow developers thieves. For these hobbyists, the notion that programs could be secret and had to be purchased violated the tradition of programming as an ongoing collaboration. The births of our two major personal computing platforms, Mac and PC, consequently both stem from significant changes in the relations between openness and secrecy, sharing and ownership.
In Hacker Culture, Douglas Thomas provides a rewarding account of what preceded and followed these developments, charting the evolution of cracking and hacking from early yet seasoned programmers, generally found at Ivy League departments or under ARPA jurisdiction, to the demonized teenage villains of the 1990s. Although the term "hacking" has become somewhat of an umbrella misnomer to cover diverse behaviors bridging half a century, Thomas does it remarkable justice through, as he puts it, "an effort to understand hacking as an activity that is conditioned as much by its history as by the technology that it engages." To this end, he seeks to engage the role of hacking from an expansive and useful perspective, covering the hacker relationship to technology and society, representation of the hacker through both mainstream media and outlets such as TAP, Phrack and 2600, as well as the juridical construction of the criminalized hacker, which is basically a fancy term for Kafkaesque travesties of justice (the cases of Kevin Mitnick and Chris Lamprecht are analyzed in depth).
Hacker Culture is thankfully not a stylized look at subculture, as an embryonic cult aspiring to become marketable culture, but rather a much broader view of the increasingly computerized networks that comprise society. It is an intelligent exploration beyond the package-design boxes of software, covering our documents, and the product-design casings of computers, housing our institutions. Seen from, or via, an autonomous, skilled perspective on the command line, Hacker Culture provides an indispensable insight into a history of computing that it has become increasingly important to understand for computer users of all levels and abilities. As such, it is perhaps best suited, and intended, for those who do not frequent sites like this, but even pundits with Slashdot bookmarked since it was listed in the root will presumably enjoy the thoughtful analysis Thomas brings to the subject.
A lingering criticism, not exactly directed at the book, is that this publication truly marks the entry of the "hacker" into the realm of academia, where this figure will be dissected ad nauseam along with other minority reports concerned with the so-called radical fringes. Earlier blockbusters on the hacker topic, like Steven Levy's eponymous Hackers: Heroes of the Computer Revolution from 1994, had a certain "sensationalist" appeal that, akin to William Gibson's Neuromancer, drew more of their leitmotifs from classic frontier westerns than cultural criticism. Instead of reading about jacking in and cracking from these primal sources, we got a ton of obligatory theory that read between the lines and reported on the findings at twice the length. Thomas, although he writes both eloquently and lucidly in an entertaining style, is fundamentally connecting the dots of theoretical writing as a second-generation commentator, frequently quoting Levy, for example, and at times the discussion embarks on rather redundant pontifications as a result. (Recall how you can guess the subject of most connect-the-dots outlines, while it usually takes a child careful tracing to number 147 or so before a shriek of joy recognizes the rabbit.) Such misgivings, which are essentially more inspired by the predictable rhetorical mode of academia than this book, are however relatively minor compared to the welcome prospects of actually having some core ideas about free information and open-source computing distributed to a wider audience.
A question remains about what will happen to the figure of the hacker now that we have had, and discussed, both Matthew Broderick, in Hollywood's War Games, and Kevin Mitnick, in jail. In Hacker Culture, both lay claim to capture and coach the collective imagination with regards to what informed autonomy means and the paybacks it receives. Perhaps the future, following Hacker Culture, will prepare a better balance between revered stardom, obscene bankrolls, criminal records and lone isolation cells?
Reviewer Are Flagan has trouble remembering his own passwords. You can purchase Hacker Culture from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
a tedious Kuro5hin style `debate` (two opposing sides not listening to each other) about why it's Cracker and not Hacker (or vice versa).
If anyone likes the idea of a hacker history and doesn't have the time to do the reading, I'd recommend Pirates of Silicon Valley. It aired a few months ago on TV and covers most of what the reviewer talks about.
Very cool to see the history of something that is still so alive today
Have you been stalked by Seth today?
Another decent read, in my view was Takedown - the story of notorious "cracker" Kevin Mitnick. Although the author, Tsutomu Shimomura takes all the credit for doing aboslutely everything, and portrays his team and associates as bumbling idiots, the story about Kevin's life and habits is quite interesting.
;-)
Another pretty good story was "The Watchman" which was about Kevin Poulson, the famous Ma Bell phone switch hacker. This guy was a real freak! The ultimate geek, at one stage he had a stolen phone switch taking up most of his living room in his appartment, along with stolen unix terminals etc. He was the guy who kept winning phone competitions by controlling the phone equipment, and sending goths along to pick up the prizes!
Code, Hardware, stuff like that.
I picked this book up over the summer on a whim. I expected a fairly interesting read that might tend to romanticize the image of hackers in some way.
Not so. The book is actually very dense, and looks at hackers/hacker culture in a more sociological/anthropological context, examining norms and values of the subculture versus traditional society and so forth.
It's interesting and I moved through it fairly quickly, but it's not really light reading. It basically reads like someone's thesis paper or something. And there are enough typos that it just might drive you nuts. But on a four hour flight, I would much rather read this than the thrilling American Airlines magazine.
I am not Herbert.
I wish there was a book that did an enertaining job of chronicling the culture surrounding the people that made the IT world what it is today that did not refer to HACKERS, get them mixed up with CRACKERS and did not play exclusively to the culture of personality around Gates and Jobs.
_ _
Sure, Gates and Jobs should play a big part in chronicle of history around the progress in the computer industry and software industries, sure. However, what about Bill Joy, Ken Thompson and Dennis Ritchie?
They played a big part too. It was not in the PC world sure but it impacted Universities and Corporations on a very large scale. What about talking over the rise of Open Source in a way that did not either make it sound like a magical revolution cheering it forward as the only future or making sound like some horrible fifties commie plot? What about going over it in a detached objective fashion while still capturing the personality and excitement people have?
I am still looking for a good history of the Hacker/IT/Computer Revolution that takes in interesting truly balanced approach.
Does anyone have a good example?
_______________________________________________
ACK
"Consider yourself a member of a virtual corporation with Mr. Torvalds as your Chief Executive Officer." - Linux Advocac
fact ? eh ? If the whole of OS X is not much more than a wrap of FreeBSD then how come the good GNUstep folks are still struggling to complete a workalike after nearly a decade ?
There is a heck of a lot more to OS X than just Darwin you know , just like there is a whole lot more to GNU than just linux.
-- Oh Well
This got me to think about how I would hack a wet paper bag.
Test Subject: Plain small paper bag from a plastic bag of paper bags labeled, simply, "Paper lunch bags." Then I soaked it in water for 2 minutes, shook off the excess water, and laid it down flat.
Software used: I used Red Hat Linux (6.3) and a variety of tools on Windows 2000 (with SP1).
My first attempt was to connect the paper bag to the network. Lacking any RJ11 port, I was forced to assume it was wireless. I placed it on my cable router, in hopes that it would try and boot to DHCP. I waited a long time, but it did not attempt to gain IP access. This would be harder than I thought.
Then I thought maybe it I wrapped the bag around the head of a Cat5 cable, maybe that would work. No luck. It just sat there, inert. I tested the Cat5 cable on a known working system, and found it did not work. I tried another, but while this worked, it did not work on the wet paper bag.
I searched google for "wet paper bag" and "2600 wet paper bag" and Usenet for "wet paper bag." It did not return any useable results, although it appears that quite a lot of people assume script kiddies cannot hack one, either. I checked the TCP/IP manual that came with my Cisco training, and did not find anything that might help. I had no idea what level of the OSI layer would work on a wet paper bag, but I assumed if it was hackable, it would have to at least get to layer 2. So I attached it to an old X.25 serial cable, and tried frame routing, but all I got were device timeouts. Wet paper bags are a LOT more secure than I thought!
After a day of this, I thought I had finally gotten a login prompt, but I found I accidentally was using the IP address of my other LINUX box.
I asked around, and found a script kiddie at the local comic book store. I asked him if he could hack a wet paper bag, but instead of answering, he became angry, and asked me what cable service I used. I didn't think it would help, but I told him everything I knew. Later when I got home, my ZoneAlarm had crashed in what I am guessing was a DOS attack.
So far, I have concluded I cannot hack a wet paper bag, either. I have shown my results to my boss, and soon, "WPB Protocol" will replace OpenBSD as the security standard in all our offices. That gives me only 3 weeks to learn how to program one. I hope there a gcc for it...