<?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"
	>
<channel>
	<title>Comments on: Speculations on Teaching Secure Programming</title>
	<atom:link href="http://www.cerias.purdue.edu/weblogs/pmeunier/general/post-140/speculations-on-teaching-secure-programming/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cerias.purdue.edu/weblogs/pmeunier/general/post-140/speculations-on-teaching-secure-programming/</link>
	<description>Privacy, Security and Information Assurance issues</description>
	<pubDate>Mon, 12 May 2008 13:59:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Controlled Flight Into Terrain &#8250; Pascal Meunier on Teaching Secure Programming</title>
		<link>http://www.cerias.purdue.edu/weblogs/pmeunier/general/post-140/speculations-on-teaching-secure-programming/#comment-209340</link>
		<dc:creator>Controlled Flight Into Terrain &#8250; Pascal Meunier on Teaching Secure Programming</dc:creator>
		<pubDate>Thu, 17 Apr 2008 13:45:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.cerias.purdue.edu/weblogs/pmeunier/general/post-140/speculations-on-teaching-secure-programming/#comment-209340</guid>
		<description>[...] CERIAS Weblogs » Speculations on Teaching Secure Programming  Security is somewhat of a habit, an attitude, a way of thinking and life. You won’t become a secure programmer just because you learned of a new vulnerability, exploit or security trick today, although it may help and have a cumulative effect.   This was written by irving. Posted on Thursday, April 17, 2008, at 9:45 am. Filed under Software. Bookmark the permalink. Follow comments here with the RSS feed. Post a comment or leave a trackback. [...]</description>
		<content:encoded><![CDATA[<p>[...] CERIAS Weblogs » Speculations on Teaching Secure Programming  Security is somewhat of a habit, an attitude, a way of thinking and life. You won’t become a secure programmer just because you learned of a new vulnerability, exploit or security trick today, although it may help and have a cumulative effect.   This was written by irving. Posted on Thursday, April 17, 2008, at 9:45 am. Filed under Software. Bookmark the permalink. Follow comments here with the RSS feed. Post a comment or leave a trackback. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephan</title>
		<link>http://www.cerias.purdue.edu/weblogs/pmeunier/general/post-140/speculations-on-teaching-secure-programming/#comment-191339</link>
		<dc:creator>Stephan</dc:creator>
		<pubDate>Wed, 27 Feb 2008 16:05:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.cerias.purdue.edu/weblogs/pmeunier/general/post-140/speculations-on-teaching-secure-programming/#comment-191339</guid>
		<description>Great thoughts!  I think this also reflects on a common discussion I've come across before that university CS departments seemed to be more concerned with churning out the "factory programming drones" than really teaching computer science/technology as they once did.  There is an entire art and creative aspect to development that seems to be lost these days in the effort to push out more Java programmers with minimal skill sets.

Perhaps there is an underlying Java programmer quota that each Uni must meet yearly! :)

One thing to note about programmers with a lack of security knowledge (or even sloppy/lazy coding habits) is that they present an enormous liability for their current/future employer(s).  A Uni without at least some solid security training is really doing a disservice to the student, his/her potential employers and the industry itself.</description>
		<content:encoded><![CDATA[<p>Great thoughts!  I think this also reflects on a common discussion I&#8217;ve come across before that university CS departments seemed to be more concerned with churning out the &#8220;factory programming drones&#8221; than really teaching computer science/technology as they once did.  There is an entire art and creative aspect to development that seems to be lost these days in the effort to push out more Java programmers with minimal skill sets.</p>
<p>Perhaps there is an underlying Java programmer quota that each Uni must meet yearly! <img src='http://www.cerias.purdue.edu/weblogs/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>One thing to note about programmers with a lack of security knowledge (or even sloppy/lazy coding habits) is that they present an enormous liability for their current/future employer(s).  A Uni without at least some solid security training is really doing a disservice to the student, his/her potential employers and the industry itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura Bowser</title>
		<link>http://www.cerias.purdue.edu/weblogs/pmeunier/general/post-140/speculations-on-teaching-secure-programming/#comment-169939</link>
		<dc:creator>Laura Bowser</dc:creator>
		<pubDate>Tue, 15 Jan 2008 18:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.cerias.purdue.edu/weblogs/pmeunier/general/post-140/speculations-on-teaching-secure-programming/#comment-169939</guid>
		<description>I've encountered this in my limited teaching as a TA and later as a teacher to corporate "students".  The "wow" and flash of showing the bad things only goes so far.  And the students have to understand *why* things are bad.  (I've had some students ask me why it was bad for an exploit to get administrative privileges).  Unfortunately, most computer science/development classes aren't teaching security, they're teaching coding/development. 

I think there needs to be a freshman class on security in general, and required by *all* students, not just those in technical degrees.  It could cover basic things like not sharing your password all the way up to showing exploits.  At that point, these students have a base to work from.  

Just because someone wants to be a developer doesn't mean they care about security.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve encountered this in my limited teaching as a TA and later as a teacher to corporate &#8220;students&#8221;.  The &#8220;wow&#8221; and flash of showing the bad things only goes so far.  And the students have to understand *why* things are bad.  (I&#8217;ve had some students ask me why it was bad for an exploit to get administrative privileges).  Unfortunately, most computer science/development classes aren&#8217;t teaching security, they&#8217;re teaching coding/development. </p>
<p>I think there needs to be a freshman class on security in general, and required by *all* students, not just those in technical degrees.  It could cover basic things like not sharing your password all the way up to showing exploits.  At that point, these students have a base to work from.  </p>
<p>Just because someone wants to be a developer doesn&#8217;t mean they care about security.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
