<?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 for Green Spring Design, LLC</title>
	<atom:link href="http://greenspringdesign.com/blog/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://greenspringdesign.com/blog</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Wed, 08 Sep 2010 10:31:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on Mercurial and the case for signatures by Jeremy</title>
		<link>http://greenspringdesign.com/blog/?p=11#comment-47</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Mon, 16 Mar 2009 22:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://greenspringdesign.com/blog/?p=11#comment-47</guid>
		<description>Monotone looks interesting - thanks for the suggestion.  

I want to do this for the same reason that /var/log/* is not world-writeable.   Just because someone is trusted to log in doesn't mean they should have write-access to the log, which is used to analyze security post-facto if something happens.  

The identification and logging scheme should be one 'security level' higher than users.  For unix logins, it's done with file permissions.  Ditto for SVN and CVS.  For a DVCS, it likely has to be done with crypto if at all.</description>
		<content:encoded><![CDATA[<p>Monotone looks interesting - thanks for the suggestion.  </p>
<p>I want to do this for the same reason that /var/log/* is not world-writeable.   Just because someone is trusted to log in doesn&#8217;t mean they should have write-access to the log, which is used to analyze security post-facto if something happens.  </p>
<p>The identification and logging scheme should be one &#8217;security level&#8217; higher than users.  For unix logins, it&#8217;s done with file permissions.  Ditto for SVN and CVS.  For a DVCS, it likely has to be done with crypto if at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mercurial and the case for signatures by Jakub Narębski</title>
		<link>http://greenspringdesign.com/blog/?p=11#comment-25</link>
		<dc:creator>Jakub Narębski</dc:creator>
		<pubDate>Fri, 06 Mar 2009 13:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://greenspringdesign.com/blog/?p=11#comment-25</guid>
		<description>First, for commits to appear in canonical repository they have to be either pulled by someone with access rights (assuming that he/she trusts the repository he/she pulls from), or have rights to push to repository (with hooks providing additional access control).

Second, if you are really paranoid like IPsec guys, and require for each comit to be signed, why not use &lt;a href="http://monotone.ca/" rel="nofollow"&gt;Mototone&lt;/a&gt; distributed version control system?</description>
		<content:encoded><![CDATA[<p>First, for commits to appear in canonical repository they have to be either pulled by someone with access rights (assuming that he/she trusts the repository he/she pulls from), or have rights to push to repository (with hooks providing additional access control).</p>
<p>Second, if you are really paranoid like IPsec guys, and require for each comit to be signed, why not use <a href="http://monotone.ca/" rel="nofollow">Mototone</a> distributed version control system?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
