X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 55A649DCA52 for ; Sun, 12 Feb 2006 21:13:52 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 74468-05 for ; Sun, 12 Feb 2006 21:13:55 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 322C29DC93C for ; Sun, 12 Feb 2006 21:13:50 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k1D1DidJ001835; Sun, 12 Feb 2006 20:13:44 -0500 (EST) To: "Joshua D. Drake" cc: Rodrigo Sakai , pgsql-admin@postgresql.org Subject: Re: Change port number In-reply-to: <43EFDB98.1060201@commandprompt.com> References: <000f01c63041$49743d80$1401a8c0@netsis01xp> <43EFDB98.1060201@commandprompt.com> Comments: In-reply-to "Joshua D. Drake" message dated "Sun, 12 Feb 2006 17:06:32 -0800" Date: Sun, 12 Feb 2006 20:13:44 -0500 Message-ID: <1834.1139793224@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.109 required=5 tests=[AWL=0.109] X-Spam-Score: 0.109 X-Spam-Level: X-Archive-Number: 200602/155 X-Sequence-Number: 20576 "Joshua D. Drake" writes: > Rodrigo Sakai wrote: >> I have a question about changing the port number of Databases >> server. It was told to me that is a good administrative practice to >> change the port number of the services, like change the 5432 to 6985 >> or any other number. This is for security reasons. Is really a good >> practice? > Well, not really. Anyone who wants to get in, is just going to scan your > ports to find out what is open anyway. What you really need to do > is have a decent firewall in place and correctly configure postgresql > from the beginning. It's just "security by obscurity". Now there's nothing wrong with that, as long as you realize that it's only one obstacle in the path of an attacker, and not a very large one. Use it as one component of your security plan, but not the only one. regards, tom lane