Book Description
The best-selling Stealing the Network series reaches its climactic conclusion as law enforcement and organized crime form a high-tech web in an attempt to bring down the shadowy hacker-villain known as Knuth in the most technically sophisticated Stealing book yet.
Stealing the Network: How to Own a Shadow is the final book in Syngress ground breaking, best-selling, Stealing the Network series. As with previous title, How to Own a Shadow is a fictional story that demonstrates accurate, highly detailed scenarios of computer intrusions and counter-strikes. In How to Own a Thief, Knuth, the master-mind, shadowy figure from previous books, is tracked across the world and the Web by cyber adversaries with skill to match his own. Readers will be amazed at how Knuth, Law Enforcement, and Organized crime twist and torque everything from game stations, printers and fax machines to service provider class switches and routers steal, deceive, and obfuscate. From physical security to open source information gathering, Stealing the Network: How to Own a Shadow will entertain and educate the reader on every page. The books companion Web site will also provide special, behind-the-scenes details and hacks for the reader to join in the chase for Knuth.
· The final book in the Stealing the Network series will be a must read for the 50,000 readers worldwide of the first three titles
· The companion Web site to the book will provide challenging scenarios from the book to allow the reader to track down Knuth
· Law enforcement and security professionals will gain practical, technical knowledge for apprehending the most supplicated cyber-adversaries
Customer Reviews:
The SQL Injection Adventures of Pawn.......2007-06-14
Did you enjoy the previous three Stealing the Network books? Are you looking for more? Then move along now, nothing to see here.
The prior books were interesting because they introduced the reader to new ideas or new angles on old ideas, then moved on without belaboring them. If you wanted more details, there were often URLs provided. The last two tied the stories together with the intriguing Knuth character. But the folks running the project chose to switch to a new format, with fewer characters and stories, not to mention fewer authors, and fewer ways to split the profits.
After three books with the same (proven) formula, it's understandable the authors would want to try something new. Alas, it's a disaster.
Welcome to "How to Own a Shadow," aka "The SQL Injection Adventures of Pawn." Pawn is one of the new characters in this volume, and is the first StN character I hoped would get shot to death by the cops in a mini-mall parking lot. Yes, he's that irritating. Particularly after reading 40 pages about his childhood as a high-functioning autistic (or something like that), and around 100 pages of him performing SQL injection attacks. Most of which is totally unrelated to Knuth. Note to the authors: SQL injection is interesting, but if you want to write a book about it, just write a book about it. I even gave you a title, what more do you want? You can even recycle much of this book, like you recycled part of the last one here.
Oh, you noticed the real subtitle of the book, "The Chase for Knuth." First, one chases _after_ fugitives, and hunts or searches _for_ them. Not that it matters, because there's not much chasing or hunting going on in this book. There isn't much Knuth, either. We see him in the first hundred pages, which is mostly about his son analyzing poker software. That's the last we see of either of them. Because, really, this is "The Biography of Pawn." We do get 50 pages of Knuth at the end of the book, but don't get excited: it's all from the last book, added as obvious filler.
Speaking of filler, there's a 17 page advertorial thrown in for BiDiBLAH, which is commercial software by SensePost. Oddly enough, they're listed as technical advisors for the book. I'm sure it's a fine app, but the authors have forgotten about Knuth again, since it has nothing to do with the story. If it had been relevant, it might have been a less obnoxious addition.
Not everything is bad. There's a brief bit about RFID, which of course turns into how to use RFID for SQL attacks. We get to meet Knuth's supposedly dead wife, and a charming shrew she is. All in all, though, this book isn't worth reading unless you're a truly devoted fan of the series, or SQL. I'm still a fan of the previous books, and I hope the authors can recapture what made them so intriguing for their next book. I won't be buying that one until I'm sure it's not Book Two of the Pawn Saga, however.
Author "review".......2007-04-13
Let me first say that I am one of the authors on this book. I don't think authors can objectively review their own work in a forum such as this, so I won't. This won't stop me from rating it five stars to help reinforce the law of averages. ;-)
I will, however, address a few reviews posted here. First and foremost, I am a huge fan of the Stealing series, and the authors that worked on each of the three previous books. But based on customer reviews and our own feelings on the matter, the authors unanimously agreed that boosting the story value of the book was a priority. After all, even security geeks deserve a good plot and decent characters if they take the time to read technical fiction. Books of this genre should also teach. By all fair reviews, this book does both. If you're interested in straight fiction, or straight tech, you'll find this book to only be half-good. If you're willing to be entertained, and are looking to learn something cool about hackers and how they operate, this is the book for you. And there I go, drifting into a review.
So let me address one other complaint: the lack of a "real" ending. Well, that's our fault. There's more to the series, and we know how it's going to end, but we adamantly refused to slip another deadline, so the book went to print with a cliffhanger ending. Now we're not out to sell more books or make your life miserable by leaving you hanging, but this book had to either wrap up where it did, or it would have been scrapped by the publisher, who had no real choice in the matter. As authors, we missed our deadlines, but we did it in order to improve the final product. I'm personally proud of the end result, and the reviews show that we have good reason to be proud.
So to long-time Stealing readers, this book is different because we grew in our craft, and our EXTREMELY capable story editor (Scott Pinzon) held us to the standard of mainstream fiction. Will we make the New York Times best-seller list because of our efforts? No. But this book isn't for those readers. It's for those in and around technology that have read one to many straight technical books.
So we would love to hear what you think. Post a review if you'd like, or if you just want to chat about the book, head over to the "book talk" section of my web site's forums (you know where to find it- Google is your friend). I'd love to hear from you.
j0hnny
One of the better installments when it comes to plot and pacing..........2007-04-05
It's nice when recreational reading overlaps with technical material, and the Stealing The Network series qualifies for that designation. The latest installment is Stealing the Network: How to Own a Shadow - The Chase For Knuth by Johnny Long, Timothy Mullen, Ryan Russell, and Scott Pinzon, and it's an enjoyable read that is heavy on the technical how-to while maintaining a decent plotline.
There's basically two story-lines here... The first involves Robert Knoll Jr. and his father, and is a continuation from the last book. All the police surveillance and investigations are taking a toll on Junior's life, so he decides to act on his father's cryptic message to head down to Mexico with nothing much more than the clothes on his back (and a large amount of cash). He is contacted by people who work for his father, and is taken down to Costa Rica where Senior runs an on-line poker site. Everything that Junior wants is provided (top of the line, too), and he starts doing some programming and network intel for his father. But he really doesn't have a clue as to what Senior is really up to...
The second story-line involves an autistic kid by the name of Paul Wilson. As he grows up, he starts gaining an interest in computer hacking and solving puzzles involving gaining access to various network sites. He's befriended by an on-line entity known as Rafa who is amazed at how Paul can pick up concepts almost immediately. It helps that he has a photographic memory and is wired such that these types of problems engage him. Rafa starts paying him for "research assignments", and Paul is thinking that he's actually doing legit security work. That, coupled with his intense interest in the martial arts, pretty much absorbs all his time. But he starts to understand a bit of what's really going on when he starts to hack a mysterious local business in order to help out a woman in his dojo. She has an ulterior motive for wanting to use his phenomenal hacking skills, but it may get them both arrested or killed.
From a plot pacing standpoint, I was pleasantly surprised. The other books tended to be a bit more "vignette" in nature, so the overall story suffered. At least here, the plot and technology actually supported each other. Again, it's not New York Times best-seller action-adventure, but it works for this type of approach. Paul seemed to be a bit over-the-top in his skills, but that element was supported by his autism. It stretched credibility at times, but not so much that you started to laugh (or at least I didn't). My biggest disappointment is that there was no plot resolution to either story-line, so it's a given that you'll need to read the next one to see how it turns out. The plotlines are converging, and the next book *should* be pretty good. Still, I would have liked a bit more payoff at the end.
Regardless, this is an interesting book about hacking techniques (complete with code) all wrapped up in an action/adventure plot. I'll be interested to see how they merge the story and carry it on in the next installment...
Entertaining way to learn.......2007-04-05
This book was excellent for someone interested in technology but has a hard time reading dull technical books. I have been interested in digital security for a while, but until recently hadn't played around with SQL injections. I was interested in learning more about them and pleased to see that this book offered an excellent primer on SQL injections in the form of a story, which held my interest. In addition there was a cool primer on RFID hacking which I really enjoyed. The supporting story was intriguing and kept me reading to find out what happened next.
There was a cliffhanger ending, and now I'm really looking forward to the next one.
Best One Yet.......2007-03-14
You can definately see the influence of the infamous Johny Long in the writing of this one. The book is incredible i was 150 pgs into it before I could take a bathroom break. :D get it and the rest.
Book Description
Brute Force looks at people having the most contact with everyday animal abuse- humane law enforcement officers who are charged with enforcing anti-cruelty statutes. The author spent one year studying 30 "animal cops" and dispatchers in two large cities. Rookie animal cops think of themselves as a brute force because they believe that they have legitimate authority to represent the interests of abused animals. They see themselves as a power for the helpless, a voice for the mute. On the job experience changes this view. As animal cops conduct their investigations and prosecutions, they see how the public trivializes cruelty. Rather than "fighting the good fight" against egregious cases of cruelty, they are overwhelmed with complaints that are ambiguous and must be "stretched" to qualify as legally defined abuse or with complaints, such as barking dogs or "thin" pets, that are used in interpersonal disputes to get neighbors or spouses into trouble. Even more discouraging to officers are clear-cut and extreme cases of cruelty that do not lead to guilty verdicts or stiff penalties in court. Resulting cynicism is aggravated when rookies realize that they are seen as second-rate "wannabe" cops or closet animal "extremists." With little legitimate authority to enforce the law, animal cops become humane educators who try to make people into responsible pet owners. With few victories in court, they look for other ways to feel effective in their fight against cruelty. And with different preferences for doing police or animal work, their department culture tolerates both styles. Cynicism is replaced by humane realism.
Customer Reviews:
The working world of the humane law enforcement officer.......2004-10-26
Review: Brute Force
This is an insightful, analytically astute, balanced, and timely ethnographic study of humane law enforcement officers (the "animal police"). Suspended, as they are, between police officers and animal control workers, humane officers seek to safeguard the well-being and welfare of animals in a society where animal-human relationships are becoming ever more ubiquitous and ever more finely textured.
Although this is not a "shock book," I still found it disconcerting to read. One would assume (as I did prior to reading this book) that if someone has taken on the responsibility of owning a domesticated/farm animal or pet, that simple utilitarian motives would move that individual to at least minimally provide for that animal[s]. This, sadly, is not always the case. I also learned that legal constructs such as "abuse" and "cruelty" are not clear cut--whether that be in the field or in the courtroom.
Arluke constructs this thoughtful examination around several themes and concepts, including the emotional socialization of humane officers as they move from the idealism of newly graduated rookies to the more nuanced perspective of senior officers. Perspectives toward the meaning of work can differ as Arluke found two occupational groupings in the humane officers he studied: (1) the "police-oriented officer" and the (2) "animal-inclined officers." As reflected in their labels, the police-oriented officers identified more with the police and law enforcements aspects of their work while the animal-inclined officers were often younger, more likely to be female, and more often identified themselves as "animal people" and pet owners.
I was most impressed with the work of humane officers as Arluke detailed the lengths to which these public servants would mediate with animal owners, the complainant and/or neighbors on behalf of animals. Officers bought pet food for poor owners, constructed shelters for trapped in the element animals. and went out of their way to defuse what can easily be extremely volatile situations (e.g., Humane Officer: "A complaint about animal abuse/neglect/cruelty has been made against you...." Animal Owner: "What stinking jerk said that? I want to know who that is--and now."
Most troublesome was the indifference displayed by court officials, (e.g., clerks, district attorneys and judges) when humane officers felt it was necessary to file criminal charges--usually only as a last resort by humane officers who are quite aware of their low stature and legitimacy on the court docket. It is discouraging to think how difficult it is to prove abuse or cruelty and how often the animal literally has to die or be unarguably maimed before justice can be served.
This is a well written and easily digested book, with something for animal lovers (even animal tolerators), and for social scientists interested in understanding the nature and importance of human-animal relationships.
Book Description
FUZZING
Master One of Today’s Most Powerful Techniques for Revealing Security Flaws!
Fuzzing has evolved into one of today’s most effective approaches to test software security. To âfuzz,â you attach a program’s inputs to a source of random data, and then systematically identify the failures that arise. Hackers have
relied on fuzzing for years: Now, it’s your turn. In this book, renowned fuzzing experts show you how to use fuzzing to reveal weaknesses in your software before someone else does.
Fuzzing is the first and only book to cover fuzzing from start to finish, bringing disciplined best practices to a technique that has traditionally been implemented informally. The authors begin by reviewing how fuzzing works and outlining its crucial advantages over other security testing methods. Next, they introduce state-of-the-art fuzzing techniques for finding vulnerabilities in network protocols, file formats, and web applications; demonstrate the use of automated fuzzing tools; and present several insightful case histories showing fuzzing at work. Coverage includes:
• Why fuzzing simplifies test design and catches flaws other methods miss
• The fuzzing process: from identifying inputs to assessing âexploitabilityâ
• Understanding the requirements for effective fuzzing
• Comparing mutation-based and generation-based fuzzers
• Using and automating environment variable and argument fuzzing
• Mastering in-memory fuzzing techniques
• Constructing custom fuzzing frameworks and tools
• Implementing intelligent fault detection
Attackers are already using fuzzing. You should, too. Whether you’re a developer, security engineer, tester, or QA specialist, this book teaches you how to build secure software.
Foreword xix
Preface xxi
Acknowledgments xxv
About the Author xxvii
P
ARTI B
ACKGROUND 1
Chapter 1 Vulnerability Discovery Methodologies 3
Chapter 2 What Is Fuzzing? 21
Chapter 3 Fuzzing Methods and Fuzzer Types 33
Chapter 4 Data Representation and Analysis 45
Chapter 5 Requirements for Effective Fuzzing 61
P
ART II T
ARGETS AND A
UTOMATION 71
Chapter 6 Automation and Data Generation 73
Chapter 7 Environment Variable and Argument Fuzzing 89
Chapter 8 Environment Variable and Argument Fuzzing: Automation 103
Chapter 9 Web Application and Server Fuzzing 113
Chapter 10 Web Application and Server Fuzzing: Automation 137
Chapter 11 File Format Fuzzing 169
Chapter 12 File Format Fuzzing: Automation on UNIX 181
Chapter 13 File Format Fuzzing: Automation on Windows 197
Chapter 14 Network Protocol Fuzzing 223
Chapter 15 Network Protocol Fuzzing: Automation on UNIX 235
Chapter 16 Network Protocol Fuzzing: Automation on Windows 249
Chapter 17 Web Browser Fuzzing 267
Chapter 18 Web Browser Fuzzing: Automation 283
Chapter 19 In-Memory Fuzzing 301
Chapter 20 In-Memory Fuzzing: Automation 315
P
ART III A
DVANCED F
UZZING T
ECHNOLOGIES 349
Chapter 21 Fuzzing Frameworks 351
Chapter 22 Automated Protocol Dissection 419
Chapter 23 Fuzzer Tracking 437
Chapter 24 Intelligent Fault Detection 471
P
ART IV L
OOKING F
ORWARD 495
Chapter 25 Lessons Learned 497
Chapter 26 Looking Forward 507
Index 519
Customer Reviews:
Great book.......2007-08-29
In this book the authors do a number of things that are worth reading:
o Document how and why SPIKE works (and implement their own block-based fuzzer sulley)
o Go through the process of writing a .flv fuzzer
o Go through the process of writing a Python ActiveX fuzzer, which was probably my favorite part.
o Talk about the downsides of various kinds of fuzzing. For example, when is fuzzing with a genetic algorithm not the right thing to do?
That alone made this a great book.
Great on Theory...Pretty Good on Execution.......2007-07-29
I anxiously awaited reading and putting this book to use. Fuzzing is one of those "mystical" concepts that the people cranking out exploits were doing and I wanted to be able to use some of the publicly available fuzzers to fuzz for vulnerabilities and join the ranks.
From the back cover: "...Now, its your turn. In this book, renowned fuzzing experts show you how to use fuzzing to reveal weaknesses in your software before someone else does."
I thought the book excellently covered the theory portions of fuzzing. The format of theory/background of a fuzzing method (Environment Variable and Argument Fuzzing, Web Application and Server fuzzing, File Format Fuzzing, Network Protocol Fuzzing, Web Browser Fuzzing, and In-Memory Fuzzing) followed with that fuzzing method Automation or on Unix and then on Windows worked perfectly. It was a good structure and informative. The Automation or Unix and Windows sections fit in well with the theory sections before it.
I think the book falls a bit short on practical execution (case studies) of using the fuzzing tools. Granted I say this based on my own expectations of what I would like to see from a fuzzing book but also from what the authors say in the preface that we will get out of the book. They say, "We detail numerous vulnerabilities throughout the book and discuss how they might have been identifies through fuzzing." Some of the case studies are exactly what I expected like case studies in Chapter 10, the fuzzing with SPIKE section in Chapter 15, and the Complete Walkthru with Sulley in Chapter 21. Some of the others fall a bit short. I expected a lot more out of the ActiveX fuzzing sections (chapter 18), the Shockwave Flash example in Chapter 21 was useful for the discussion of creating a test case for a protocol but after 11 pages of mostly code in the last section we basically get told to load it into PaiMei and "go fuzz", and while the theory parts of chapter's 7 & 8 were great, telling me to find an AIX 5.3 box to see some example environment variables and argument vulnerabilities was less than useful. It would have been much more useful to use some of today's fuzzing tools to find some old vulnerabilities in something like *BSD or old RedHat distributions, something I might have in the lab or at least something I could install in VMWare.
Likes: Theory, background, discussion of how and why they built the "author built" fuzzers they cover in the book, some of the case studies gave me everything I needed to reproduce on my own in the lab. Providing the fuzzers on the companion website was great as well. The George Bush quotes were hilarious as well and made me look forward to each chapter so I could get another quote.
Dislikes: some of the case studies I don't think went into enough detail (no step by step instructions), I think the explanations of the blocks of code could have been better and numbering lines so we could refer to them in the text would have helped. The discussion of the existing frameworks was a little bit light (but we do get told to go the companion website for more info). Ideally we would have walked thru a couple of easy examples using multiple fuzzer frameworks to get us from advisory to EIP= 0x41414141. That would have been nice to see.
Overall a great book, it has a place on the bookshelf next to shellcoder's handbook and some other programming books and it will be used (many times) as a reference to play with the various fuzzers available out there.
Average customer rating:
- If you've already...
- Chronicle of a Distributed Computing Project
- Extraordinary book, manages to explain complex concepts in simple language
- More interesting and readable than I would have imagined.
- Why exposing the vulnerabilty of DES was deemed to be so critical by those in the know in 1997.
|
Brute Force: Cracking the Data Encryption Standard
Matt Curtin
Manufacturer: Springer
ProductGroup: Book
Binding: Hardcover
 History
| Business & Culture
| Computers & Internet
| Subjects
| Books
Encryption
| Security & Encryption
| Web Development
| Computers & Internet
| Subjects
| Books
General
| Computers & Internet
| Subjects
| Books
General
| Science
| Subjects
| Books
History of Technology
| Technology
| Science
| Subjects
| Books
Social Aspects
| Technology
| Science
| Subjects
| Books
All Amazon Upgrade
| Amazon Upgrade
| Stores
| Books
Computers & Internet
| Amazon Upgrade
| Stores
| Books
Science
| Amazon Upgrade
| Stores
| Books
Similar Items:
-
The Design of Rijndael: AES - The Advanced Encryption Standard (Information Security and Cryptography)
-
Cracking DES: Secrets of Encryption Research, Wiretap Politics & Chip Design
-
Practical Cryptography
-
Applied Cryptography: Protocols, Algorithms, and Source Code in C, Second Edition
-
Crypto: How the Code Rebels Beat the Government Saving Privacy in the Digital Age
Accessories:
-
Guide to Elliptic Curve Cryptography (Springer Professional Computing)
-
Privacy Enhancing Technologies: 6th International Workshop, PET 2006, Cambridge, UK, June 28-30, 2006, Revised Selected Papers (Lecture Notes in Computer Science)
-
Advances in Cryptology -- ASIACRYPT 2006: 12th International Conference on the Theory and Application of Cryptology and Information Security, Shanghai, ... (Lecture Notes in Computer Science)
ASIN: 0387201092 |
Book Description
In the 1960s, it became increasingly clear that more and more information was going to be stored on computers, not on pieces of paper. With these changes in technology and the ways it was used came a need to protect both the systems and the information. For the next ten years, encryption systems of varying strengths were developed, but none proved to be rigorous enough. In 1973, the NBS put out an open call for a new, stronger encryption system that would become the new federal standard. Several years later, IBM responded with a system called Lucifer that came to simply be known as DES (data encryption standard).
The strength of an encryption system is best measured by the attacks it is able to withstand, and because DES was the federal standard, many tried to test its limits. (It should also be noted that a number of cryptographers and computer scientists told the NSA that DES was not nearly strong enough and would be easily hacked.) Rogue hackers, usually out to steal as much information as possible, tried to break DES. A number of "white hat" hackers also tested the system and reported on their successes. Still others attacked DES because they believed it had outlived its effectiveness and was becoming increasingly vulnerable. The sum total of these efforts to use all of the possible keys to break DES over time made for a brute force attack.
In 1996, the supposedly uncrackable DES was broken. In this captivating and intriguing book, Matt Curtin charts DES’s rise and fall and chronicles the efforts of those who were determined to master it.
Customer Reviews:
If you've already..........2007-04-12
If you've already looked up cryptography and/or DES in several encyclopedias (i.e. Britannica, Wiki, Google... ), read Kahn's Codebreakers, Mitnick's and Poulsen's books, then there's no real point in reading this one. Oh, and Schneier's Applied Crypto.
I don't know, this is just me
Chronicle of a Distributed Computing Project.......2006-06-09
This book chronicles the history of how the DESCHALL team won the RSA Data Security, Inc.'s contest to crack a message encrypted with 56-bit cryptography. Although the contest was only one in a series sponsored by RSA, this particular contest was highly significant because 56-bit encryption represented the Data Encryption Standard (DES), meeting the specifications for data encryption required by the United States government. Federal law required the use of DES for government cryptography, and many financial and other private institutions also had adopted DES, but cryptographers and computer scientists were uncomfortable with DES because they felt it was too weak. They felt that 56-bit encryption left confidential data vulnerable to brute-force attacks, in which each of the possible decryption keys is tried until the one that will decrypt the message is found. In cracking the message and winning the RSA contest, the DESCHALL team demonstrated that it was indeed possible to defeat 56-bit encryption within a not unreasonable length of time.
But it wasn't easy. The team needed to try trillions upon trillions of possible keys to see which one would unlock the message. If they were to test each key on a single computer in turn, even using a very powerful supercomputer could take years and years. Instead, the team took a very different approach. They created software that could run on ordinary desktop computers, and got thousands of people across the continent (as well as a few in other regions of the world) to run the software on their own computers. The team leaders set up a server on the Internet to send out assignments of blocks of decryption keys for the participating computers to try, and received the results back over the Internet. Such a system in which many computers in many locations work on a single problem is called "distributed computing." The DESCHALL project wasn't the first time distributed computing was used to solve a problem, but it was one of the first to achieve both significant results and widespread publicity. In this book, Curtain details how the DESCHALL team came about, who wrote and distributed the software, and how the distributed computing project was managed, from publicity to enrollment to winning the contest.
In addition to chronicling the progress of the DESCHALL project, Curtain also provides essential background information about cryptography and the associated political issues. One reason why the DES contest was of such interest was that although stronger 128-bit encryption methods existed at the time, US laws restricted the export of such strong encryption software. Proposed legislation would allow the use of strong encryption only if it provided a backdoor for access by law enforcement. Once the DESCHALL team demonstrated that DES encryption could be cracked relatively easily, more lawmakers were convinced of the need to allow the use of better encryption technology. In addition, the restrictions against exporting 128-bit encryption have been relaxed, allowing US companies to compete in the world market for strong encryption software.
The copy-editing of the book was far from perfect, and there are a number of errors that leave readers scratching their heads, such as "After the list bean receiving and distributing about thirty messages daily,..." nevertheless, the overall text is generally clear and fairly easy to comprehend, even for those who are not cryptography experts. The book makes an enjoyable read for those interested in distributed contributing or cryptography and its associated political controversies during the late 1990s.
Extraordinary book, manages to explain complex concepts in simple language.......2006-06-07
In 1997 Matt Curtin along with a small team of like minded white-hat hackers set out to prove that the security encryption standard DES, (Data Encryption Standard) was no longer secure. For various reasons the US government had chosen not to allow an upgrade which would provide far superior protection. Curtin and the team known as DES-chell harnessed a vast array of computer buffs, and computers across America to prove this vulnerablity and show that this was a serious matter which needed urgent attention. This is Curtin's account of the process. What sets it apart from many other books on code, and computers is that it is highly accessible. This is a book about the process of discovering the code, but it is also a book about the ramifications, the politics, the arguments offered. It also offers, in highly accessible language background to the complex matters he talks about, which made it easy for me, a non-computer buff, to understand.
His use of analogys were wonderful, so talking about the standard 56bit encryption likened it to having a tumbler safe, with only one tumbler with 10 numbers on it there are only 10 settings which could be the possible combination. The average chance of finding the correct setting will therefore take 5 turns. To increase the security you could either add an extra number to the combination, that is make the tumbler have 11 numbers, or by adding an extra tumbler you increase the number of combinations to 100 and automatically made the likelihood of finding the combination 10 times slower. He likens 56 bit security as having 56 tumblers. However the likelihood of finding the combination was still a possibility with that level of encryption. And this is what he set out to do, he and his team believing that the only standard should be 128 bits.
He harnessed thousands of computers across america, and the way he did this is fully documented. What I really liked was another analogy he used here. He discussed the fact that the Brute Force search for the key involved a whole series of simple calculations, and Brute Force searches of the combination (that is searching every combination until you find one) is simply a matter of time. So the higher the bits used int he secutiry the exponentially longer time it takes. However using hugely intelligent computers isn't the best way to find it - it is like getting a trained mathmetician to do a series of 5th grade math sums. He might do them faster, but not that much faster. What you need is thousands of 5th graders working on the sums. So that's what they literally did. Using computers in homes and labs all over the US - although the key people refined the software in some interesting ways to increase the speed.
This is the story of their search, the competition with other groups also searching for the key, and the eventual outcome of the search. The interesting part of the conclusion in the outcome of the search is that the Press really did not seem to understand the complex issues involved. And they are complex, and yet so straight forward. In light of the Twin Towers the ethics vs the basic rights are probably still being strongly debated.
Matt Curtin manages to guide us through the process in good fashion. It is a good read, complex and thought provoking.
More interesting and readable than I would have imagined........2006-06-05
When approached by the author as to whether I was interested in reading Brute Force, I was-- with some reservations. It has been a while since I hung up my tech strategy hat to go work in the non-IT world. Also, even though I'm reasonably technical, I'm a long way from a Cypherpunk. I was a little concern that it would get too technical for me to really appreciate.
To be honest, I was also curious whether there was enough material about DESCHALL to really warrant a full book. I had been aware of the crack when it happened, and had honestly not looked much further than the "brute force. took several months. ho hum." attitude that the press seemed to be applying to the story.
I am pleased to say that I was wrong to be worried on both counts.
First of all, Curtin is a blessedly clear writer. As he covers topics which are cryptography specific, he explains them. Furthermore, he explains them using simple language so that I had no problem understanding. You do not need to be a cryptographer to read this book.
Second, there apparently is enough material for a full book. Curtin manages to set up a really interesting story that is fully placed in a political and social context. Bonus because he does that without rehashing ground that has been covered about PGP and Zimmerman in other books. I found myself really interested in the DESCHALL efforts. It was particularly interesting to start drawing the analogy with later distributed computing efforts that were essentially tested with this effort.
The foreward by Gilmore was fun enough-- but then, I like his writing and I really like the EFF.
I would recommend this book for someone interested in the history of computing, or for someone with a special interest in security issues. Some computer background helps, but you do not need to be a specialist to read and enjoy the book. Truthfully, the book is closer to 4 and a half stars than five-- but Curtin gets some extra credit for all the ways that he could have made it unreadable, but did not.
Why exposing the vulnerabilty of DES was deemed to be so critical by those in the know in 1997........2006-05-27
In many ways reviewing Matt Curtin's "Brute Force" is a real challenge for me. That is because I am not particularly well versed in computer technology. As such I did not recognize nor did I understand the meaning of a great many of the technical terms that were necessarily used throughout this book. I must admit that I really struggled with this reality at times. But having said that I still found "Brute Force" to be a very worthwhile read.
In order to fully appreciate the magnitude of the issues involved here it is extremely important to understand the prevailing political climate in this country back in 1997. As new and more elaborate uses for computers and the internet were emerging it seems that the U.S. government was content to continue with inferior encryption standards. DES (Data Encryption Standard) was a 56-bit key cryptographic system that had been the standard in this country since 1977. Even during those early years many computer experts were warning that this rather weak system would soon have to be replaced. The risk of data being compromised was simply too great. In 1997, as the battle lines were being drawn over replacing DES with a much stronger standard our government wanted access to virtually all information--even if encrypted. On the other hand private industry and individual citizens were clamoring for a much tougher encryption standard to replace DES. This battle could have gone either way. "Brute Force" tells the amazing story about how a group of like-minded people banded together to prove once and for all that DES was extremely vulnerable to attack. Matt Curtin tells the story of the unique competition that would emerge and ultimately lead to tougher and more secure encrytion that would benefit just about everyone in this country. What occured in the Spring of 1997 is a truly remarkable story and Matt Curtin tells it very well.
As I indicated earlier "Brute Force" contains a lot of technical jargon that many folks would not be familiar with. It is probably safe to say that the more you know about computers the more you will glean from this book. But I was able to follow the story line pretty well and learned an awful lot about a topic I knew virtually nothing about. In the end it was well worth the effort. Recommended.
Average customer rating:
- Save Your Money, Find Another Book
- Very weak action novel
- The Action Starts Here!!!
- The Action Starts Here!!!
- Action Sci-Fi
|
Brute Force
Dean Wesley Smith
Manufacturer: Del Rey
ProductGroup: Book
Binding: Mass Market Paperback
Smith, Dean Wesley
| ( S )
| Authors, A-Z
| Science Fiction & Fantasy
| Subjects
| Books
Adventure
| Science Fiction
| Science Fiction & Fantasy
| Subjects
| Books
General
| Science Fiction
| Science Fiction & Fantasy
| Subjects
| Books
( S )
| Authors, A-Z
| Science Fiction & Fantasy
| 4-for-3 Books Store
| Stores
| Books
Adventure
| Science Fiction
| Science Fiction & Fantasy
| 4-for-3 Books Store
| Stores
| Books
General
| Science Fiction
| Science Fiction & Fantasy
| 4-for-3 Books Store
| Stores
| Books
All 4-for-3 Deals
| 4-for-3 Books Store
| Stores
| Books
Similar Items:
-
Crimson Skies
-
First Strike (Halo)
-
Ghosts of Onyx (Halo)
-
Halo, Books 1-3 (The Flood; First Strike; The Fall of Reach)
-
The Flood (Halo)
ASIN: 0345458508
Release Date: 2002-10-01 |
Book Description
At the dawn of the twenty-fourth century, with colonies spanning fifty star systems, mankind has created the Confederation of Allied Worlds. When trouble erupts, the Confed’s solution is swift, savage, and supremely effective: dispatch small teams of elite warriors. Deadly fighters like Tex. . . .
As one of the most decorated soldiers in the Confederation’s arsenal, Tex has survived covert operations in every steaming hellhole. As a result, he knows more than enough about the Confed’s most brutal and amoral activities, which makes him wonder: Is it mere coincidence that all missions assigned to veteran teams seem to be suicide missions?
Fortunately, the new assignment doesn’t have the markings of a lethal affair. Tex is dispatched to the Ulysses star system, a backwater group of inconsequential planets populated with misfits and malcontents. What he doesn’t know is that this lowly cluster secretly harbors perhaps the greatest threat ever faced by the Confederation. Worse yet, the shadowy Protectorate behind the mission intends to make certain Tex does not survive.
But Tex hasn’t earned his reputation as a well-honed killing machine for nothing. . . .
Brute Force, Xbox, and the Xbox Logos are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Used under license. Copyright © 2002 Microsoft Corporation. All Rights Reserved.
Customer Reviews:
Save Your Money, Find Another Book.......2006-01-23
The Halo books were great! This book is a fine example of using a poor plot and a poor writer. I would rate this book a 2 on a scale of 1 to 10. If you must read this book, check it out from your public library and save your money. I have never read any of Mr. Smith's books and after this one, I know I won't read anymore of his books. There are too many GOOD books available to read instead of wasting your time on this type writing.
Very weak action novel.......2005-11-26
After playing Brute Force, I expected something like what hapenned to me after playing Halo and devouring the 3 Halo series books: just and plainly being amazed about the gathering of sweet writing around a very good game.
I enjoyed Brute Force, but found the book very weak up to the point of finding it boring. The book starts right in the action (very pale by the way) and develops slughishly through the paces of diferent operative misions. By the time it starts to get momentun; voilá, the book is over!!! No good whatsoever. If you really want to get hooked in a game-based book, get the Halo's series, or Crimson Skies, and you will be delighted.
The Action Starts Here!!!.......2005-11-08
"Nice shootin'," Tex said, as the Special Operations team
charged into the enemy base killing some guards on the way in.
Dean Wesley Smith, the author of Brute Force Betrayals, likes
to be discriptive in his writing. He uses description in his
battle chapters like, "His cut was viciously bleeding down
Tex's neck" and "The deafening sounds of explosions were all
over the planet". What I like about the author's writing
style is that he never stays on one topic for long he keeps
the action flowing by having each chapter going to a different
battle. One thing I don't like about the book is that it has
alot of swearing in it. The story is told in first
and second point of view.
Mainly the book is about a confederation of Special Force
Operatives fighting the rebel planets. The main characters
are Tex- a strong heavy weapons operative.
Hawk- the intelligent leader of Tex and Flint.
Flint- sniper that is on Tex's and Hawk's team.
The book is set in outer space and the genre is science fiction/fantasy.
I recommend this book to people who like shooting video games from ages
13-adult.
The Action Starts Here!!!.......2005-11-08
"Nice shootin'," Tex said, as the Special Operations team
charged into the enemy base killing some guards on the way in.
Dean Wesley Smith, the author of Brute Force Betrayals, likes
to be discriptive in his writing. He uses description in his
battle chapters like, "His cut was viciously bleeding down
Tex's neck" and "The deafening sounds of explosions were all
over the planet". What I like about the author's writing
style is that he never stays on one topic for long he keeps
the action flowing by having each chapter going to a different
battle. One thing I don't like about the book is that it has
alot of swearing in it. The story is told in first
and second point of view.
Mainly the book is about a confederation of Special Force
Operatives fighting the rebel planets. The main characters
are Tex- a strong heavy weapons operative.
Hawk- the intelligent leader of Tex and Flint.
Flint- sniper that is on Tex's and Hawk's team.
The book is set in outer space and the genre is science fiction/fantasy.
I recommend this book to people who like shooting video games from ages
13-adult.
Action Sci-Fi.......2003-10-24
Brute force is a fun, light read. It is not deep and lacks some character development. I was hoping that the book would reveal more detail of the character's history; but it did not. It lets us down in that department. But the action makes up for It- kinda feels like a comic book because the action is off the wall is some parts. In the first mission "Tex" and his team demolish a group of pirates inside their base and steal their money. Later on he cooperatively works with a scout named "Hawk" who is able to make herself invisable. And an android named "Flint" also joins in; it can sharp-shoot with a sniper rifle with deadly accuracy. The story and action-packed pacing is what
makes it entertaining and good if you are bored. And the ending is shocking. I recommend it if you want something fun to read and you like a light read.
Average customer rating:
|
Industrialized Nature: Brute Force Technology And The Transformation Of The Natural World
Paul Josephson
Manufacturer: Island Press
ProductGroup: Book
Binding: Hardcover
General
| Social Sciences
| Nonfiction
| Subjects
| Books
Social Theory
| Sociology
| Social Sciences
| Nonfiction
| Subjects
| Books
Environmental Science
| Earth Sciences
| Science
| Subjects
| Books
General
| Science
| Subjects
| Books
General & Reference
| Technology
| Science
| Subjects
| Books
History of Technology
| Technology
| Science
| Subjects
| Books
General
| Environmental
| Civil
| Engineering
| Professional & Technical
| Subjects
| Books
Air
| Pollution
| Environmental
| Civil
| Engineering
| Professional & Technical
| Subjects
| Books
Ecology
| Biological Sciences
| Professional Science
| Professional & Technical
| Subjects
| Books
Environmental Science
| Earth Sciences
| Professional Science
| Professional & Technical
| Subjects
| Books
Conservation
| Environment
| Outdoors & Nature
| Subjects
| Books
Living on the Land
| Ecology
| Outdoors & Nature
| Subjects
| Books
| Architecture
| Hunting & Fishing
ASIN: 1559637773 |
Book Description
The construction of the Three Gorges Dam on China's Yangtze River. The transformation of the Amazon into a site for huge cattle ranches and aluminum smelters. The development of Nevada's Yucca Mountain into a repository for nuclear waste. The extensive irrigation networks of the Grand Coulee and Kuibyshev Dams. On the face of it, these massive projects are wonders of engineering, financial prowess, and our seldom-questioned ability to modify nature to suit our immediate needs. For nearly a century we have relied increasingly on science and technology to harness natural forces, but at what environmental and social cost.
In Industrialized Nature, historian Paul R. Josephson provides an original examination of the ways in which science, engineering, policy, finance, and hubris have come together, often with unforeseen consequences, to perpetuate what he calls "brute-force technologies"?the large-scale systems created to manage water, forest, and fish resources. Throughout the twentieth century, nations with quite different political systems and economic orientations all pursued this same technological subjugation of nature. Josephson compares the Soviet Union's heavy-handed efforts at resource management to similar projects undertaken in the United States, Norway, Brazil, and China. He argues that brute-force technologies require brute-force politics to operate. He shows how irresponsible?or well-intentioned but misguided?large-scale manipulation of nature has resulted in resource loss and severe environmental degradation.
Josephson explores the ongoing industrialization of nature that is happening in our own backyards and around the world. Both a cautionary tale and a call to action, Industrialized Nature urges us to consider how to develop a future for succeeding generations that avoids the pitfalls of brute-force technologies.
Customer Reviews:
Fascinating insight into WWII.......2002-09-06
I just finished reading Brute Force by John Ellis. His thesis is that of the title i.e. the war was won largely by the overwhelming productive capacity of the allies. He backs this up with clear and ample statistics. But his book is by no means dry. In fact it was very engrossing for he delves deeply into the causes and implications of the production dissimilarities. While praising the heroics and sacrifices of allied soldiers, he doesn't spare their leadership for succumbing to the temptation of brute force. Numerous quotations and stories make the book an enjoyable read. One story is of a German lieutenant who told his captors how the American tanks kept coming and he kept shooting them. "Unfortunately, we ran out of bullets before you ran out of tanks." If you are not aware of the economic aspects of the war, this book can certainly change your perspective. Definitely a well researched and well written book. But, you may also wish to read "Why the Allies Won" by R. Overy. His thesis (in one sentence), is that WWII was really won in 1942 when the Axis still had parity.
A controversial but well written book.......2001-09-04
Remember all the World War II movies where a handful of American or British soldiers mow down scores of German soldiers because the Allies are smarter? Ellis' argument here is that the Allies won the war not by being smarter that than the Germans but by outproducing them in war material by a huge margin. Ellis produces a substantial amount of evidence to support his claims. For example, the famous Luftwaffe bombing of London in 1940 cannot compare to the tremendous number of bombs dropped by the Allies on Berlin. Part of the reason for discrepancy in production is that the Allies, as stable democracies, were quicker to put their economies on a war footing. Unfortunately, the innovations they used to increase production beyond levels previously believed possible did not extend to military tactics. The result were higher casualties and a longer war than might have othewise been the case.
Average customer rating:
- so-so strategy guide
- Brute force is long, this helps alot
|
Brute Force (Prima's Official Strategy Guide)
Steve Honeywell
Manufacturer: Prima Games
ProductGroup: Book
Binding: Paperback
General
| Strategy Guides
| Games & Strategy Guides
| Computers & Internet
| Subjects
| Books
Video Games
| Games & Strategy Guides
| Computers & Internet
| Subjects
| Books
General
| Puzzles & Games
| Entertainment
| Subjects
| Books
Video & Electronic Games
| Puzzles & Games
| Entertainment
| Subjects
| Books
Similar Items:
-
Brute Force
ASIN: 0761539883
Release Date: 2003-06-03 |
Book Description
Elite. Highly-Trained. Brutal.
·Exclusive excerpt from the now available Brute Force: Betrayals
·Complete walkthrough of each mission
·Tactics for controlling the right character—in the right situation
·Tips to dominate multiplayer action
·Vital stats for all weapons, items, and characters
·Strategies for commanding your elite team
Customer Reviews:
so-so strategy guide.......2003-07-04
I was rather disappointed in this strategy guide. There were numerous places where the book was just no help at all, particularly on the final level. Now, to be fair, some of this is due to repetitive level design on the part of the game's makers. Still, there were too many instances of the guide saying, more or less, "Now go over a hill and find the thing and blow it up." Every hill looks the same! Which one?!
Brute force is long, this helps alot.......2003-06-05
With Brute Force only being released on tuesday (28th) this brute force strategy guide puts you through all the levels. I do recommend that to get a nice handfo the game only use the book as a reference, yuo wont take advantage of the games super engine and teamwork controls. This game is awsome, so get this awsome strategy guide, yet its not differnet than any other strategy guide? well whatever,
Customer Reviews:
GREAT ACTION ADVENTURE!.......1999-07-29
If you want heroes galore - this one is for you. There is a movie written all over this book and the rest of the series. The author also writes other action books under the name Jack Buchannan, the series - M.I.A. Hunter! Another great action/adventure series.
Guns, War, violence and bloodshed.......1998-06-08
This book was entertaining. The plot left nothing to be desired. It was fast paced and action-packed. Loved every minute, and never wanted it to end.
Books:
- Stick Control for the Snare Drummer
- Stop Sitting on Your Assets: How to Safely Leverage the Equity Trapped in Your Home and Transform It Into a Constant Flow of Wealth and Security
- Storm Front (The Dresden Files, Book 1)
- Subaru Legacy, 1990-1999: Includes Legacy Outback and Legacy Brighton (Haynes Manuals)
- Technical Analysis Explained : The Successful Investor's Guide to Spotting Investment Trends and Turning Points
- The Adventures of Tintin: Tintin in America / Cigars of the Pharaoh / The Blue Lotus (3 Complete Adventures in One Volume, Vol. 1)
- The Beck Diet Solution: Train Your Brain to Think Like a Thin Person
- The Botany of Desire: A Plant's-Eye View of the World
- The Children of Now: Crystalline Children, Indigo Children, Star Kids, Angels on Earth, and the Phenomenon of Transitional Children
- The Complete Visual Dictionary of Star Wars: The Ultimate Guide to Characters and Creatures from the Entire Star Wars Saga
Books Index
Books Home
Recommended Books
- Storm of Steel
- Life After Death: The Burden of Proof
- Amos : To Ride A Dead Horse
- Bettas: A Complete Introduction
- Emily The Strange
- History: Fiction or Science
- Head First PMP: A Brain-Friendly Guide to Passing the Project Management Professional Exam
- Caught Inside: A Surfer's Year on the California Coast
- Confessions of a Window Dresser Tales From A Life In Fashion
- Don't Die Broke
Stealing the Network: How to Own an Identity (Stealing the Network) (Stealing the Network)
Stealing the Network: How to Own the Box
Stealing the Network: How to Own a Continent
Hacker's Challenge 3 (Hacking Exposed)
Botnets: The Killer Web Applications
