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 4A39B9DC85B for ; Sun, 12 Feb 2006 21:03:45 -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 67881-09 for ; Sun, 12 Feb 2006 21:03:48 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by postgresql.org (Postfix) with ESMTP id DCD339DC84D for ; Sun, 12 Feb 2006 21:03:42 -0400 (AST) Received: from [192.168.1.100] (or-67-76-146-141.sta.sprint-hsd.net [67.76.146.141]) (authenticated bits=0) by hosting.commandprompt.com (8.13.4/8.13.4) with ESMTP id k1D0qSVN022695; Sun, 12 Feb 2006 16:52:28 -0800 Message-ID: <43EFDB98.1060201@commandprompt.com> Date: Sun, 12 Feb 2006 17:06:32 -0800 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: Rodrigo Sakai CC: pgsql-admin@postgresql.org Subject: Re: Change port number References: <000f01c63041$49743d80$1401a8c0@netsis01xp> In-Reply-To: <000f01c63041$49743d80$1401a8c0@netsis01xp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (hosting.commandprompt.com [192.168.1.101]); Sun, 12 Feb 2006 16:52:29 -0800 (PST) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.085 required=5 tests=[AWL=0.085] X-Spam-Score: 0.085 X-Spam-Level: X-Archive-Number: 200602/154 X-Sequence-Number: 20575 Rodrigo Sakai wrote: > Hello all, > > 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. Joshua D. Drake > > Thanks. -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: PLphp, PLperl - http://www.commandprompt.com/