<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title type="html">encryption - Mark Rogers</title>
  <icon>http://www.markdavidrogers.com/oxitesample/Content/icons/flame.ico</icon>
  <logo>http://www.markdavidrogers.com/oxitesample/Content/icons/flame.png</logo>
  <updated>2009-10-01T10:02:00Z</updated>
  <subtitle type="html">This is the Oxite Sample description</subtitle>
  <id>http://www.markdavidrogers.com/oxitesample/tags/encryption/atom</id>
  <link rel="alternate" type="text/html" hreflang="en" href="/oxitesample/tags/encryption"/>
  <link rel="self" type="application/atom+xml" href="http://www.markdavidrogers.com/oxitesample/Tags/encryption/ATOM"/>
  <generator uri="http://oxite.net" version="1.0">Oxite</generator>
  <entry>
    <title type="html">Encryption Blues</title>
    <link rel="alternate" type="text/html" href="http://www.markdavidrogers.com/oxitesample/Blog/encryption-blues"/>
    <id>http://www.markdavidrogers.com/oxitesample/Blog/encryption-blues</id>
    <updated>2009-10-01T17:11:41.057Z</updated>
    <published>2009-10-01T10:02:00Z</published>
    <author>
      <name>Admin</name>
    </author>
    <category term="encryption" />
    <content type="html" xml:lang="en">
      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.
    </content>
  </entry>
</feed>

