| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
| Cc: | jd(at)commandprompt(dot)com, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, David Fetter <david(at)fetter(dot)org>, Kris Jurka <books(at)ejurka(dot)com>, 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 22:42:12 |
| Message-ID: | 26056.1227739332@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Marc G. Fournier" <scrappy(at)hub(dot)org> writes:
> <jd(at)commandprompt(dot)com> wrote:
>> Well they can still talk to the port of course but its irrelevant
>> because unless they have an ssh key, they aren't getting in. Period.
> Well, they weren't getting in before ... i twas the massive flood of attempts
> that was hurting :)
Yeah. So having a more secure login API won't help that a bit.
I don't have a problem with moving the ssh support to a nonstandard
port, but I do have a problem with the lack of notification about it.
Even core found out the hard way.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-11-26 22:56:27 | Re: What's going on with pgfoundry? |
| Previous Message | Marc G. Fournier | 2008-11-26 22:31:51 | Re: What's going on with pgfoundry? |