|
Where will that user & pwd be stored?Aaron's recommend for the FTPTOOL software is a program that control's the exit point for ftp serving. I am not a FTPTOOL user so cannot describe it exactly, but an exit program allows you to act as the gatekeeper and decide if a ftp transaction should be allowed. FTPTOOL and other
Exit Program packages may offer various levels & methods for this control.FTP can send files, retreive files, read, make & remove directories, execute commands. With such power you would want control & logging. The exit pgm could revoke all but a specifc file from a specific location.
The QHST logs do not log ftp activity. The job logs for the serverprograms, at their default logging level, do not really log much. So the exit point is prob the best point to log exactly whats going on & when. Just because you specify inlmnu=*signoff doesn't mean any pc user with the ftp user/pwd can't log onto the i's ftp server. Again exit pgm can control that.
FTP will respect object authority.I run a customer's box, sending & receiving files all day from customers & vendors, and wouldn't do it without an exit pgm and the security audit on. Because the customer's network security is only "moderate" we get many scripted ftp attempts every day from outside the network. No problems in 6 years, but i can see the risk.
For "best practices" others can speak to, but consider ssl. Jim Franz----- Original Message ----- From: "Chuck Lewis" <chuck.lewis@xxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, January 02, 2007 4:18 PM Subject: FTP user question
Hi Folks,We are working with a vendor and one of their software applications needs todo some FTP work and we need to set up a user profile for this on the iSeries. What are "best practices" for something like this ? It will be embedded in an application and the application is pointed to a specific folder on the IFS.I was wondering if setting INLMNU(*SIGNOFF) would still allow it to work OK.Any other recommendations ? Thanks ! Chuck --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.