Re: What's going on with pgfoundry? - Mailing list pgsql-hackers

From Steve Crawford
Subject Re: What's going on with pgfoundry?
Date
Msg-id 492D9AAB.7060501@pinpointresearch.com
Whole thread Raw
In response to Re: What's going on with pgfoundry?  (Kris Jurka <books@ejurka.com>)
Responses Re: What's going on with pgfoundry?  ("Marc G. Fournier" <scrappy@hub.org>)
Re: What's going on with pgfoundry?  (Andrew Chernow <ac@esilo.com>)
Re: What's going on with pgfoundry?  (David Fetter <david@fetter.org>)
List pgsql-hackers
Kris Jurka wrote:
>
>
> On Wed, 26 Nov 2008, Dave Page wrote:
>
>>
>> It's the same IP address - but try port 35 for ssh. Marc changed it
>> (temporarily) due to a vast number of malicious connection attempts.
>>
>
> Why wasn't this change communicated to anyone, not even gforge-admins? 
> How temporary is temporary?
>
> Kris Jurka
>
I can't speak to the administrative and communications aspects, but 
based on my experience, I can recommend communicating to the appropriate 
users and making the change permanent.

I have changed the external ssh port on all machines I administer. The 
result is the complete elimination of the previous hundreds to thousands 
of daily script-kiddie brute-force attempts I used to see.

Obscurity should not be your *only* line of defense, but camouflage 
helps as well. And even if it didn't, it still reduces server-load, 
bandwidth and heaps of logfile cruft.

Cheers,
Steve



pgsql-hackers by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Re: [bugfix] DISCARD ALL does not release advisory locks
Next
From: "Marc G. Fournier"
Date:
Subject: Re: What's going on with pgfoundry?