Thank you for the suggestion, as you suggested i shall go for application level.
I have another query too, please answer,
Normally, If i need to store an integer value i have to define it as int, If I
encrypt this, i must define its type as string of different size[it depend upon
the encryption output] than its original size. It increases the db size. I am
known that if it is secure i have to choose encryption. but when i choose
encryption it leads the more memory usage.
Any comment on this?
From: Johan De Meersman <vegivamp@stripped>
To: Vikram A <vikkiatbipl@stripped>
Cc: MY SQL Mailing list <mysql@stripped>
Sent: Mon, 27 September, 2010 6:55:04 PM
Subject: Re: Best encription method?
Both have benefits.
* data is encrypted during transmit, too
* processing is offloaded from your hard-to-scale database server
* decrypt keys don't pass your database, so dba or other users can't peekDB
* Guaranteed consistent implementation regardless of client
Can't think of other benefits of DB-side encryption, offhand :-) I would go for
the app-side every time. Let the database worry about managing the data, don't
bother it with application stuff.
On Mon, Sep 27, 2010 at 3:15 PM, Vikram A <vikkiatbipl@stripped> wrote:
>Can i have your valuable suggestion on the following?
>I would like to encrypt a particular table of records.
>I hope can choose two ways,number one, application level encryption method
>choosing our own encryption algorithm and an another is database level
>my question is, which is portable, which is consistent? or altogether the
>encryption should not degrades the performance.
>Note: The application is going to be across an intranet
>Suggestions are appreciated!
>Thank you in advance.
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel