Average customer rating:
- True Brady Bunch Fans Might Want To Think Twice Before Reading This
- A walk through Bradyland
- Even With It's Flaws I Still Love This Book!
- About the many mistakes in the ep guide
- Great buy!
|
Growing Up Brady : I Was a Teenage Greg
Barry Williams , and
Chris Kreski
Manufacturer: Good Guy Entertainment
ProductGroup: Book
Binding: Paperback
 Entertainers
| Arts & Literature
| Biographies & Memoirs
| Subjects
| Books
Television Performers
| Arts & Literature
| Biographies & Memoirs
| Subjects
| Books
General
| Biographies & Memoirs
| Subjects
| Books
Family & Childhood
| Biographies & Memoirs
| Subjects
| Books
Memoirs
| Biographies & Memoirs
| Subjects
| Books
General
| Foreign Languages
| Reference
| Subjects
| Books
General
| Arts & Photography
| Subjects
| Books
General
| Performing Arts
| Arts & Photography
| Subjects
| Books
Look Inside Art Books
| Trip
| Specialty Stores
| Books
Look Inside Biographies
| Trip
| Specialty Stores
| Books
Look Inside Entertainment Books
| Trip
| Specialty Stores
| Books
Look Inside Reference Books
| Trip
| Specialty Stores
| Books
Similar Items:
-
Brady Home Movies
-
Growing Up Brady
-
Brady Bunch Book
-
The Brady Bunch Guide To Life (Miniature Editions)
-
It's a Sunshine Day: The Best of the Brady Bunch
ASIN: 0967378508 |
Book Description
This is the inside story of The Brady Bunch as only Barry Williams could tell it! In this updated Collector's Edition are updated information and numerous never-before-seen photos of this classic American TV show and its stars.
Think you know everything about Greg, Peter, Bobby, Marcia, Jan, Cindy, Mike, Carol, Alice-- and the people who played them? Think again! From drunken golf-cart races across the Paramount lot to make-out sessions in Tiger's doghouse, Barry tells the real Brady story, previously hidden behind the carefully-groomed facade of TV's favorite family. In 31 anecdote-packed chapters, Barry Williams takes readers from the beginnings of the show through its wildly successful run, and on through all the Brady Bunch reunions, wrapping up with a facscinating chapter on "Whatever Happened to..."
Also included in this pop culture classic is a play-by-play of every Brady Bunch episode, making Growing Up Brady the ultimate Brady Bunch collectible--as well as a delcious slice of Hollywood gossip.
The Bradys remain one of America's most loved and admired TV families. From 1969 through 1974, The Brady Bunch aired every Friday night on ABC. The show reamins one of TV's highest-rated shows, reaching 72 million viewers during its two evening repeats on Nick at Nite.
Customer Reviews:
True Brady Bunch Fans Might Want To Think Twice Before Reading This.......2007-02-02
The fact that there were some laughs in this book and it was interesting and well-written has to be balanced against the reality that tell-alls like this damage the nice fantasy that The Brady Bunch has been for thirty-some years. I don't mean to put Barry Williams down but I sort of wish I'd never read this book with its unhappy revelations and...too much information.
A walk through Bradyland.......2007-01-16
I really enjoyed listening to the audio version of Growing Up Brady: I Was a Teenage Greg by Barry Williams. It reminded me of how much I enjoyed watching the show while growing up. It was nice to hear that the kids were a "normal" group of kids in an abnormal situation-- which is possibly how they avoided many of the problems of other child stars, and also nice to hear that even though there were squabbles, the kids pretty much got along together and that they still think of each other as family. This is a very enjoyable book!
Even With It's Flaws I Still Love This Book!.......2006-01-04
I love The Brady Bunch, it is one of my favorite classic sitcoms and I bought and read Barry Williams Book, Growing Up Brady and I loved his stories, his accounts of playing Greg Brady and the episode guides, etc. Okay so there are some factual mistakes in the episode guides but the book was a fun and interesting read about one of the greatest family sitcoms of all time and I highly recommend it to all Brady Bunch fans and if you liked this book I also recommend the BradyMania Book by Elizabeth Moran. Gowing Up Brady and Brady Maina are both fun books!
About the many mistakes in the ep guide.......2005-10-09
Williams apparently mentions Tank Gates as being a boyfriend from Carol's college days. Actually Tank was from Carol's HIGH SCHOOL era! Dozens of other mistakes in this worthless, ill researched trash.
Great buy!.......2005-08-30
Brady Bunch fans will love this book. You get behind the seens details that you never new before. If you want to know what went on off the set, this will tell you about things that you could never find on the internet. Great book. I recommend this to all Brady fans out there.
Average customer rating:
- No dissappointment. Very entertaining and revealing.
|
Growing Up Brady: I Was a Teenage Greg/Audio Cassette
Barry Williams
Manufacturer: Publishing Mills
ProductGroup: Book
Binding: Audio Cassette
General
| Nonfiction
| Books on Cassette
| Audiobooks
| Formats
| Books
General
| Books on Cassette
| Audiobooks
| Formats
| Books
General
| Television
| Entertainment
| Subjects
| Books
ASIN: 1879371359 |
Customer Reviews:
No dissappointment. Very entertaining and revealing........1998-12-07
Barry Williams comes through with the gritty goods on the off-set romances between the on-set Brady kids! Also, lots of interesting and revealing tid-bits about the show and the cast. Williams's honest, no-holds-barred discussion of his early professional experiences is also entertaining. One disappointment is that the audio version doesn't address "Cyndi's near drowning in Hawaii". Nor does Williams' address some of the more controversial personal issues (revealed in the tabloids) of some of his castmates. But all in all, a resounding thumbs up!
Amazon.com
Computing hardware would have no value without software; software tells hardware what to do. Software therefore must have special authority within computing systems. All computer security problems stem from that fact, and Exploiting Software: How to Break Code shows you how to design your software so it's as resistant as possible to attack. Sure, everything's phrased in offensive terms (as instructions for the attacker, that is), but this book has at least as much value in showing designers what sorts of attacks their software will face (the book could serve as a checklist for part of a pre-release testing regimen). Plus, the clever reverse-engineering strategies that Greg Hoglund and Gary McGraw teach will be useful in many legitimate software projects. Consider this a recipe book for mayhem, or a compendium of lessons learned by others. It depends on your situation.
PHP programmers will take issue with the authors' blanket assessment of their language ("PHP is a study in bad security"), much of which seems based on older versions of the language that had some risky default behaviors--but those programmers will also double-check their servers' register_globals settings. Users of insufficiently patched Microsoft and Oracle products will worry about the detailed attack instructions this book contains. Responsible programmers and administrators will appreciate what amounts to documentation of attackers' rootkits for various operating systems, and will raise their eyebrows at the techniques for writing malicious code to unused EEPROM chips in target systems. --David Wall
Topics covered: How to make software fail, either by doing something it wasn't designed to do, or by denying its use to its rightful users. Techniques--including reverse engineering, buffer overflow, and particularly provision of unexpected input--are covered along with the tools needed to carry them out. A section on hardware viruses is detailed and frightening.
Customer Reviews:
Not as good as other works by these great authors, but still valuable.......2007-07-04
I read Exploiting Software (ES) last year but realized I hadn't reviewed it yet. Having read other books by these authors, like McGraw's Software Security and Hoglund's Rootkits, I realized ES was not as good as those newer books. At the time ES was published (2004) it continued to define the software exploitation genre begun in Building Secure Software. However, I don't think it's necessary to pay close attention to ES when newer books by McGraw and Hoglund are now available.
On the positive side, I appreciate three aspects of ES. First, I like the attention paid to attack patterns. This concept makes sense and should be used by other authors who want to describe a means to exploit a target. Second, I am impressed that ES features a whole chapter (5) on attacking client software. When ES was published, client-side attacks were just becoming popular. Discussing this problem shows great insights on the part of the authors. Third, several of the examples in ES are great case studies on exploiting software. When explained in sufficient detail they make for educational reading.
On the down side, I agree with several other reviewers that the book seems somewhat erratic. Attack patterns that are two sentences long are probably candidates for inclusion in a chart, not listed in the main text. I don't think the predictions found in ch 1 were necessary, and I think some of the criticism of detection methods in ch 6 border on the ignorant. I agree that perfect detection is impossible, but there are plenty of methods that work in the real world. They may not be real-time, but no intruder is perfectly stealthy in all aspects of an attack.
Regarding chapters 7 and 8, on buffer overflows and rootkits -- at 170 pages, those could almost have been their own book. The material doesn't seem to match the rest of the book, and it's obviously Hoglund's work. Add in a like-minded chapter on reverse engineering (3) at 74 pages and you definitely have a stand-alone book!
It's probably sufficient to read Building Secure Software, Software Security, and Rookits if you like the McGraw/Hoglund approach to attacking and defending software. Take a quick look at the attack pattern material to get a feel for that concept.
Want to fix things instead of break them?.......2006-03-03
One of the authors here.
Thinking carefully about how things break is a good idea. You should read this book and you should also read the Shellcoder's Handbook" by Litchfield et al. Pretend security nonsense crumbles under the weight of real attacks.
However, if you're interested in fixing the problem, get "Software Security: Building Security In". It's time to DO software security!
On the other hand, if you're looking for the ultimate weapon in the attacker's toolkit, go get "Rootkits."
In the end, the only smart move is a combo package of "think like and attacker" and "build like a pro." For your best all around bargain, get "The Software Security Library."
Why we use it for a graduate class.......2005-08-19
The one major strength of this book, from a computer science viewpoint, is its emphasis on "attack patterns". This systemization of these issues really differentiates this book from many of its competitors (which tend to be either the latest 500 hacks or descriptions of standards). Put simply CS is the study of algorithms, and this book fits nicely into that tradition.
great book.......2005-06-29
I am a relative novice to programming and exploitation however this book was truly a mind exciting experience. I found all of it's content to be useful, although I would say that this text is definately for an advanced user or someone quite motivated to understand the ideas presented as it delves into quite a bit of detail demanding advanced knowledge of several languages. Although there is a lot of info in this book, I would say that if you do not already know how to exploit a system in a basic form, you will be lost immediately as a step by step proceedure is not given but assumed to be known.
Fires up the hacker in me!.......2005-04-20
Anyone who's been in network security long enough will tell you that the current state of products and `solutions' to security problems are woefully inadequate.
Firewalls, intrusion detection systems, content filters and anti-virus solutions are all reactive technologies, and as a result, they fail to address the primary cause of security vulnerabilities.
This root cause is bad software. Viruses, worms and hackers exploit vulnerabilities in the design and logic of software applications to compromise, destroy and otherwise take control of important information. Once you accept this fact, you'll realize that the only path to good security is to write better code.
`Exploiting Software - How to Break Code' is a book that fires up the hacker in me. It does not aim to teach you about the latest scanning tool, instead, it teaches you how to find and exploit vulnerabilities in systems. While many of the ideas in the book (such as the omnipresent buffer overflow) are not new, there is simply no literary comparison to the treatment given to them in this book.
Application security is one of the highest regarded and specialized technical services in the security industry, and thus, finding people (let alone books) that delve in-depth into the topic is rare and refreshing. The first day I used this book, I was on an application security project. The target application was a distributed database application running on SQL server with a web front-end.
I happened to have this book along with me, and while reading through it, the section on equivalent requests was something I hadn't tried - sure enough, 20 minutes later I had full control of the application and a very good impression of this book.
I particularly like the conceptual sections of this book, especially their idea of `attack patterns' - generic scenarios that often lead to compromise in systems. A thorough study of all these attack patterns will leave you a much better analyst than when you started out, and it definitely pays off when it comes to testing.
The book is also chock-a-block full of code, something that other books don't have the guts to do. Better yet, we're not talking about `hello world' stuff here, while reading the excellent chapter on root kits I finally realized that the device driver code I was trying out was way over my head. That's something you like to find, because it gives you something to learn.
The art of reverse engineering, disassembly, writing IDA-Pro plugins, black / white and grey-box techniques, advanced payload creation on multiple architectures - this book has it all. The only thing I can possibly say against it is that this it caters to a niche audience.
If you're not a coder or seriously into security however, large parts of the book may be inaccessible to you. However if you're a hacker, security tester or application developer and you don't own a copy of this book, you're not reaching your full potential.
Customer Reviews:
Great advice for software developers.......2007-06-29
If your company has a web site, there are many people waiting to attack it and break into it.
In How to Break Web Software: Functional and Security Testing of Web Applications and Web Services, authors Mike Andrews and James Whittaker detail the myriad Web software exploits that attackers will attempt to carry out. The tools and techniques that can be used to fight against them are also detailed.
The book also includes a companion CD that contains all of the source code referenced in the book in addition to a number of testing tools. The authors include software code from an insecure Web site, which helps the reader get a real-world feel for the topics involved.
The authors conclude with a look at the last 50 years of software defects, showing that developers are not learning from the mistakes.
The authors are of the opinion that software quality is no better today than it was decades ago. And in some cases, it is worse.
The book helps drive home the importance of having developers think about writing secure code and testing it for flaws. It is a recommended read for IT professionals.
Short on content with too much padding.......2007-05-18
I was disappointed in this book. The actual content was pretty thin, and not very well written. Chapter 1 is a complete waste of time, and actually spends pages explaining what client/server means, what the Web is, and other things that are patently obvious to the supposed audience for this material. I found myself turning to the front to see if this book was written in 1997! You then get nine fairly short chapters with instructions on how to hack a website, more or less; followed by 50 pages of useless padding in the appendices including: an unrelated article co-authored by Whittaker for the IEEE, a detailed list of all the bugs present in their "sample application," and then descriptions of their recommended tools, all of which can easily be found on the Web without paying $22 for this book.
As another reviewer mentioned, there are many typos and other problems like incorrect illustrations, making the reader wonder if Addison-Wesley even employs a copy editor. Furthermore, I felt this book was inaccurately named and described. It's really more about rudimentary hacking and protecting your web application against hackers than web quality or web testing. A beginning web developer might do well to read this as a primer on how to create sites and applications with basic security, but as an experienced tester it was of limited use to me.
Wow!.......2007-04-13
I've been programming for over 10 years and thought that I had encountered it all. Uh ya, I was wrong. I'm amazed that a person can work with something for so long and yet still miss simple things like URL jumping. This is a great 32,000 foot view of web security (not a how to hack book) and covers what you should know if you are a web developer. Even if you alredy "know it all" this is a great read and excellent reference for creating check lists on projects and threats they may be succeptable to.
Fast international delivery.......2007-03-15
It was a good experience to purchase from Amazon and getting them delivered in India at my door-step. Order reached me ontime and is in good condition.
Thanks,
Samta
Very informative. If you develop web software it's a must-read.......2006-08-04
I recently finished reading How to Break Web Software: Functional and Security Testing of Web Applications and Web Services by Mike Andrews and James A. Whittaker. I, like many of you, develop web software for a living. I've always taken security seriously and occasionally sneered when I ran across examples of common mistakes. Having said that, this book was an eye opener for me.
The book covers common exploits such as bypassing input validation, SQL injection, and denial of service. There were also several types of attacks I hadn't really considered before. I won't list them here because someone would undoubtedly say, "I can't believe he didn't know about that one!" The authors cover 24 different types of attacks in all. The book also includes coverage of web privacy issues and security related to web services.
Finally, as icing on the cake, a CD is included that contains many tools that will find permanent spots in your arsenal. There are tools to do things like scan web servers for common exploits, mirror sites for local analysis, and check SSL cipher strengths. My favorites are the local proxies that will allow you to view and modify posts as they travel from the client and the server. I always knew I could do this, but didn't know how easy it is. The CD also contains the source code of an example site that includes many flaws for you to practice.
This book is written for software professionals to help them put the hackers out of business. So, it necessarily includes hacker techniques. If you develop or test web software, you should read this book before the hackers do. :-)
Customer Reviews:
Good ideas, but fails to follow through.......2006-03-07
The book categorizes software testing for security defects into attacks on software dependencies, user interfaces, design and implementation. The book focuses on 19 attacks (one being "overflow input buffers"), which form the core of the book. Parts 2 and 3 of the book explain when and how to apply each attack and what faults they find. Part 4 takes a more hands-on look at how to perform the testing.
In my opinion, the book is too dependent on the Holodeck 1.3 program provided on the CD. Rather than explaining security testing in a tool agnostic way, the book often simply explains how to use Holodeck to perform an attack. I use Linux and Holodeck is Windows only, so it was useless to me. Reviewer Yvonne Eu said the tool did not work in her test environment. Holodeck is currently maintained by Security Innovation who charge $1495 for a single user license, but they also offer a 30 day evaluation license. If the version on the CD does not work for you, these are your two options. The book is a lot less useful if Holodeck does not work for you, so bear this in mind.
The focus on Holodeck also limits the scope of the book. The use of other types of tools such as web proxies, port scanners and tools to exercise user interfaces is not adequately covered.
Finally, I was disappointed by chapter 6, which looks at security testing three applications: Windows Media Player 9.0, Mozilla 1.2.1 (for Windows), and OpenOffice 1.0.2 (for Linux). This is an ideal opportunity to dive down and show how security testing tools should be applied, common pitfalls, and hands-on techniques for finding security issues. Instead, the chapter only explains how attacks should be planned and goes no deeper.
If you are new to security testing and want an overview of some common types of tests that should be run, this book will be useful. If you are interested in using Holodeck for your testing, this book will also be useful. If you do not fall into these categories, there are other books which are a better fit. If you want more detail, I recommend trying one of the Hacking Exposed series.
Holodeck rules! - Does it?.......2005-10-28
The whole book feels like a promotion for Holodeck tool. Some of the chapters are very straightforward: boot your AUT (Application Under Test) from Holodeck and see what happens. However, the version of the tool supplied with the book isn't supported by anybody and, sure enough, it doesn't work with my AUT. The supported one is above $1K for single user licence...
Though as much as I appreciate the general ideas about blackbox security testing Whittaker is voicing in this book, I feel it's just not enough there for its price. :(
Security testing for QA folks, also good for infosec folks.......2004-09-23
I'm the type of person who won't buy a tech book unless it's worth reading and referring to, and it didn't take much skimming to realize this was going to be worth it. My opinion hasn't changed since finishing it. I had a specific need for information on non-web application penetration (security) testing and I was surprised to find exactly what I needed in this book, and in a short, easy-to-read package including a CD with two unique tools to help apply what it teaches.
If you're a software tester or in the software quality assurance field, especially if you're interested in security, you need to read this book as it will likely be an eye-opener. It's not full of shocking anecdotes to scare developers into writing better software, it's a handbook of what to look for when testing software after you think you've done all your testing, and at the same time gives developers and project managers good information on how to design, code, and state requirements better.
If you're a security person, especially the burgeoning field of application security, you might also find this book pretty enlightining. Everyone's heard of penetration testing and vulnerability assessment, but typically only in the context of attacking remotely over a network. This book shows you how to attack the (more traditional?) software on your local machine, but not to the level of detail or geekiness of "shellcoding."
While I feel the cover price is a bit steep for such a thin book, especially given the amount of "filler" like illustrations, blank pages, figures, etc., the content is superb and the writing style makes it easy to read. I also appreciate that the points made and examples used tend to get me thinking and I'm able to apply the concepts right away--maybe it's just my "tinkerer" mindset but this book seems to encourage the reader to think outside the box and experiment, which I like. I don't give many 5-star ratings but I think this book deserves it.
Whittaker strikes again!.......2004-05-31
The software community has been awaiting for a book like this. It's a almost perfect intro to software security concepts. Again, Whittaker keeps it low in pages and words. In my opinion, the way books should be written (except ones purely theoretical).
Once again Whittaker approachs is hands-on examples. Even if some examples don't apply to modern software the idea behind you is to get you thinking. I've applied the techniques in this book with extremely great results.
Excellent continuation or Whittaker's earlier book.......2004-03-07
James Whittaker has taken the approach and the tools he introduced in "How to Break Software: A Practical Guide to Testing" (ISBN 0201796198), and has teamed with coauthor Herbert Thompson to adapt them to security testing. In this book the software under test (or attack, since that is the underlying approach) is primarily in the Microsoft environment. That the principles can be applied to any operating system or environment is evident in one scenario where Linux-based OpenOffice is attacked. The the fault model provided early in the book can form the basis for any software test strategy with a goal to uncover and exploit vulnerabilities.
The approach itself is to create a plan, then systematically attack. The areas of vulnerability covered include unanticipated input scenarios (which, even after decades, is still an exposure in too many applications and operating systems), find and attack design flaws and implementation anomalies, and leave no potential vulnerability untested. Among these are the usual exposed ports and default names; however, there are exploits based on data, time stamping and other less common areas that are overlooked by testing professionals - and that is one of the main audiences of this book.
While the techniques and the approach in this book are sound, I would have liked the attacks presented as formal test cases, which would be more meaningful to the testing professionals who will benefit the most from this book. However, the authors do introduce the concept of security testing as an element of QA, adding to the small (but hopefully growing) body of knowledge to be used by QA. I recommend this book, as well as "Exploiting Software: How to Break Code" (ISBN 0201786958) as two books that should be read and used by software testing practitioners. The information combined in these books will-if put into practice-significantly improve the quality and security of software that is released into production.
Books:
- History: Fiction or Science? (Chronology, No. 1)
- History: Fiction or Science? (Chronology, No. 1)
- Hood and Bismarck
- How I Learned to Cook: Culinary Educations from the World's Greatest Chefs
- How to Watch TV News
- Income Tax Fundamentals, 2007 Edition (Income Tax Fundamentals)
- Life After Television
- Litigation Support Report Writing: Accounting, Finance, and Economic Issues
- Mac OS X Bible, Panther Edition
- Macromedia Flash MX 2004 Bible
Books Index
Books Home
Recommended Books
- A Feast for Crows
- The Cestus Deception
- History: Fiction or Science
- Mudslingers: The Top 25 Negative Political Campaigns of All Time Countdown from No. 25 to No. 1
- History: Fiction or Science
- Rich Dad's Real Estate Advantages: Tax and Legal Secrets of Successful Real Estate Investors
- Shroud for a Nightingale
- Some Place Like Home: Using Design Psychology to Create Ideal Places
- Jim Henson: The Works - The Art, the Magic, the Imagination
- Advances in Comparative and Environmental Physiology
