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).
Looks like an interesting read. Now where can I download the e-book version of it? Doc "There are two essential rules to management. One, the customer is always right; and two, they must be punished for their arrogance." - Dogbert
We should take care not to make the intellect our god; it has, of course, powerful muscles, but no personality.
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?
but I don't think that there is any culture with hackers. These are just frustrated acne-ridden teenage teenagers who what to get rid of their frustration by bring mischief over other people. This "finding security holes and increasing security" is just a bad excuse for this. Hahaha increasing security by hack into a system and install a rootkit and several assorted backdoors ?
And these "white hat" hackers are just a grown up version of these kids. Take a guy like fyudor the nmap creator who hacked into the system of some kiddy slashdot troll just because he called him a wanker. Security increasing by threatening 17 year olds ?
I think it's very bad when books like this glorify criminals - and that's what hackers really are. This takes kids onto the bad road ending them up in prison someday.
I was introduced to computers from the hacker culture presented in the (mediocre) film hackers when I was in early teens. People grouch quite a lot about the portrayal of hackers in modern culture (speckled 'evil' nerd - 2600 letters often have stories of people who enjoy hacking and informing administrators of vulnerabilities getting suspended, and associated with people like the trenchcoat mafia), but I found the film really interesting - the characters seemed like normal people for a change (not segrated because of seclusiveness or 'black clothes', but because they were just smarter).
"You know you don't act like a scientist, you're more like a game show host." Dana Barret
hacking the GIBSON in this book?
Why oh why do we have to go over this again?
figure of the hacker now that we have had, and discussed, both Matthew Broderick, in Hollywood's War Games, and Kevin Mitnick, in jail.
Matthew Broderick, in WarGames, and Kevin Mitnick, in 'low security but you still get pounded up the ass' prison, were not hackers.. they were crackers.
Hackers are friendly quiche eating Pascal programmers and Mac users, whereas crackers are naughty people who do a lot of hacking.
Crackers are also quite nice with some cheese on them.
mogorific carpentry experiments
oxymoron
Best Windows Freeware
Most of the time the reviewer is talking about "intruder" types, like Kevin Mitnick, Phrack and 2600, but then periodically jumps over to Steven Levy and the Altair, using a much more Jargon File-ish use of "hacker".
I don't care particularly which word is used but came away from the review without a clear idea of what the book is about.
What I'm listening to now on Pandora...
If this is the first, where does The New Hacker's Dictionary come in? Not mainstream enough? It is much more than just the Jargon File.
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.
Living in a small town and being able to work command lines has people in total fear of me. People assume that because I can really use a computer I'm some sort of nefarious hacker just waiting for the chance to steal all their financial info.
When are non-geek types going to realize that being a serious computer user, system admin or even a programmer doesn't mean you're ALSO a hacker? When will they start taking a bit of responsibility for securing their systems? Most hackers I've met here are script kiddies who couldn't hack a wet paper bag if the people in the area bothered installing security patches...
I put crackers into my soup. Hackers are the dedicated computer hobbyists. Some of them do legal stuff and some cross over the line. They all are hackers. Go back into the past. Look at the MIT hackers from a few years back. Traditionally hackers aren't going for profit and don't do damage. They just explore and learn. Just like like in any classification of people there are some people that are nice and some that are not so nice. Cracker is a stupid term. Many of your so called crackers are very dedicated hobbyists and if you looked deeper you would find out they are truely hackers by the very definition. Of course most of them are script kiddies, but hey, you gotta start somewhere..
IIS only runs on PCs. My guess is that this "wet paper bag" architecture you speak of usually runs Apache.
Most hackers I've met here are script kiddies who couldn't hack a [server] if the people in the area bothered installing security patches (i.e. Linux).
Mod me down and I will become more powerful than you can possibly imagine!
No need for this!
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
to interject that raw food veganism is the only morally acceptable lifestyle.
Hm. Hey, all the pages are blank!
hyacinthus (as are the pages of the book's sequel, _Hacker Philosophy_)
Since the story on ESRI was rejected, I am asking all Linux scientists who use GIS systems to follow this link to take a survey in support of Linux development.
"Rocky Rococo, at your cervix!"
If you want good books that show what hackers were doing to military installations and whatnot in the mid-80's, try reading 'The Cuckoo's Egg' or 'Masters of Deception'. These books will give you a good look at how Tymnet was more full of holes that Swiss cheese at that point is history. 'The Cuckoo's Egg' is better, but they are both enjoyable, from a hacker's perspective.
Sleep: A completely inadequate substitute for caffeine.
It's not comprehensive, but you might want to check out Tracy Kidder's Soul of a New Machine (I'm too lazy at the moment to link to a bookseller) about the creation of Data General and the much-revered VAX line of computers.
BTW, it is my suspicion that years from now, when all the dust settles, folk will conclude that a lot of key development of computers actually took place in industries like trucking (traveling salesman problem anyone?) far from the spotlight, where the techies were just expected to get the job done and not pressed for details.
After all, what was the first major industry to universally computerize?
Can you guess?
That's right, retail stores. Yup. Sam Walton always said that the biggest thing that gave him his edge was his heavy usage of computers for things like logistics and anticipation of demand.
Now given that the other major contenders are accounting/insurance and personnel departments I suspect that for every Steve and Steve working at Atari was a just as influential person who did their seminal work in a polyester shirt in some big conservative company. But since that's not good televison, it ain't gettin' covered any time soon. After all it would be much harder to cast a heartthrob like Noah Wyle in such a role. The best you'ld do is Jack Black or Curtis "Booger"Armstrong.
Off to dig out my original, pre-recall, "Real Genius" poster,
Rustin
Data is the lever, rigor the fulcrum, brains the force that drives it all.
My main problem with this book is that although the subject matter is fascinating, the actual writing is tedious, and follows an extremely dry academic style. I felt like I was reading a graduate-level sociology dissertation. Ho, hum. Material this interesting deserves a much better treatment.
Jeez, getting through the introduction was a chore. I was reminded of the Bataan Death March. The introduction was the worst. It was like an endless academic spiel, just going on, and on, and on, and on (but you get the idea). BREVITY IS THE SOUL OF WIT, MAN! Sigh...
Still...
He means well. And, for an academic audience, the book might be helpful in that it might frame hackers in a more positive, more accurate light.
But, Jesus, does he ramble. I think a much better-written book on hackers is "Hackers" by Steven Levy, which follows the original MIT hackers, and traces up through the microcomputer companies and game developers that came later. I'd like to see Mr. Levy do a followup, taking us from the early nineties to the present. He's a much more animated, interesting writer (no disrespect to the academic style of "hacker culture", it's just a little dry).
Farewell! It's been a fine buncha years!
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
Reading this book cleared my illusion that all /. readers led lives like Zero Cool and Acid Burn from "Hackers", the movie.
"Hack the gibson!"
Hackers are friendly quiche eating Pascal programmers and Mac users, whereas crackers are naughty people who do a lot of hacking So... people who "do a lot of hacking" are NOT called hackers, according to you? Interesting distinction. I guess there's precedent. People who lie, cheat and steal aren't called criminals, they are called politicians...
Actually, "eponymous" refers to the giver of the title, e.g. "Romulus was the eponymous founder of Rome." So a book named "Steven Levy" would be eponymously-titled.
And just because you're a hacker doesn't mean you do anything illegal or nefarious. The term also indicates people in certain professions, or who do many forms of intense but not illegal code-hacking on PC's
Who replace my cat-in-bag with a can-of-worms? - phorm
and their relationship to the hacker culture and mainstream culture is:
"Underground"
Which is available, in its entirety here:
http://www.underground-book.com/download.php3
What I really liked about this book was the indepth story telling about several hackers, their relationships with other hackers (globally I might add), their relationships with family and other "non-hackers," and their general makeup as people.
After reading this, I felt I had a much better appreciation of the importance that the hacker culture can have for some people. The hacker underground was clearly a place where these kids felt most comfortable, and in some cases provided an important level of social support that they didn't otherwise have access to.
Living in a small town and being able to work command lines has people in total fear of me.
!!!!!!!!
Holy crap man! Don't you see the possiblities here? You can make them all your PERSONAL SLAVES! Get on it right away!
If tits were wings it'd be flying around.
nt sorry everyone just useless post so i can read this later when i'm not drunk and going to class
GENERATION O98346: The first time you see this, copy it into your sig and remove a random number from the generation. T
...most hackers have traditionally been found in, on, or near large, well-computerized research universities.
In fact, that person sitting next to you in class could be a hacker! Your prof could be a hacker! Your friendly school janitor could be a hacker!
(Are you now, or have you ever been a hacker?)
Heh...
Academicians have been talking about hackers for a long time. (I seem to recall writing a paper on the subject for a grad school class, and doing some reading up for it, anyway.) Maybe people just didn't notice until now.
I'm not a geek, I'm just a clever script.
...I can't believe people still think Captain Crunch (John Draper) discovered that the whistles inside Captain Crunch Cereal were able to emit roughly 2600hz tones. It was actually a group of blind phone phreaks who Draper hung with. This is known, has been known a long time, and even Draper has admitted as such in a number of interviews (after he's gotten older, after his supply of young hackers has essentially been assured based on his "reputation").
Please, don't perpetuate a falsehood. And no, you really don't want any "stretching exercises".
You can read Howard Rheingold's "Tools For Thought" online or buy it from MIT Press. I think Bill Gates is mentioned only once.
This reads like a transcript for that TLC program about hackers:
Hackers: Computer Outlaws
[ There are many variations of this. Here is one, which is shorter than others but has more of the feel of the "original" I remember from way back when... source: http://www.cirr.com/~barkley/jokes/realprog.html ]
Real Programmers...
Don't eat quiche. Real programmers don't even know how to spell quiche. They like Twinkies, Coke, and palate-scorching Szechwan food.
Don't write applications programs. They program right down to the bare metal. Applications programs are for dullards who can't do systems programming.
Don't comment their code. If it was hard to write, it should be hard to understand and even harder to modify.
Don't draw flowcharts. Flowcharts are, after all, the illiterate's form of documentation. Cavemen drew flowcharts; look how much it did for them.
Don't use COBOL. COBOL is for wimpy applications programmers.
Don't use FORTRAN. FORTRAN is for wimpy engineers who wear white socks, pipe stress freaks, and crystallography weenies. They get excited over finite state analysis and nuclear reactor simulations.
Don't use LOGO. In fact programmers use LOGO after puberty.
Don't use APL unless the whole program can be written on one line.
Don't use LISP. Only effeminate programmers use more parentheses than actual code.
Don't use Pascal, BLISS, ADA, or any of those sissy-pinko computer science languages. Strong typing is a crutch for people with weak memories.
Never work 9 to 5. If any are around at 9 a.m. it's because they were up all night.
Don't play tennis or any other sport that requires a change of clothes. Mountain climbing is OK, though, and real programmers often wear climbing boots to work in case a mountain should suddenly spring up in the middle of the machine room.
Don't like the team programming concept. Unless, of course, they are the Chief Programmer.
Have no use for managers. Managers are a necessary evil. They are for dealing with personnel bozos, bean counters, senior planners, and other mental defectives.
Don't drive around in clapped out mavericks. They prefer BMW's, Lincolns, or pick-up trucks with floor shifts. Fast motorcycles are highly regarded.
Like vending machine popcorn. Coders pop it in the microwave oven. Real programmers use the heat given off by the CPU. They can tell what job is running just by listening to the rate the corn is popping.
Know every nuance of every instruction and use them all in every real program. Puppy architects won't allow execute instructions to address another execute as the target instruction. Real programmers despise such petty restrictions.
Don't bring brown bag lunches to work. If the vending machine sells it, they eat it. If the vending machine doesn't sell it, they don't eat it. Vending machines don't sell quiche.
Kind of ironic that the Microsoft Press reprinted it more recently, although that copy of mine doesn't have a very good binding and is falling apart.
I'm impressed with the called shot of Flamebait. However it might not have been flamebait had you backed up your post. Realistically I don't see anything wrong with the description of Darwin. #1 it is aqualicious (I'm assuming this as a good adjective) and it damn sure is expensive (I have 3 mac's and they are worth every penny). So if you had commented as to why that was an incorrect description maybe you wouldn't have had to call your own shot.
Just my thoughts.....
I thought @Large was quite interesting. It does a good job of debunking the "genius geek hero," too, showing the cracker as pretty pathetic, but also showing how much damage he could achieve. Good antidote to too much William Gibson (I love the stuff, but it's no more real than Raymond Chandler's about real private eyes).
i agree!
http://www.biker-needs-a-harley.org/
i tend to use the trash can in my office. good luck!
http://www.biker-needs-a-harley.org/