Securing FTP/iX

ftp>
6.3.3.2 Permission Delete:
ü If a user lacks the SM capability and PERMISSION_DELETE is turned OFF, the user should not
be able to
delete a file:
ftp> delete strsyss
---> DELE strsyss
550 Command access denied, permission restricted.
Delete command "DELE strsyss" failed. (FTPERR 71)
ftp>
ü
When PERMISSION_DELETE is set to ON, users should be able to delete a file, again provided there are
no restrictions imposed by MPE/iX:
ftp> delete strerr01
550 Command access denied, permission restricted.
Delete command "DELE strerr01" failed. (FTPERR 71)
ftp>
6.3.3.3 Permission Overwrite:
The following are examples of overwriting a file when PEMISSION_OVERWRITE is set to ON and OFF
respectively. The FTP/iX user lacks the SM capability.
ftp> put FINFOHLP
200 PORT command ok.
150 File: FINFOHLP opened; data connection will be opened
200 PORT command ok.
150 File: FINFOHLP;REC=-256,1,V,ASCII;DISC=10000,8 opened; data connection will be
opened
226 Transfer complete.
8207 bytes sent in 0.00 seconds (8014.65 Kbytes/sec)
ftp>
ftp> put finfohlp
200 PORT command ok.
150 File: finfohlp opened; data connection will be opened
200 PORT command ok.
550 Command access denied, permission restricted.
Data Transfer Request Failed. (FTPERR 13)
ftp>
6.3.4 Configuring SETPARMS for Logging commands and transfers
Please refer to section 6.3 for details on SETPARMS configuration file.
Here is a sample listing of the SETPARMS.ARPA.SYS configuration file:
# Purpose: To log the FTP internal commands and data transfers between the FTP/iX server and a FTP/iX client.
Page
16
of
28
Secure FTP on MPE/iX
7/18/2008
http://jazz.external.hp.com/papers/Securing
-
FTP
-
Whitepaper.html