<?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: Encrypting web.config</title>
	<atom:link href="http://jtoee.com/2008/02/encrypting-webconfig/feed/" rel="self" type="application/rss+xml" />
	<link>http://jtoee.com/2008/02/encrypting-webconfig/</link>
	<description>Putting the &#62;O&#60; in technology</description>
	<lastBuildDate>Thu, 04 Mar 2010 15:21:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ravi</title>
		<link>http://jtoee.com/2008/02/encrypting-webconfig/comment-page-1/#comment-1061</link>
		<dc:creator>Ravi</dc:creator>
		<pubDate>Fri, 04 Dec 2009 21:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://jtoee.com/wordpress/?p=41#comment-1061</guid>
		<description>aspnet_regiis creats a new key pair if you try to import just the Public key ..</description>
		<content:encoded><![CDATA[<p>aspnet_regiis creats a new key pair if you try to import just the Public key ..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Holodak</title>
		<link>http://jtoee.com/2008/02/encrypting-webconfig/comment-page-1/#comment-30</link>
		<dc:creator>Scott Holodak</dc:creator>
		<pubDate>Tue, 06 Jan 2009 23:47:49 +0000</pubDate>
		<guid isPermaLink="false">http://jtoee.com/wordpress/?p=41#comment-30</guid>
		<description>One small (but important) change:
C:\app&gt; aspnet_regiis -px MyCustomContainer mykeys.xml -pri

The -pri argument tells the machine that created the key store to also export the private key to the xml file.  Without it, you only export the public key.  Your procedure for importing and authorizing users remain the same.  

aspnet_regiis will allow you to import just the public key, but you would only be able to use it to encrypt sections (not decrypt).  If you encrypted your connection strings on the first server and installed just the public key on all the others, only the first server would be able to connect to the DB.  The rest wouldn&#039;t be able to parse the config.</description>
		<content:encoded><![CDATA[<p>One small (but important) change:<br />
C:\app&gt; aspnet_regiis -px MyCustomContainer mykeys.xml -pri</p>
<p>The -pri argument tells the machine that created the key store to also export the private key to the xml file.  Without it, you only export the public key.  Your procedure for importing and authorizing users remain the same.  </p>
<p>aspnet_regiis will allow you to import just the public key, but you would only be able to use it to encrypt sections (not decrypt).  If you encrypted your connection strings on the first server and installed just the public key on all the others, only the first server would be able to connect to the DB.  The rest wouldn&#8217;t be able to parse the config.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-07-23 &#171; Praveen&#8217;s Blog</title>
		<link>http://jtoee.com/2008/02/encrypting-webconfig/comment-page-1/#comment-6</link>
		<dc:creator>links for 2008-07-23 &#171; Praveen&#8217;s Blog</dc:creator>
		<pubDate>Wed, 23 Jul 2008 10:48:22 +0000</pubDate>
		<guid isPermaLink="false">http://jtoee.com/wordpress/?p=41#comment-6</guid>
		<description>[...] Jochen Toppe’s Blog » Encrypting web.config [...]</description>
		<content:encoded><![CDATA[<p>[...] Jochen Toppe’s Blog » Encrypting web.config [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
