Dear all, I know that many MySQL developers are subscribers of this list and I decided to ask this question with all the possible respect that the developers and MySQL itself deserves. I think it's the most appropriate list to do this and the place where I will receive the most precise answers. I have an application (QuizGame) with a client using VB 6 and a server created using C. The connection is estabilished using TCP/IP. Today, the server itself connects to MySQL and performs all the queries, processing the results. It works fine but the amount of users is growing fast and I want to transfer part of the queries' job to the client (update user information, getting ranking information). This means that I'll have to add a user on MySQL like game@% using a password. Today all the queries are performed via localhost and at least this seems to be more secure. So, which are the risks of opening MySQL to the client? Can the system be harmed somehow? What about sniffers and tcpdumping? Thanks in advance for all the answers that I'll get and up the "power trio"! Best regards, Fábio Ottolini --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
