> At 05:19 PM 07/13/2001 , you wrote:
> >Hi,
> >
> >I would like to be able to create some tables in a database on an SQL server
> >at my web provider, then access those tables via a client application
> >running on my PC over the Internet (dial-up connection). My understanding is
> >that the client application accesses the SQL server via TCP/IP and not ODBC.
> >
> >My web provider says no way. They can enable an ODBC connection for one
> >static IP address, which is not an acceptable solution, because a) I don't
> >want to use ODBC, and b) my dial-up connection may use one of a range of IP
> >addresses. They will not let me have direct TCP/IP access to the database.
> >
> >My question is why my ISP would say this. Of course the database is password
> >protected, so I don't see why direct access is any more a security risk than
> >using their web-based client. Is this common practice among ISPs, or do I
> >need to shop for a new one? Any suggestions?
If your hosting provider runs SSH on the server, get an SSH client that
does tunneling. Create a tunnel from your local machine on any port
(3306 works well :), to port 3306 (or whatever port MySQL is running on)
on the remote computer. When you log the SSH session in (the ssh.com
client can do tunnels only), you have "local" access to the database.
As far as the system is concerned, you're local to it. As far as your
client app is concerned, the DB is on localhost. As far as anyone else
is concerned, the passwords and all traffic is encrypted.
--
Sapere aude
My mind not only wanders, it sometimes leaves completely.
---------------------------------------------------------------------
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
