for example, i have table containsa field - p***word, which is a md5
hash

i have this table to replicate across the publich network

i don't want to setup any secure channel for replication since it
might cause additonal overhaded and delay...

are there any workaround for making a particular field more secure?



one way i am thinking is to create a mysql custome function, which
encrypt the hash

it work as following: (php)

$p***word = "p***word"
$p***word = encrypt_me($p***word);


e.g.

update tableA set p***word = md5( decrypt_me($p***word) );

which decrypt_me() and encrypt_me, but at different language, one for
php and one for mysql procedure, when the sql statement repliate
across the network, people don't know the hash....

any comments on this approach or better method?

thanks.

If you are using a good salt-ing mechanism (google for p***word hash
salting if you don't do this already) on the current hash then it
shouldn't really be an issue to transfer them as is. If you want to be
more secure you may be able to use some of the encryption functions
built into mysql: http://dev.mysql.com/doc/refman/5.0/...on_aes-encrypt.

On 5 26 , 3 55 , "justin.dema...@gmail.com"
<justin.dema...@gmail.com> wrote:
> If you are using a good salt-ing mechanism (google for p***word hash
> salting if you don't do this already) on the current hash then it
> shouldn't really be an issue to transfer them as is. If you want to be
> more secure you may be able to use some of the encryption functions
> built into mysql:http://dev.mysql.com/doc/refman/5.0/...ions.html#func....

p***word is an example...for example, if i want to excrypt the phone
no. hashing didn't work....

the problem with mysql encryption is that the key will be visible to
the public network during replication, so this is the reason i need to
use my own...

thanks anyway

howa wrote:
> for example, i have table containsa field - p***word, which is a md5
> hash
>
> i have this table to replicate across the publich network
>
> i don't want to setup any secure channel for replication since it
> might cause additonal overhaded and delay...

Encryption will also cause some additional overhead and delay. Just pipe
it through an encrypted tunnel like SSH.

Cheers,
Nicholas Sherlock