<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Book Review:</title>
	<atom:link href="http://paco.to/2009/book-review/feed" rel="self" type="application/rss+xml" />
	<link>http://paco.to/2009/book-review</link>
	<description>My Random Musings and Rants</description>
	<lastBuildDate>Thu, 17 Jun 2010 16:12:46 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ari Takanen</title>
		<link>http://paco.to/2009/book-review/comment-page-1#comment-1634</link>
		<dc:creator>Ari Takanen</dc:creator>
		<pubDate>Fri, 24 Apr 2009 18:47:55 +0000</pubDate>
		<guid isPermaLink="false">http://paco.to/?p=316#comment-1634</guid>
		<description>Thanks Paco! I added a link to the review on the book web site: http://www.fuzz-test.com/

Some comments on the &quot;Not-So-Good&quot;:

Motherhood and apple pie things were included so that the book can be used as a course book. For some unlucky (or reluctant to learn) people, just giving links will not help much.

Product comparisons were actually originally intended to be scattered around, to teach some other aspect in relation to fuzzing, rather than just focus too much on data that will be outdated fast. One chapter was still dedicated to just plain product comparison (thanks to Charlie Miller). Do not take that chapter as a fact though, as most open source and commercial tools develop rather fast, whereas others have been already abandoned for some reason. Things really develop fast in this market. For example, Codenomicon tools used in the comparison were already previous generation when the book came out.

Fuzzing is &quot;über alles&quot;! At least for the intended audience. The guys who do have access to source code (which does not usually include security auditors and testers) definitely need to look at static analysis also. That was out of the scope for this book.

In short, in everything we did in the book, the purpose was that the book is equally valid five or ten years from now.</description>
		<content:encoded><![CDATA[<p>Thanks Paco! I added a link to the review on the book web site: <a href="http://www.fuzz-test.com/" rel="nofollow">http://www.fuzz-test.com/</a></p>
<p>Some comments on the &#8220;Not-So-Good&#8221;:</p>
<p>Motherhood and apple pie things were included so that the book can be used as a course book. For some unlucky (or reluctant to learn) people, just giving links will not help much.</p>
<p>Product comparisons were actually originally intended to be scattered around, to teach some other aspect in relation to fuzzing, rather than just focus too much on data that will be outdated fast. One chapter was still dedicated to just plain product comparison (thanks to Charlie Miller). Do not take that chapter as a fact though, as most open source and commercial tools develop rather fast, whereas others have been already abandoned for some reason. Things really develop fast in this market. For example, Codenomicon tools used in the comparison were already previous generation when the book came out.</p>
<p>Fuzzing is &#8220;über alles&#8221;! At least for the intended audience. The guys who do have access to source code (which does not usually include security auditors and testers) definitely need to look at static analysis also. That was out of the scope for this book.</p>
<p>In short, in everything we did in the book, the purpose was that the book is equally valid five or ten years from now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
