>Neil,
>Perhaps you replied directly to the thread starter.
My bad. It was in Friday's batch or emails.
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
>Did you actually SNIP the "document[ation] how it can be done safely for
all
>the world to see and learn!" ??? Or are you saying go buy this book?
No, I retyped the passage in its entirety from the book. Learn to
SNIP your posts !
Cheers - Neil
--
Neil,
Perhaps you replied directly to the
From: "Dwight Altman" <[EMAIL PROTECTED]>
To: "'Peter Beckman'" <[EMAIL PROTECTED]>,
"'Neil Smith [MVP, Digital media]'" <[EMAIL PROTECTED]>
Cc:
Date: Mon, 9 Jan 2006 09:24:05 -0600
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Co
On Fri, 6 Jan 2006, Neil Smith [MVP, Digital media] wrote:
Peter Beckman wrote:
So I'm thinking about how to save credit card numbers in the DB, for
re-charging cards for subscriptions, new orders, etc.
Yes yes, lawsuits, scary, etc.
I'm glad you're so blase about this and the threat of your
Peter wrote:
> So I'm thinking about how to save credit card numbers in the DB, for
> re-charging cards for subscriptions, new orders, etc.
> I'm also thinking about how to save passwords in the DB, not plaintext, but
> not one-way encrypted either.
> Any suggestions? How would I secure the datab
Yes yes, lawsuits, scary, etc.
I'm glad you're so blase about this and the threat of your business
going under due to exposure to extortion. When you've got the site
running, let me know the address, so I can advise my friends and
colleagues to avoid it at any cost.
Public key encryp
[EMAIL PROTECTED]
Subject: Re: [PHP-DB] Storing Credit Cards, Passwords, Securely,two-way
encryption
Date: Fri, 06 Jan 2006 23:52:25 +
At 03:48 06/01/2006, you wrote:
Date: Thu, 5 Jan 2006 22:48:24 -0500 (EST)
From: Peter Beckman <[EMAIL PROTECTED]>
To: John Meyer <[EMAIL PROTECTED]&
flowed
Subject: Re: [PHP-DB] Storing Credit Cards, Passwords, Securely, two-way
encryption
On Thu, 5 Jan 2006, John Meyer wrote:
Peter Beckman wrote:
So I'm thinking about how to save credit card numbers in the DB, for
re-charging cards for subscriptions, new orders, etc.
Yes ye
On Fri, 6 Jan 2006, Julien Bonastre wrote:
Any reason why you need to have reversible encryption on the password
value??
No... I just prefer to assume that if someone gets my DB, they might
try
using user/pass pairs on banking sites, or paypal, or other ways, and
if I
can reversible en
On Fri, 6 Jan 2006, Julien Bonastre wrote:
Any reason why you need to have reversible encryption on the password value??
No... I just prefer to assume that if someone gets my DB, they might try
using user/pass pairs on banking sites, or paypal, or other ways, and if I
can reversible encrypt
On Thu, 5 Jan 2006, John Meyer wrote:
Peter Beckman wrote:
So I'm thinking about how to save credit card numbers in the DB, for
re-charging cards for subscriptions, new orders, etc.
Why, is the first question I would ask you.
So I'm thinking about how to save credit card numbers in the DB,
"Bastien Koert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>;
Sent: Friday, January 06, 2006 12:36 PM
Subject: RE: [PHP-DB] Storing Credit Cards, Passwords, Securely, two-way
encryption
CC saving is a bad idea on a web facing server...much better to let
the user re-input
Peter Beckman wrote:
So I'm thinking about how to save credit card numbers in the DB, for
re-charging cards for subscriptions, new orders, etc.
Why, is the first question I would ask you. First off, on a new order,
why wouldn't you just save the authorization code, instead of the credit
card
Bastien
From: Peter Beckman <[EMAIL PROTECTED]>
To: PHP-DB Mailing List
Subject: [PHP-DB] Storing Credit Cards, Passwords, Securely, two-way
encryption
Date: Thu, 5 Jan 2006 20:27:57 -0500 (EST)
So I'm thinking about how to save credit card numbers in the DB, for
re-charging car
So I'm thinking about how to save credit card numbers in the DB, for
re-charging cards for subscriptions, new orders, etc.
I'm also thinking about how to save passwords in the DB, not plaintext, but
not one-way encrypted either.
Any suggestions? How would I secure the database? I'm thinking so
15 matches
Mail list logo
