<?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: Educational Hacking?</title>
	<atom:link href="http://www.computerdefense.org/2007/09/educational-hacking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.computerdefense.org/2007/09/educational-hacking/</link>
	<description>Sharing my thoughts with the world.</description>
	<lastBuildDate>Mon, 26 Jul 2010 03:10:24 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: princess of antiquity</title>
		<link>http://www.computerdefense.org/2007/09/educational-hacking/comment-page-1/#comment-28869</link>
		<dc:creator>princess of antiquity</dc:creator>
		<pubDate>Mon, 01 Oct 2007 09:36:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.computerdefense.org/?p=391#comment-28869</guid>
		<description>Personally, I don&#039;t believe that it is essential or even needed to do this kind of experiments. I still think that it is still better to learn how to design a good security rather than protecting it by blocking known attacks. We don&#039;t need to know all of them, because at the rate they are growing, we&#039;ll never finish. Instead, I think that we just have to assume that its there. &#039;Coz if its not meant to be hackable, then, it shouldn&#039;t be. 

But, hey, what do I know, I&#039;m just a student. ^_^</description>
		<content:encoded><![CDATA[<p>Personally, I don&#8217;t believe that it is essential or even needed to do this kind of experiments. I still think that it is still better to learn how to design a good security rather than protecting it by blocking known attacks. We don&#8217;t need to know all of them, because at the rate they are growing, we&#8217;ll never finish. Instead, I think that we just have to assume that its there. &#8216;Coz if its not meant to be hackable, then, it shouldn&#8217;t be. </p>
<p>But, hey, what do I know, I&#8217;m just a student. ^_^</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JaceTheAce</title>
		<link>http://www.computerdefense.org/2007/09/educational-hacking/comment-page-1/#comment-28357</link>
		<dc:creator>JaceTheAce</dc:creator>
		<pubDate>Wed, 26 Sep 2007 22:30:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.computerdefense.org/?p=391#comment-28357</guid>
		<description>I&quot;ve seen this alot lately - the subject and the practicing of. The coverage shows the anxiousness society has with public open malicious development.
i just spent the past days at large conference and even the Presenters of the study session were displaying and encouraging &#039;engaging&#039; the malware situation deeper: like so. 
Unfortunately no obvious answer yet with the fine balance between Tool and Instigator. They&#039;ll just have to do like you said, test these each individually in court with a nonpartisan Judge.
I believe the pressure of the sincerity people have for this subject maintains honesty well enough for the time being.
It becomes blatantly obvious if people take their Home-Malicious tools though and release the self controlling and self-deciding destroyer on its own. 

i Find i learn and take in new programs/coding the best when i can get my hands on the source code- then run it and debug, then go back, change some values, objects. Later - prolly inject/change/add/modify the program to learn more again. 
To bad for this subject the program - is malicious related.</description>
		<content:encoded><![CDATA[<p>I&#8221;ve seen this alot lately &#8211; the subject and the practicing of. The coverage shows the anxiousness society has with public open malicious development.<br />
i just spent the past days at large conference and even the Presenters of the study session were displaying and encouraging &#8216;engaging&#8217; the malware situation deeper: like so.<br />
Unfortunately no obvious answer yet with the fine balance between Tool and Instigator. They&#8217;ll just have to do like you said, test these each individually in court with a nonpartisan Judge.<br />
I believe the pressure of the sincerity people have for this subject maintains honesty well enough for the time being.<br />
It becomes blatantly obvious if people take their Home-Malicious tools though and release the self controlling and self-deciding destroyer on its own. </p>
<p>i Find i learn and take in new programs/coding the best when i can get my hands on the source code- then run it and debug, then go back, change some values, objects. Later &#8211; prolly inject/change/add/modify the program to learn more again.<br />
To bad for this subject the program &#8211; is malicious related.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kurt wismer</title>
		<link>http://www.computerdefense.org/2007/09/educational-hacking/comment-page-1/#comment-27959</link>
		<dc:creator>kurt wismer</dc:creator>
		<pubDate>Sun, 23 Sep 2007 22:03:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.computerdefense.org/?p=391#comment-27959</guid>
		<description>&quot;You create the virus via point and click… picking specific vulnerabilities, actions and packing processes. Afterwards you run the virus and attempt to work backwards to the initial settings you chose. You watch it’s actions with a debugger and a sniffer. I would say this is definitely educational and there’s a good chance many people in InfoSec did this sort of thing when they were first playing with security.&quot;

indeed, i&#039;m sure many in infosec and even outside of infosec did this sort of thing... i believe sarah gordon covered this set in her paper &quot;the generic virus writer II&quot;... 3 guesses why that set warranted mention and the first 2 don&#039;t count...

if you must experiment with viruses, experiment with ones that already exist, not ones you make...</description>
		<content:encoded><![CDATA[<p>&#8220;You create the virus via point and click… picking specific vulnerabilities, actions and packing processes. Afterwards you run the virus and attempt to work backwards to the initial settings you chose. You watch it’s actions with a debugger and a sniffer. I would say this is definitely educational and there’s a good chance many people in InfoSec did this sort of thing when they were first playing with security.&#8221;</p>
<p>indeed, i&#8217;m sure many in infosec and even outside of infosec did this sort of thing&#8230; i believe sarah gordon covered this set in her paper &#8220;the generic virus writer II&#8221;&#8230; 3 guesses why that set warranted mention and the first 2 don&#8217;t count&#8230;</p>
<p>if you must experiment with viruses, experiment with ones that already exist, not ones you make&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
