AES is a good algorithm choice for an symmetric cipher. It would be a good
idea to use an unique, random initialization vector (IV) for each number.
This will help prevent brute force attacks as it will cause the cipher text
to be different for the same cc#. You can store the IV next to the
encrypted data as it is not a secret.
Encrypting the AES key with DPAPI is also a good idea. Essentially,
anything you can do to make it hard for attackers to steal the key is good.
www.dotnetthis.com has a good symmetric encryption sample.
Joe K.
> Ok,
>
[quoted text clipped - 8 lines]
>
> Weston Weems
Weston Weems - 03 Jan 2006 22:54 GMT
www.dotnetthis.com does have a basic encryption sample, which I could
already do, but has reference to "making it industry strength" which I
could not find anywhere on the site.
Does anyone have recommendations or a simple demo of how one would use
the encryption plus storing the key as scalable/clusterable as possible?
right now webserver is the machine that would be encrypting the data and
storing on a seperate db server, but later on, who knows. If I
understand correctly DPAPI would prevent me from being able to easilya
dd a load balanced web app server to the pool etc.
> AES is a good algorithm choice for an symmetric cipher. It would be a good
> idea to use an unique, random initialization vector (IV) for each number.
[quoted text clipped - 21 lines]
>>
>>Weston Weems
Hi,
I would think Rijndael with DPAPI is a good option.
Kaustav.
> Ok,
>
[quoted text clipped - 8 lines]
>
> Weston Weems