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

search for in the

Modelo de Armazenamento Criptografado> <Segurança de Bancos de Dados
Last updated: Fri, 22 Aug 2008

view this page in

Conectando com o Banco de Dados

Você pode querer estabelecer as conexões sobre SSL para criptografar comunicações cliente/servidor para aumentar a segurança, ou você pode usar ssh para criptografar a conexão de rede entre clientes e o servidor de banco de dados. Se uma dessa opções for usada, monitoramento do seu tráfego e obtenção de informação sobre seu banco de dados serão dificultados por um atacante.



add a note add a note User Contributed Notes
Conectando com o Banco de Dados
M Zijlstra
17-Aug-2007 12: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
29-Jul-2007 03: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
28-Jul-2006 01: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 06:20
Obviously, this does not apply if PHP and the DBMS are running on the same machine.

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