<?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 for jwiltshire.org.uk</title>
	<atom:link href="http://www.jwiltshire.org.uk/content/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jwiltshire.org.uk/content</link>
	<description>The public face of jwiltshire</description>
	<lastBuildDate>Thu, 14 Feb 2013 07:37:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on X-RaceProtection: yes by Elessar</title>
		<link>http://www.jwiltshire.org.uk/content/2013/02/13/x-raceprotection/comment-page-1/#comment-3606</link>
		<dc:creator>Elessar</dc:creator>
		<pubDate>Thu, 14 Feb 2013 07:37:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwiltshire.org.uk/content/?p=374#comment-3606</guid>
		<description><![CDATA[Good idea, but does the X- prefix for experimental stuff not have been deprecated?]]></description>
		<content:encoded><![CDATA[<p>Good idea, but does the X- prefix for experimental stuff not have been deprecated?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on X-RaceProtection: yes by Anonymous</title>
		<link>http://www.jwiltshire.org.uk/content/2013/02/13/x-raceprotection/comment-page-1/#comment-3605</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 14 Feb 2013 01:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwiltshire.org.uk/content/?p=374#comment-3605</guid>
		<description><![CDATA[The idea makes sense in principle, but the name of the header doesn&#039;t do a good job of conveying its meaning.  You only want to use this when making the obvious reply, such as &quot;done&quot; or &quot;processed&quot; or &quot;handled&quot;, as opposed to any form of substantive response.  Also, RFC6648 deprecated the use of the &quot;X-&quot; prefix.  Thus, I&#039;d suggest a header name like &quot;ObviousReply&quot; instead, with the same semantics.

You might also consider a couple of additional flags, space-separated from the &quot;yes&quot; or Message-Id.  First, if either the earlier or later mail has the keyword &quot;checksum-unquoted&quot; in ObviousReply, the system processing the mail should only drop later mails in favor of earlier ones if the unquoted (non-&#039;&gt;&#039;-prefixed) text of both messages matches exactly, modulo whitespace and with standard signature dropping (&quot;-- &quot;).  Second, if ObviousReply includes the keyword &quot;symmetric&quot;, both mails must include the ObviousReply header to get dropped; that seems like a reasonable quid-pro-quo for using the header, enforcing that either party believes that they&#039;ve written the obvious message and wouldn&#039;t mind having their message dropped in favor of another.]]></description>
		<content:encoded><![CDATA[<p>The idea makes sense in principle, but the name of the header doesn&#8217;t do a good job of conveying its meaning.  You only want to use this when making the obvious reply, such as &#8220;done&#8221; or &#8220;processed&#8221; or &#8220;handled&#8221;, as opposed to any form of substantive response.  Also, RFC6648 deprecated the use of the &#8220;X-&#8221; prefix.  Thus, I&#8217;d suggest a header name like &#8220;ObviousReply&#8221; instead, with the same semantics.</p>
<p>You might also consider a couple of additional flags, space-separated from the &#8220;yes&#8221; or Message-Id.  First, if either the earlier or later mail has the keyword &#8220;checksum-unquoted&#8221; in ObviousReply, the system processing the mail should only drop later mails in favor of earlier ones if the unquoted (non-&#8217;&gt;&#8217;-prefixed) text of both messages matches exactly, modulo whitespace and with standard signature dropping (&#8220;&#8211; &#8220;).  Second, if ObviousReply includes the keyword &#8220;symmetric&#8221;, both mails must include the ObviousReply header to get dropped; that seems like a reasonable quid-pro-quo for using the header, enforcing that either party believes that they&#8217;ve written the obvious message and wouldn&#8217;t mind having their message dropped in favor of another.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on From building to demolishing by Matthew W.S. Bell</title>
		<link>http://www.jwiltshire.org.uk/content/2012/08/13/from-building-to-demolishing/comment-page-1/#comment-3489</link>
		<dc:creator>Matthew W.S. Bell</dc:creator>
		<pubDate>Mon, 13 Aug 2012 17:00:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwiltshire.org.uk/content/?p=351#comment-3489</guid>
		<description><![CDATA[That wiring is in an electrical safe zone, and, as such, does not require capping. I believe it might be required to be further from the surface, however.]]></description>
		<content:encoded><![CDATA[<p>That wiring is in an electrical safe zone, and, as such, does not require capping. I believe it might be required to be further from the surface, however.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on From building to demolishing by Nick</title>
		<link>http://www.jwiltshire.org.uk/content/2012/08/13/from-building-to-demolishing/comment-page-1/#comment-3488</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Mon, 13 Aug 2012 14:45:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwiltshire.org.uk/content/?p=351#comment-3488</guid>
		<description><![CDATA[For what it&#039;s worth, there&#039;s nothing in the wiring regs about protecting cables in that kind of situation - there are defined &quot;safe zones&quot; in a line above and below a socket which people are expected not to try and put a drill through.]]></description>
		<content:encoded><![CDATA[<p>For what it&#8217;s worth, there&#8217;s nothing in the wiring regs about protecting cables in that kind of situation &#8211; there are defined &#8220;safe zones&#8221; in a line above and below a socket which people are expected not to try and put a drill through.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on From building to demolishing by Jon</title>
		<link>http://www.jwiltshire.org.uk/content/2012/08/13/from-building-to-demolishing/comment-page-1/#comment-3487</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 13 Aug 2012 13:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwiltshire.org.uk/content/?p=351#comment-3487</guid>
		<description><![CDATA[Well, there was a large slab of wood on top to make a sideboard, but it had zero storage capacity. I didn&#039;t take a photo of it before I took it out, since at that stage I was just having a look inside (I got a bit carried away).]]></description>
		<content:encoded><![CDATA[<p>Well, there was a large slab of wood on top to make a sideboard, but it had zero storage capacity. I didn&#8217;t take a photo of it before I took it out, since at that stage I was just having a look inside (I got a bit carried away).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on From building to demolishing by Elessar</title>
		<link>http://www.jwiltshire.org.uk/content/2012/08/13/from-building-to-demolishing/comment-page-1/#comment-3486</link>
		<dc:creator>Elessar</dc:creator>
		<pubDate>Mon, 13 Aug 2012 12:51:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwiltshire.org.uk/content/?p=351#comment-3486</guid>
		<description><![CDATA[Neat work. You say this wall was just eating space for decorative purpose? There is at least one architect that deserved some slaps…]]></description>
		<content:encoded><![CDATA[<p>Neat work. You say this wall was just eating space for decorative purpose? There is at least one architect that deserved some slaps…</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I&#8217;m probably not going to DebConf12 by Gunnar</title>
		<link>http://www.jwiltshire.org.uk/content/2012/06/15/probably-not-going-to-debconf12/comment-page-1/#comment-3465</link>
		<dc:creator>Gunnar</dc:creator>
		<pubDate>Fri, 15 Jun 2012 23:09:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwiltshire.org.uk/content/?p=334#comment-3465</guid>
		<description><![CDATA[Oh, hold please a day, two max, before deciding!

I am not part of the travel sponsorship team - But I know they were making their best to send out the first batch of results now.]]></description>
		<content:encoded><![CDATA[<p>Oh, hold please a day, two max, before deciding!</p>
<p>I am not part of the travel sponsorship team &#8211; But I know they were making their best to send out the first batch of results now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on StartSSL: finally, a trustworthy certifier* by Brad</title>
		<link>http://www.jwiltshire.org.uk/content/2011/06/13/startssl-finally-a-trustworthy-certifier/comment-page-1/#comment-3322</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Fri, 24 Jun 2011 20:44:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwiltshire.org.uk/content/?p=312#comment-3322</guid>
		<description><![CDATA[They&#039;re back up, no false certs issued or private keys stolen.  more info here.

http://www.theregister.co.uk/2011/06/21/startssl_security_breach/

amazing to me how little the company bothered to communication their situation.  I have a class2 cert with them and would certainly want their assurance that docs I provided them were not compromised / stolen etc.]]></description>
		<content:encoded><![CDATA[<p>They&#8217;re back up, no false certs issued or private keys stolen.  more info here.</p>
<p><a href="http://www.theregister.co.uk/2011/06/21/startssl_security_breach/" rel="nofollow">http://www.theregister.co.uk/2011/06/21/startssl_security_breach/</a></p>
<p>amazing to me how little the company bothered to communication their situation.  I have a class2 cert with them and would certainly want their assurance that docs I provided them were not compromised / stolen etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on StartSSL: finally, a trustworthy certifier* by Corsac</title>
		<link>http://www.jwiltshire.org.uk/content/2011/06/13/startssl-finally-a-trustworthy-certifier/comment-page-1/#comment-3317</link>
		<dc:creator>Corsac</dc:creator>
		<pubDate>Tue, 21 Jun 2011 06:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwiltshire.org.uk/content/?p=312#comment-3317</guid>
		<description><![CDATA[Hmhm, advertising StartSSL might not have been a good idea, they&#039;ve just been compromised:

Due to a security breach that occurred at the 15th of June, issuance of digital certificates and related services has been suspended. Our services will remain offline until further notice.

Subscribers and holders of valid certificates are not affected in any form.

Visitors to web sites and other parties relying on valid certificates are not affected.

We apologize for the temporary inconvenience and thank you for your understanding.]]></description>
		<content:encoded><![CDATA[<p>Hmhm, advertising StartSSL might not have been a good idea, they&#8217;ve just been compromised:</p>
<p>Due to a security breach that occurred at the 15th of June, issuance of digital certificates and related services has been suspended. Our services will remain offline until further notice.</p>
<p>Subscribers and holders of valid certificates are not affected in any form.</p>
<p>Visitors to web sites and other parties relying on valid certificates are not affected.</p>
<p>We apologize for the temporary inconvenience and thank you for your understanding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on StartSSL: finally, a trustworthy certifier* by Kint</title>
		<link>http://www.jwiltshire.org.uk/content/2011/06/13/startssl-finally-a-trustworthy-certifier/comment-page-1/#comment-3316</link>
		<dc:creator>Kint</dc:creator>
		<pubDate>Mon, 20 Jun 2011 22:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.jwiltshire.org.uk/content/?p=312#comment-3316</guid>
		<description><![CDATA[http://www.h-online.com/security/news/item/Attack-on-Israeli-Certificate-Authority-1264008.html]]></description>
		<content:encoded><![CDATA[<p><a href="http://www.h-online.com/security/news/item/Attack-on-Israeli-Certificate-Authority-1264008.html" rel="nofollow">http://www.h-online.com/security/news/item/Attack-on-Israeli-Certificate-Authority-1264008.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
