Chris, Strong
passwords aren’t going to continue to mean much with NT-based FTP
services; the username and password are passed in clear text to the server. If you must
use it, though, you can configure your FTP sites to only accept incoming
connections from your client’s IP addresses, providing those are limited.
If not, it’s going to be fairly hard to keep people from hitting
your server. You could also download and install IIS Lockdown to help
further harden your FTP server. Personally,
however, I’d install OpenSSH (http://www.openssh.org/)
and have your clients use SFTP to upload their files. You can then remove
FTP, which will get rid of port 20/21, and provide security for username and
password credentials passed in connection strings since SSH is encrypted. Cordially yours, From: Justin MacCarthy
[mailto:[EMAIL PROTECTED] More question than answers first .... Is it NT or Windows 2000 ? How are you coming to the conclusion that
it is FTP attack? Sure its not a DOS against the FTP port? What logs do you have ? Are you running any IDS system? Have you notified your ISP or upstream
provider of the attack Are your event logs filling up and being
corrupted? What other info do you have ? Are most of your users user your FTP from
static IP addresses? How long has the attack being going? What firewall are you using? Justin
|
- [ cf-dev ] OT: NT security problem Chris Tazewell
- RE: [ cf-dev ] OT: NT security problem Peter Harrison
- RE: [ cf-dev ] OT: NT security problem Peter Harrison
- RE: [ cf-dev ] OT: NT security problem Justin MacCarthy
- RE: [ cf-dev ] OT: NT security problem Jerry G. Young II
- RE: [ cf-dev ] OT: NT security problem Justin MacCarthy
- Re: [ cf-dev ] OT: NT security problem Taz
- Re: [ cf-dev ] OT: NT security problem Mark Woods
- RE: [ cf-dev ] OT: NT security problem Justin MacCarthy
- Re: [ cf-dev ] OT: NT security problem duncan . cumming
- RE: [ cf-dev ] OT: NT security problem Peter Harrison