On Wed, 2005-05-11 at 08:46 -0700, Bill Wohler wrote: > Bill Wohler wrote: > > >> A Google search was unfulfilling and not relevant with my Debian system. > > s. keeling wrote: > > > Next time, go to lists.debian.org and search the mailing list > > archives. This (and many others) has been discussed here numerous > > times in the past. > > Paul Johnson wrote: > > > Already answered this month. Please search the archives. Summary > > answer: Don't allow logins from networks no legitimate users will be > > coming from. > > Paul and "s.", > > I *did* search the archives. I had hoped to avoid these sorts of > comments by mentioning that I had searched already. Perhaps you didn't > realize that Google indexes lists.debian.org and you can limit your > search to the archives with "site:lists.debian.org". > > Dennis' reply was helpful as he gave me the keywords to look for. Note > that the "SSH blocking" thread did not appear in at least the first > 100 hits of "ssh site:lists.debian.org". Since there were over 195,000 > hits, the thread would not be easy to find if you didn't have the > right keywords > > I hope solutions other than the one given above were presented. The > solution above can be done trivially with the firewall, but is > unusable since I log in from random places around the Internet.
I found that setting my ssh port to something other than 22 helped very much. As long as you know the new port number, then you should be able to do what you want. (The only prob I've had with using other than port 22 was with 'mpich' version 1, but version 2 overcomes that restriction but does requirement rebuilding applications) -- Michael Bane Atmospheric Physics Group University of Manchester -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
