Re: FTP on V3R2

[Carel Teijgeler <teygeler@xxxxxxx>]

tomh@simas.com wrote:

>
> Can someone tell me - is FTP included in the base OS/400 for v3r2?  If
> not, what do I need?
>
>
> Also, how do I go about restricting an FTP user to a certain directory
> on the 400?  Say that I've created a user profile called 'FTP01'.
> When the user establishes an FTP connection, they'll be prompted for
> their userid (FTP01) and password.  Once on, I want them to be locked
> into their 'FTP01' directory, and only be able to put/get files into
> that FTP01 directory.
>
>
> Be in mind that I don't know diddley about exit points...

Tom,

In addition to the remarks of Rob:

To get the FTP-user to the wanted library grant him authority to that
library; I discovered if an FTP-user has no rights on a library he
cannot assess objects.

Use the CWD (Change working directory) command in FTP to make that
library his current library.

Beware; an FTP-user can do a lot of things, although being limited on
the profile. (CRTDUPOBJ is allowed for instance), so some security
should be added. Herefore you need exit points.

In fact, IBM should take care of this: anything on the black box an be
secured with authorisation lists, *PUBLIC *EXCLUDE, etc., but since
TCPI/IP opens up that box nothing is secure any more.

In stead of exit points you can try to exclude *PUBLIC authority on
library QTCP and only grant some users rights. Or try the same thing
with user QTCP (changing the system value of the USRLIBL caused user not
to sign on anymore, because *PUBLIC had *EXCLUDE on those libraries in
the new list and Client Access over TCP/IP needs user QTCP somewhere,
somehow).

Perhaps this may help.

Regards,

Carel Teijgeler.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---