This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: UPDATE: Active FTP Issue with inetutils 1.5

>I'm currently in the process of rebuilding all of "my" packages;
>inetutils is on the list and I'm making good progress plowing through
>that list. So, I should be able to get to it soon; most likely within
>the next week or two.
>Thank you for doing such a thorough job tracking this down. I saw your
>first message on this topic, and frankly I had no idea why the behavior
>changed from 1.3.x, nor if it was intentional upstream. Sergey was the
>right person to answer your quesstion, and I'm glad you followed thru on

Thanks for the response.  The reason that I dug into this is that this
impacted the customers we service remotely.  We've also noticed the
certain implementations of Sonic firewalls create the same issue but
in their case they are proxying FTP more so than just passing it
though... I think.

This FTP issue also impacted access lists on Cisco routers and
probably others.  An access-list is dumb but has the ability to allow
the "ftp-data" port to come back through.  This is just a dumb access
list looking at the source or destination with port 20.  Firewalls
don't have this issue because the inspect the PORT command on the
control channel to allow the data connection back the "port"

Since we use inetutils ftpd and we have access lists in certain places
we've had to redo our access lists and do all the inspection of these
things at our firewalls.  If you think about  what this does on FTP is
you see an IP connecting to another IP and both are using high order
"random" ports.  That makes it almost impossible to implement any kind
of security without doing packet inspection.  We have customers that
may only have low end gear and use access lists so we're trying not to
impact our customers by this.

Anyway I thank you for your help and hope that you'll be able to have
a new fix for this soon.  I realize this is all on a voluntary basis
so I appreciate the effort on your end to maintain and port the code.
It's a great package.


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]