Thanks Joe.
I ended up encrypting the data and then creating a hex string (i.e.
<joseph.e.kap...@removethis.accenture.com> wrote:
> Maybe you should show your code? It sounds like you have a misunderstanding
> of how you should be encoding your data. Basically, you use Base64 to
> represent arbitrary binary data as a string. Base64 is good for this
> purpose because it can deal with binary data that doesn't have a good
> natural string representation such as data with embedded nulls and other
> non-printable characters. Examples of "arbitrary binary data" in the
> context of crypto include encrypted data, hashes and keys.
>
> If you have a string of plain text and need to encrypt that, you typically
> want to use a text-based encoding such as UTF8 to convert that into binary.
>
> Joe K.
>
> --
> Joe Kaplan-MS MVP Directory Services Programming
> Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net > --<michaellove...@yahoo.com> wrote in message
>
> news:1177011761.188062.178380@l77g2000hsb.googlegroups.com...
>
>
>
> > Hi there.
>
> > I am trying to encrypt a connect string that has some special
> > characters in it (i.e. ';' and '=' and whatever other funky chars can
> > be in a password). So this chokes when I use the Convert.ToBase64 and
> > Convert.FromBase64 methods. I need the result to be a legitimate
> > string that I can put into a config file. Any ideas on how to best
> > overcome this issue?
>
> > Thanks, Mike- Hide quoted text -
>
> - Show quoted text -