At 05:54 PM 3/20/2010, John Daisley wrote:
Jim
In the case of our encrypted data no user, application or script is given
access to the tables in question. Access is only granted via a couple of
stored procedures and to be honest if you didn't know which ones you would
have a hard job finding
Jim
In the case of our encrypted data no user, application or script is given
access to the tables in question. Access is only granted via a couple of stored
procedures and to be honest if you didn't know which ones you would have a hard
job finding them as we have hundreds.
Problem with keepi
Hi Neil.
Information (in most cases a string < 100 chars, but that's probably not
important) that actually needs to be decrypted, so a hash won't do.
Jim
On 3/20/2010 5:09 PM, Tompkins Neil wrote:
Hi
What sort of information are you looking to encrypt ? If it is for user
passwords I'd reco
Thanks for all the responses and useful information.
Cheers
Neil
On Thu, Mar 18, 2010 at 6:35 PM, mos wrote:
> At 04:18 AM 3/18/2010, Tompkins Neil wrote:
>
>> Hi
>>
>> I'm currently looking to develop an on line web application - which is
>> going
>> to be used by around 200+ concurrent users
Hi
What sort of information are you looking to encrypt ? If it is for user
passwords I'd recommend SHA256 which is one way encryption. Or are you
looking to encrypt more sensitive information like card holder data ?
Regards
Neil
On Fri, Mar 19, 2010 at 4:22 PM, Jim wrote:
> Thanks for the re
I switched the tmp directory to a much bigger partition and I am still getting
the error. Any other ideas?
TIA,
Zak
--- On Wed, 3/10/10, Walter Heck wrote:
> From: Walter Heck
> Subject: Re: Corrupted table
> To: "Zakai Kinan"
> Cc: mysql@lists.mysql.com
> Date: Wednesday, March 10, 2010,
