Re: Change port number

From: Christopher Browne <cbbrowne(at)acm(dot)org>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Change port number
Date: 2006-02-14 13:26:23
Message-ID: 87mzgurs00.fsf@wolfe.cbbrowne.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

In the last exciting episode, rodrigo(dot)sakai(at)poli(dot)usp(dot)br ("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, it would presumably protect against certain kinds of "script
kiddie" attacks which assume that PostgreSQL can only ever run on port
5432.

It won't protect terribly much against a concerted attack.

We use variant port numbers a lot because we have multiple database
instances in our environments. The measure isn't "protective" so much
as it is necessary, since at most one instance can use port 5432...
--
let name="cbbrowne" and tld="gmail.com" in String.concat "@" [name;tld];;
http://linuxdatabases.info/info/internet.html
"I heard that if you play the Windows CD backward, you get a satanic
message. But that's nothing compared to when you play it forward: It
installs Windows...." -- G. R. Gaudreau

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Mike Lott 2006-02-14 14:25:20 Possible to check integrity of restored database?
Previous Message Arnau 2006-02-14 11:38:13 pg_xlog location