On Fri, Jan 26, 2001 at 10:39:46AM -0600, Patrick Goetz wrote:
>
> Thanks for the response.
>
> On Thu, 25 Jan 2001, Jeremy D. Zawodny wrote:
> > > It just occurred to me, however, that this becomes a much bigger
> > > problem when the web server(s) and the database server are running
> > > on d
Hi Patrick,
You can try something like:
ssh -L 6969:ukdb-qa: root@ukdb-qa
Use the above on a remote host (lets call it wms-qa). This assumes ukdb-qa is
running a mysqld on port . This command will cause wms-qa to listen on port
6969 for connections and forward them all across a secure con
Thanks for the response.
On Thu, 25 Jan 2001, Jeremy D. Zawodny wrote:
> > It just occurred to me, however, that this becomes a much bigger
> > problem when the web server(s) and the database server are running
> > on different machines.
>
> Only if they're on different networks. Ideally, you
On Thu, Jan 25, 2001 at 10:01:59PM -0600, Patrick Goetz wrote:
>
> Currently, every system I've set up is small enough so as to have
> the web server and the database server on the same machine.
> Consequently, loss of security due to packet-sniffing can be
> completely controlled by using, say,
Currently, every system I've set up is small enough so as to have the web
server and the database server on the same machine. Consequently, loss of
security due to packet-sniffing can be completely controlled by using,
say, apache-ssl, since communications between the web server and the
database
