<?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: Amending my F0rb1dd3n Network Review</title>
	<atom:link href="http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/</link>
	<description></description>
	<lastBuildDate>Thu, 05 Jan 2012 11:44:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Plagiarism and the State of Infosec Publishing &#124; InfoSec Reviews Blog</title>
		<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/#comment-819</link>
		<dc:creator>Plagiarism and the State of Infosec Publishing &#124; InfoSec Reviews Blog</dc:creator>
		<pubDate>Mon, 22 Aug 2011 13:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=628#comment-819</guid>
		<description>[...] ‘This was an honest mistake and I sincerely apologize for any miscommunication. I hope that the correct and proper citations can be added soon and that all questions regarding copyright and plagiarism issues can be resolved. I hope the book can still be enjoyed as a valuable contribution to the information security community and I hope it will go on to fulfill its objective in reaching anyone who desires to learn more about hacking and security. I want to specifically apologize to Jayson, Kent, Syngress, Rachel, Angelina, all the readers, reviewers, and others who have taken offense. I want to fix this and I sincerely appreciate everyone&#8217;s positive support!’  (http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/).  [...]</description>
		<content:encoded><![CDATA[<p>[...] ‘This was an honest mistake and I sincerely apologize for any miscommunication. I hope that the correct and proper citations can be added soon and that all questions regarding copyright and plagiarism issues can be resolved. I hope the book can still be enjoyed as a valuable contribution to the information security community and I hope it will go on to fulfill its objective in reaching anyone who desires to learn more about hacking and security. I want to specifically apologize to Jayson, Kent, Syngress, Rachel, Angelina, all the readers, reviewers, and others who have taken offense. I want to fix this and I sincerely appreciate everyone&#8217;s positive support!’  (<a href="http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/" rel="nofollow">http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/</a>).  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: (More) (Massive) Plagiarism in Security Books &#171; McGrew Security Blog</title>
		<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/#comment-818</link>
		<dc:creator>(More) (Massive) Plagiarism in Security Books &#171; McGrew Security Blog</dc:creator>
		<pubDate>Fri, 20 Aug 2010 00:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=628#comment-818</guid>
		<description>[...] review copy arrived, and I immediately got the same feeling as I got when I took a careful look at the original revision of Dissecting the Hack: that the listed authors of the book did not create the content they were presenting as their own. [...]</description>
		<content:encoded><![CDATA[<p>[...] review copy arrived, and I immediately got the same feeling as I got when I took a careful look at the original revision of Dissecting the Hack: that the listed authors of the book did not create the content they were presenting as their own. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fixer</title>
		<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/#comment-817</link>
		<dc:creator>fixer</dc:creator>
		<pubDate>Mon, 21 Jun 2010 14:32:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=628#comment-817</guid>
		<description>Hmmf, I wonder if Jayson and his dc405 crew remember me....LOL. Im sure they remember calling my work and trying to get me fired, fucking whitehat cunts.</description>
		<content:encoded><![CDATA[<p>Hmmf, I wonder if Jayson and his dc405 crew remember me&#8230;.LOL. Im sure they remember calling my work and trying to get me fired, fucking whitehat cunts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian J Koerner</title>
		<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/#comment-816</link>
		<dc:creator>Brian J Koerner</dc:creator>
		<pubDate>Thu, 19 Nov 2009 04:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=628#comment-816</guid>
		<description>For several years I have worked in one way or another with Syngress, Laura Colantonia, Angelina, Rachel and as far back as Amorette Pederson (sp).  I have watched Syngress grow, their processes improve and them move into a respectable publisher of information security works.  This is unfortunate and while there is software out there to detect this, the responsibility lies with the author, in this case the technical editor.  I have known Jayson Street and Kent Nabors and their works for several years and they are top notch.  I believe them and my heart goes out to them during this tough time for them.  As a former Chief Security Engineer at EDS and author myself, I would expect more from a technical editor in the information security community.  That said, the rest of us in the community need to rally behind Jayson and Kent and provide them the support that they deserve as being part of our community and behind Syngress for bringing us great information security content over many years - or better yet, allowing US to contribute to that content to further our work in the information security space.  I believe that Jayson, Kent and Syngress are dealing with this issue in an appropriate and positive manner, doing the best that they can to correct the actions of someone that they trusted.

Good luck guys.  I wish you the best.

Regards,

Brian

P.S  Hats off to Wesley for bringing to light the issue so that it could be dealt with appropriately.</description>
		<content:encoded><![CDATA[<p>For several years I have worked in one way or another with Syngress, Laura Colantonia, Angelina, Rachel and as far back as Amorette Pederson (sp).  I have watched Syngress grow, their processes improve and them move into a respectable publisher of information security works.  This is unfortunate and while there is software out there to detect this, the responsibility lies with the author, in this case the technical editor.  I have known Jayson Street and Kent Nabors and their works for several years and they are top notch.  I believe them and my heart goes out to them during this tough time for them.  As a former Chief Security Engineer at EDS and author myself, I would expect more from a technical editor in the information security community.  That said, the rest of us in the community need to rally behind Jayson and Kent and provide them the support that they deserve as being part of our community and behind Syngress for bringing us great information security content over many years &#8211; or better yet, allowing US to contribute to that content to further our work in the information security space.  I believe that Jayson, Kent and Syngress are dealing with this issue in an appropriate and positive manner, doing the best that they can to correct the actions of someone that they trusted.</p>
<p>Good luck guys.  I wish you the best.</p>
<p>Regards,</p>
<p>Brian</p>
<p>P.S  Hats off to Wesley for bringing to light the issue so that it could be dealt with appropriately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Security Justice &#187; Blog Archive &#187; Security Justice Special Edition &#8211; Jayson Street and Dissecting the hack: the f0rb1dd3n network</title>
		<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/#comment-815</link>
		<dc:creator>Security Justice &#187; Blog Archive &#187; Security Justice Special Edition &#8211; Jayson Street and Dissecting the hack: the f0rb1dd3n network</dc:creator>
		<pubDate>Fri, 30 Oct 2009 14:18:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=628#comment-815</guid>
		<description>[...] controversy regarding the plagiarism by the technical editor of the book.  You can check out the book review by Wesley McGrew that is mentioned in the podcast.  Wesley was also our guest on Episode 18 talking about the book [...]</description>
		<content:encoded><![CDATA[<p>[...] controversy regarding the plagiarism by the technical editor of the book.  You can check out the book review by Wesley McGrew that is mentioned in the podcast.  Wesley was also our guest on Episode 18 talking about the book [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StatlerAndWaldorf</title>
		<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/#comment-814</link>
		<dc:creator>StatlerAndWaldorf</dc:creator>
		<pubDate>Sun, 25 Oct 2009 04:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=628#comment-814</guid>
		<description>@Chris

Trust me, I&#039;m all for doing positive things instead of bitching. But don&#039;t try to tell me that&#039;s what this is.

You really want to call this a community thing? Fine. Go start a wiki and make a peer reviewed &quot;hacker fiction&quot; book, and make it free to everyone. That&#039;s community, sir.

Doing free tech edits to make up for a personally and professionally embarrassing series of cockups and put more money in somebody&#039;s pocket?

That&#039;s not my community, man. Maybe it&#039;s yours.

While I&#039;m being a dickweed, I wonder how many people surrounding this drama mill have deals for other books in the series in the works? Hrrm. Time to save the franchise, eh?</description>
		<content:encoded><![CDATA[<p>@Chris</p>
<p>Trust me, I&#8217;m all for doing positive things instead of bitching. But don&#8217;t try to tell me that&#8217;s what this is.</p>
<p>You really want to call this a community thing? Fine. Go start a wiki and make a peer reviewed &#8220;hacker fiction&#8221; book, and make it free to everyone. That&#8217;s community, sir.</p>
<p>Doing free tech edits to make up for a personally and professionally embarrassing series of cockups and put more money in somebody&#8217;s pocket?</p>
<p>That&#8217;s not my community, man. Maybe it&#8217;s yours.</p>
<p>While I&#8217;m being a dickweed, I wonder how many people surrounding this drama mill have deals for other books in the series in the works? Hrrm. Time to save the franchise, eh?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nickerson</title>
		<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/#comment-813</link>
		<dc:creator>Nickerson</dc:creator>
		<pubDate>Sun, 25 Oct 2009 00:00:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=628#comment-813</guid>
		<description>I am not saying you should be &quot;tripping all over yourself&quot;
I am saying.. that this community thing should be about fixing issues. Not just identifying them and walking on. Security is not just about finding the bugs.. its about teaching others how to fix them.</description>
		<content:encoded><![CDATA[<p>I am not saying you should be &#8220;tripping all over yourself&#8221;<br />
I am saying.. that this community thing should be about fixing issues. Not just identifying them and walking on. Security is not just about finding the bugs.. its about teaching others how to fix them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StatlerAndWaldorf</title>
		<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/#comment-812</link>
		<dc:creator>StatlerAndWaldorf</dc:creator>
		<pubDate>Sat, 24 Oct 2009 01:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=628#comment-812</guid>
		<description>@Chris

I just don&#039;t get how this is being spun as some kind of community thing. We&#039;re not talking about a collaborative project like MSF or nmap, and we&#039;re not talking about something that&#039;s going into Phrack, or 2600, or Uninformed, or a thousand other plausibly &quot;community&quot; outlets.

We&#039;re talking about a commercial book, published by a commercial publisher, with some dudes&#039; names on it. Written, at least kinda, by those dudes, for money. And at least one of those dudes screwed up, *hard*, as did their publisher. Why exactly should I be tripping all over myself to help them fix that?</description>
		<content:encoded><![CDATA[<p>@Chris</p>
<p>I just don&#8217;t get how this is being spun as some kind of community thing. We&#8217;re not talking about a collaborative project like MSF or nmap, and we&#8217;re not talking about something that&#8217;s going into Phrack, or 2600, or Uninformed, or a thousand other plausibly &#8220;community&#8221; outlets.</p>
<p>We&#8217;re talking about a commercial book, published by a commercial publisher, with some dudes&#8217; names on it. Written, at least kinda, by those dudes, for money. And at least one of those dudes screwed up, *hard*, as did their publisher. Why exactly should I be tripping all over myself to help them fix that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StatlerAndWaldorf</title>
		<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/#comment-811</link>
		<dc:creator>StatlerAndWaldorf</dc:creator>
		<pubDate>Sat, 24 Oct 2009 01:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=628#comment-811</guid>
		<description>&quot;Welcome to hacker fiction-like SciFi, but you don&#039;t get to make the good stuff up.&quot;
-Dan Kaminsky (From the back cover)

... You do, however, get to randomly copypasta junk from the Internet and have it make it past fact-checking and into print. Gaah. I should have listened to my Mom and went into accountancy. Every time I think we&#039;ve perfected the Security Charlatan, someone comes along and makes a better one, like some sort of Terminator that keeps reengineering itself and can&#039;t be killed. Bravo, Fritz, bravo.</description>
		<content:encoded><![CDATA[<p>&#8220;Welcome to hacker fiction-like SciFi, but you don&#8217;t get to make the good stuff up.&#8221;<br />
-Dan Kaminsky (From the back cover)</p>
<p>&#8230; You do, however, get to randomly copypasta junk from the Internet and have it make it past fact-checking and into print. Gaah. I should have listened to my Mom and went into accountancy. Every time I think we&#8217;ve perfected the Security Charlatan, someone comes along and makes a better one, like some sort of Terminator that keeps reengineering itself and can&#8217;t be killed. Bravo, Fritz, bravo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wesley McGrew</title>
		<link>http://www.mcgrewsecurity.com/2009/10/16/amending-my-f0rb1dd3n-network-review/#comment-810</link>
		<dc:creator>Wesley McGrew</dc:creator>
		<pubDate>Thu, 22 Oct 2009 20:58:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcgrewsecurity.com/?p=628#comment-810</guid>
		<description>Yes, I did offer to tech review the second volume of this series, even before all of this mess, since I like Jayson and I think it&#039;s a really cool project.  I have also offered to provide content for the reconstructed STAR section, and I hope they take me up on it.

Thanks for the comment.  You&#039;re right on the mark with it.</description>
		<content:encoded><![CDATA[<p>Yes, I did offer to tech review the second volume of this series, even before all of this mess, since I like Jayson and I think it&#8217;s a really cool project.  I have also offered to provide content for the reconstructed STAR section, and I hope they take me up on it.</p>
<p>Thanks for the comment.  You&#8217;re right on the mark with it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

