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

search for in the

암호화 저장 모델> <데이터베이스 설계하기
Last updated: Fri, 24 Jul 2009

view this page in

데이터베이스 접속하기

보안을 증가하기 위하여, 클라이언트/서버 간 통신을 암호화하는 SSL 접속을 할 수 있습니다. 또는 클라이언트와 데이터베이스 서버간의 네트워크 접속을 암호화하기 위하여 ssh를 사용할 수 있습니다. 어떠한 방법을 사용하건, 공격자가 트래픽 감시로 데이터베이스에 관한 정보를 얻기 어렵게 합니다.



암호화 저장 모델> <데이터베이스 설계하기
Last updated: Fri, 24 Jul 2009
 
add a note add a note User Contributed Notes
데이터베이스 접속하기
M Zijlstra
17-Aug-2007 01: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 04: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 02: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 07:20
Obviously, this does not apply if PHP and the DBMS are running on the same machine.

암호화 저장 모델> <데이터베이스 설계하기
Last updated: Fri, 24 Jul 2009
 
 
show source | credits | stats | sitemap | contact | advertising | mirror sites