|
Two points to this. Read both. First, I goofed. Instead of changing message TCP11AF in message file QTCP/QTCPMSGF (and any other NLS libraries you may have loaded) from '230 &1 logged on.' to '230 User logged on.', I accidentally dropped the 230 part. This locked all users out of ftp. The 230 is required by the RFC's etc. Second point. If you want to cause major grief for any client accessing ftp instead of one you created you can go ahead and make a change like the above. Then in your custom written client you can violate this RFC and make this perfectly acceptable. Maybe even change the 230 to a 530. Granted it is a little like 'security by obscurity'. Personally, I think the exit points are a better way to handle security. But enforcing your client may help in those cases in which you want to ensure a certain action is performed in a certain sequence. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.