pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Re: Change port number
4+ messages / 4 participants
[nested] [flat]

* Re: Change port number
@ 2006-02-13 01:06  Joshua D. Drake <jd@commandprompt.com>
  parent: Rodrigo Sakai <rodrigo.sakai@poli.usp.br>
  1 sibling, 1 reply; 4+ messages in thread

From: Joshua D. Drake @ 2006-02-13 01:06 UTC (permalink / raw)
  To: Rodrigo Sakai <rodrigo.sakai@poli.usp.br>; +Cc: pgsql-admin

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/




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Change port number
@ 2006-02-13 01:13  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Joshua D. Drake <jd@commandprompt.com>
  0 siblings, 0 replies; 4+ messages in thread

From: Tom Lane @ 2006-02-13 01:13 UTC (permalink / raw)
  To: Joshua D. Drake <jd@commandprompt.com>; +Cc: Rodrigo Sakai <rodrigo.sakai@poli.usp.br>; pgsql-admin

"Joshua D. Drake" <jd@commandprompt.com> 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



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Change port number
@ 2006-02-13 02:00  Rodrigo Sakai <rodrigo.sakai@poli.usp.br>
  0 siblings, 2 replies; 4+ messages in thread

From: Rodrigo Sakai @ 2006-02-13 02:00 UTC (permalink / raw)
  To: pgsql-admin

  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?

  Thanks.

^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Change port number
@ 2006-02-14 13:26  Christopher Browne <cbbrowne@acm.org>
  parent: Rodrigo Sakai <rodrigo.sakai@poli.usp.br>
  1 sibling, 0 replies; 4+ messages in thread

From: Christopher Browne @ 2006-02-14 13:26 UTC (permalink / raw)
  To: pgsql-admin

In the last exciting episode, rodrigo.sakai@poli.usp.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



^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2006-02-14 13:26 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-02-13 02:00 Change port number Rodrigo Sakai <rodrigo.sakai@poli.usp.br>
2006-02-13 01:06 ` Joshua D. Drake <jd@commandprompt.com>
2006-02-13 01:13   ` Tom Lane <tgl@sss.pgh.pa.us>
2006-02-14 13:26 ` Christopher Browne <cbbrowne@acm.org>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox