Yeah, storing the CC numbers is a scary thing to do. You open yourselves up to a tremendous amount of liability. If you do decide to do it though, you might find or write an executable that will (en)(de)crypt your strings, then you could call it from .NET apps and CF apps as needed. This approach may allow you to be more selective in the algorithm you choose to use...
Is your processing done real-time? What is it that necessitates the storing of CC nums in the first place? --Ferg Fabio Terracini wrote: >Personally, I don't think storing CC numbers are a good idea. > >You can encrypt/decrypt data in between envoirments if they use the same >algorithm. Checkout CF documentations to see avaiable algorithms. > >Also, if it's possible by your functional needs (not on the CC case, >probably), one-way "encrypts" (hashs) are more secure, since you encrypt >the data and compare the encrypted data (like on a login system). > >Fabio Terracini > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:216039 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
