PHP
downloads | documentation | faq | getting help | mailing lists | reporting bugs | php.net sites | links | conferences | my php.net

search for in the

Modelo de Almacenamiento Encriptado> <Seguridad de Bases de Datos
Last updated: Fri, 04 Jul 2008

view this page in

Conexión con la Base de Datos

Puede que desee establecer las conexiones sobre SSL para encriptar las comunicaciones cliente/servidor, incrementando el nivel de seguridad, o puede hacer uso de ssh para encriptar la conexión de red entre los clientes y el servidor de la base de datos. Si cualquiera de estos recursos es usado, entonces monitorear su tráfico y adquirir información sobre su base de datos será difícil para un atacante potencial.



add a note add a note User Contributed Notes
Conexión con la Base de Datos
M Zijlstra
16-Aug-2007 06:11
There is no need to run your db on vmware... If they're on the same machine the connection always goes through the local loopback device thus never touching the actual network.

This is true both when the DB host is specified as 'localhost' or '127.0.0.1' and if the machine's actual host name or outside network address is used (in which case the OS will/should recognise that it's actually a local connection and uses the loopback)
jakub dot lasinski at interia dot pl
28-Jul-2007 09:15
Even if webserver and DBMS are on the same phisical machine one can separate networks by setting database in virtual server inside the main system (using for example VMware solutions).
aastaneh at cmax2 dot com
27-Jul-2006 07:28
Another solution to protect your database is to have a seperate backend network exclusively used for database traffic. Your webserver(s) would have two interface cards: one facing the world, one facing the internal database network. This way- there's no chance of intercepting database traffic from the outside.
07-Oct-2005 12:20
Obviously, this does not apply if PHP and the DBMS are running on the same machine.

 
show source | credits | stats | sitemap | contact | advertising | mirror sites