| From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Kris Jurka <books(at)ejurka(dot)com>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, Dave Page <dpage(at)pgadmin(dot)org>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: What's going on with pgfoundry? |
| Date: | 2008-11-26 21:57:40 |
| Message-ID: | 492DC654.8000707@pinpointresearch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Fetter wrote:
>
>
> We should move to a port-knocking
> <http://dotancohen.com/howto/portknocking.html> or other modern
> strategy if we're going to move at all.
>
>
Yeah, but telling my firewall to move port 22 inside to port xxxx
outside took less time than writing this email. Inside the firewall
plain old ssh continues to work fine and I don't have to deal with
issues of forwarding additional ports through the firewall, mucking with
iptables rules, etc.
For my servers, moving outside access to a non-standard port has proven
100% effective for over a year so additional complexity hasn't been
warranted.
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-11-26 22:00:59 | Re: What's going on with pgfoundry? |
| Previous Message | Kevin Grittner | 2008-11-26 21:52:33 | Re: Simple postgresql.conf wizard |