-Original Message-
From: Michael T. Babcock [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 07, 2002 10:18 AM
To: '[EMAIL PROTECTED]'
Subject: Re: Protecting CC Numbers
Hack Hawk wrote:
>> This implies hard-coding a private key and password somewhere on
your
>>
On Sun, 6 Oct 2002, David Gerler wrote:
> Date: Sun, 6 Oct 2002 14:21:11 -0400
> From: David Gerler <[EMAIL PROTECTED]>
> To: Mysql <[EMAIL PROTECTED]>
> Subject: protecting CC numbers
>
> Hi,
> I am working on an application that will need to store users CC
> numbers so that they can be c
Hack Hawk wrote:
>> This implies hard-coding a private key and password somewhere on your
>> system. This type of system (IMO) should NEVER be connected to the
>> Internet.
>
>
Agreed and doubly agreed. In fact, I'd say you should never save a CC #
in your database _ever_ unless you're
One other thing..
If something goes wrong or some costumers complain about being charged
without their request etc. the credit card companies can come after you. And
if they are able to prove that you have not done everything you should to
keep the CC information secure and that your routines we
t;[EMAIL PROTECTED]>; "Mysql"
<[EMAIL PROTECTED]>
Sent: Sunday, October 06, 2002 7:57 PM
Subject: Re: protecting CC numbers
> At 11:21 AM 10/06/2002, David Gerler wrote:
> >Hi,
> >Can someone give me an overview
> >of protecting the numbers with mysql and SS
At 11:21 AM 10/06/2002, David Gerler wrote:
>Hi,
>Can someone give me an overview
>of protecting the numbers with mysql and SSL? Will the SSL protect the
>numbers when they are stored on the site? Or just when they are
>transmitted? Should I use something like PGP to encrypt the numbers
>before st