<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>encryption - Mark Rogers</title>
        <description>This is the Oxite Sample description</description>
        <link>http://www.markdavidrogers.com/oxitesample/Tags/encryption</link>
        <language>en</language>
        <image>
            <url>http://www.markdavidrogers.com/oxitesample/Content/icons/flame.png</url>
            <title>Mark Rogers</title>
            <link>http://www.markdavidrogers.com/oxitesample/Tags/encryption</link>
            <width>64</width>
            <height>64</height>
        </image>
        <item>
            <dc:creator>Admin</dc:creator>
            <title>Encryption Blues</title>
            <description>Currently I'm trying to create a single-sign on solution, and I was having trouble because sometimes (but not always) the encrypted text would fail to decrypt.  I found out that the later .net versions have stricter checking for valid characters.  So when the encrypted byte array was converted to a string, the encoding process would create characters that the stricter decoding process did not like.

This &lt;a href=&quot;http://blogs.msdn.com/shawnfa/archive/2005/11/10/491431.aspx&quot;&gt;article&lt;/a&gt; on msdn's .net security blog finally helped me out.</description>
            <link>http://www.markdavidrogers.com/oxitesample/Blog/encryption-blues</link>
            <guid isPermaLink="true">http://www.markdavidrogers.com/oxitesample/Blog/encryption-blues</guid>
            <pubDate>Thu, 01 Oct 2009 10:02:00 GMT</pubDate>
            <category>encryption</category>
        </item>
    </channel>
</rss>
