Hi Claude
Following on from what everyone else has said, if you really do need to
store the CC details (for recurring payments?) you may consider using a
payment gateway company to handle the storage and processing of customers'
credit card details. For example, eWAY in Australia have a "Managed
P
: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Cold Fusion Encryption of Bank Details etc
I wouldn't store those sort of details on shared hosting... no way,
it's too risky. Even with encryption, you're relying on the shared
host to maintain your security, and if someone gets hold
st or something to
get the information
-Original Message-
From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf
Of SAMARIS Software
Sent: Thursday, 26 February 2009 10:11 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Cold Fusion Encryption of Bank Details etc
...@googlegroups.com] On Behalf
Of Steve Onnis
Sent: Thursday, 26 February 2009 8:59 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Cold Fusion Encryption of Bank Details etc
I wold be asking "why"
Why do you need to store it?
-Original Message-
From: cfaussie@google
I wold be asking "why"
Why do you need to store it?
-Original Message-
From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf
Of SAMARIS Software
Sent: Thursday, 26 February 2009 1:36 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Cold Fusion Encryption of Ba
-Original Message-
From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf
Of Mark Mandel
Sent: Thursday, 26 February 2009 6:34 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Cold Fusion Encryption of Bank Details etc
I wouldn't store those sort of details on s
I wouldn't store those sort of details on shared hosting... no way,
it's too risky. Even with encryption, you're relying on the shared
host to maintain your security, and if someone gets hold of you DB,
its your head on the chopping block, not yours.
If they are running cf8, it's a little better
Hi Claude,
The simple solution is to use cfencrypt before you write the information to the
database and then use cfdecrypt when you read it out again - using the same
encryption key of course. For added security you could make the user logon
before the end of month to enter the encryption key
