Mike,
I agree with the things that Geoff is telling you. What I have seen in
the past and even in some free PHP programs that I downloaded for
learning purposes, is the CC number stored in your database but not
entirely. I mean like 1234789 so the customer can verify that
the transaction
MD5 encryption of passwords is secure since you do not need to decrypt the
password ever (in fact you can't). You just encrypt the password that the
user entered and check if the MD5 of each password is the same, then the
user most likely entered the correct password.
- Original Message
On Tuesday 13 August 2002 10:57 am, you wrote:
MD5 encryption of passwords is secure since you do not need to decrypt the
password ever (in fact you can't). You just encrypt the password that the
user entered and check if the MD5 of each password is the same, then the
user most likely
Makes sense, except if you use upper and lowercase characters,
numbers, and symbols (as you should for secure passwords). I
would think that with these kind of passwords, storing the sheer
number of posibilites would get slightly large. And I mean even
if it is easy to break, it's more secure
On Tuesday 13 August 2002 12:20 pm, you wrote:
Makes sense, except if you use upper and lowercase characters,
numbers, and symbols (as you should for secure passwords). I
would think that with these kind of passwords, storing the sheer
number of posibilites would get slightly large. And I
If I could find the link I would send it, but I read about 6 months
back on RSA Data Security's website that a study was being done by
mathemetician's and at the time they were theorizing that they highly
doubted any overlap in keysums but if such did exist they believed that
the key you would
On Wed, 14 Aug 2002, Robert Parker wrote:
-On Tuesday 13 August 2002 12:20 pm, you wrote:
- Makes sense, except if you use upper and lowercase characters,
- numbers, and symbols (as you should for secure passwords). I
- would think that with these kind of passwords, storing the sheer
- number of
True, and there's always the MCRYPT library.
Adam Voigt
[EMAIL PROTECTED]
On Tue, 2002-08-13 at 12:48, John S. Huggins wrote:
On Wed, 14 Aug 2002, Robert Parker wrote:
-On Tuesday 13 August 2002 12:20 pm, you wrote:
- Makes sense, except if you use upper and lowercase characters,
-
: Re[2]: [PHP] Credit Card suggestions
On Wed, 14 Aug 2002, Robert Parker wrote:
-On Tuesday 13 August 2002 12:20 pm, you wrote:
- Makes sense, except if you use upper and lowercase characters,
- numbers, and symbols (as you should for secure passwords). I would
- think that with these kind
On Wed, 14 Aug 2002, Robert Parker wrote:
-On Tuesday 13 August 2002 12:20 pm, you wrote:
- Makes sense, except if you use upper and lowercase characters,
- numbers, and symbols (as you should for secure passwords). I
- would think that with these kind of passwords, storing the sheer
- number of
On Wed, Aug 14, 2002 at 02:20:07AM -0400, Robert Parker wrote:
I don't remember where I read this but it only takes the crackers about 1 - 2
seconds to crack your average MD5 encrypted password. This is quite logical
because all they had to do is make a database of all of the MD5 sums of all
11 matches
Mail list logo
