Re: What's going on with pgfoundry?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --On Wednesday, November 26, 2008 17:42:12 -0500 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
wrote:

> "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.

I just moved pgfoundry back to port 22, sinc eout of all of them, I believe
that one had the largest impact ... I would still like to move it back to 35 ...

Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkkt1b4ACgkQ4QvfyHIvDvPV1QCgyJBxAAPznvT8CK5Hx6Dj20Jy
BqoAoLAqPZfE6L7uANeHNrpavXZ7L0bt
=o3iw
-----END PGP SIGNATURE-----