I believe MySQL 4.1 has support for ssl replication but it's still alpha at the moment.
If you are referring to connecting to a MySQL server from an application to query it then the following applies: ---from the manual--- When you connect to a MySQL server, you normally should use a password. The password is not transmitted in clear text over the connection, however the encryption algorithm is not very strong, and with some effort a clever attacker can crack the password if he is able to sniff the traffic between the client and the server. If the connection between the client and the server goes through an untrusted network, you should use an SSH tunnel to encrypt the communication. --------------------- http://www.mysql.com/doc/en/Security.html Cheers, A -----Original Message----- From: Jim Richardson [mailto:[EMAIL PROTECTED] Sent: Thursday 29 January 2004 21:03 To: [EMAIL PROTECTED] Subject: Re: Read Slaves, and load balancing between them... On Thu, Jan 29, 2004 at 03:40:17PM -0000, Andrew Braithwaite wrote: >Hi, > >I employ a simple method, I have a 'status' table on the master and >have a cron job that updates this table with the current time (now()) >every minute. I test all the slaves each minute and if the time in the >status table gets too far behind the actual time then it flags a >warning to me. > >Cheers, > >A That's a great idea, thanks! On a related note, I have two servers, one slave, one master, and I want to secure the datapath between them. What's the "best" way ? (on Linux, if that matters) I am considering stunnel, or ssh tunnel, or is there something in MySQL I can use to connect securely? -- Jim Richardson http://www.eskimo.com/~warlock "We have to go forth and crush every world view that doesn't believe in tolerance and free speech," - David Brin -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
