<?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: SecMalloc: c-lib to prevent malloc&#8217;ed memory from swapping.</title>
	<atom:link href="http://jessenoller.com/2007/08/31/secmalloc-c-lib-to-prevent-malloced-memory-from-swapping/feed/" rel="self" type="application/rss+xml" />
	<link>http://jessenoller.com/2007/08/31/secmalloc-c-lib-to-prevent-malloced-memory-from-swapping/</link>
	<description>python, programming and other things</description>
	<pubDate>Thu, 24 Jul 2008 05:42:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Calvin Spealman</title>
		<link>http://jessenoller.com/2007/08/31/secmalloc-c-lib-to-prevent-malloced-memory-from-swapping/#comment-3819</link>
		<dc:creator>Calvin Spealman</dc:creator>
		<pubDate>Sat, 01 Sep 2007 17:26:32 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/2007/08/31/secmalloc-c-lib-to-prevent-malloced-memory-from-swapping/#comment-3819</guid>
		<description>I think the string types need a specialized allocator anyway, so creating some way to secure that would be an obvious next move. The question is how an interface from python would look. A string is immutable and anywhere they are created would have to say "make this secure" because you can't make it secure after its created. It posses some problems, that maybe could only be solved with a string control character, as we use u and r today.</description>
		<content:encoded><![CDATA[<p>I think the string types need a specialized allocator anyway, so creating some way to secure that would be an obvious next move. The question is how an interface from python would look. A string is immutable and anywhere they are created would have to say &#8220;make this secure&#8221; because you can&#8217;t make it secure after its created. It posses some problems, that maybe could only be solved with a string control character, as we use u and r today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jesse</title>
		<link>http://jessenoller.com/2007/08/31/secmalloc-c-lib-to-prevent-malloced-memory-from-swapping/#comment-3602</link>
		<dc:creator>jesse</dc:creator>
		<pubDate>Fri, 31 Aug 2007 17:08:26 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/2007/08/31/secmalloc-c-lib-to-prevent-malloced-memory-from-swapping/#comment-3602</guid>
		<description>Encrypting the swap partition is less than desirable given the requirements of doing so - you need to be root, modify and reboot the system. This is for one off mallocs for the runtime of a program/application.</description>
		<content:encoded><![CDATA[<p>Encrypting the swap partition is less than desirable given the requirements of doing so - you need to be root, modify and reboot the system. This is for one off mallocs for the runtime of a program/application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://jessenoller.com/2007/08/31/secmalloc-c-lib-to-prevent-malloced-memory-from-swapping/#comment-3575</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 31 Aug 2007 16:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/2007/08/31/secmalloc-c-lib-to-prevent-malloced-memory-from-swapping/#comment-3575</guid>
		<description>Or you could encrypt the swap partition...</description>
		<content:encoded><![CDATA[<p>Or you could encrypt the swap partition&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
