Hello.
If you mentioned an AES_ENCRYPT(), see: http://dev.mysql.com/doc/mysql/en/encryption-functions.html You specify your password in your queries. The database doesn't contains the password by itself. Your application can ask a user for a password each time, and you don't have to store passwords in the source. > What i think Aes encryption reduce the risk but does not make data 100% > safe because of source code dependency. Nobody gives you a 100% garanty. love <[EMAIL PROTECTED]> wrote: > Hi, > > Aes Encryption requires a password (key) to access data, now where do > we store this key? with the source code ? or in seperate database ? > because any body who has the access to souce code can view the critical > info or even if you store passwords in another database then it is not a > big deal to get those passwords if source code is accessible. > > What i think Aes encryption reduce the risk but does not make data 100% > safe because of source code dependency. > > Love Kumar > Perl Develpment Team > eBookers.com > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
