Conference lassie::ucx

5509.0. "Why FTP/INPUT=file.ftp needs an WRITE access to file.ftp ?" by AUBER::HO (Dung HO - TSC - France) Wed May 14 1997 09:49

	Hi,

	UCX 4.1 ECO 3

$ ftp lutece/user=ho/passw=secret/input=USERS7:[NOBRE]DUNG.ftp

%RMS-E-PRV, insufficient privilege or file protection violation

$ dir dung.ftp/sec

Directory USERS7:<NOBRE>

DUNG.FTP;2           [GUESTS_P,NOBRE]                 (RWED,RWED,RE,RE)

**************************************************************
%%%%%%%%%%%  OPCOM  14-MAY-1997 13:27:36.40  %%%%%%%%%%%
Message from user AUDIT$SERVER on LUTECE
Security alarm (SECURITY) and security audit (SECURITY) on LUTECE, system id:
48197
Auditable event:          Object access
Event information:        file access request (IO$_ACCESS or IO$_CREATE)
Event time:               14-MAY-1997 13:27:36.31
PID:                      30C034B3        
Process name:             HO              
Username:                 HO              
Process owner:            [GUESTS_P,HO]
Terminal name:            TNA4:
Image name:               LUTECE$DKA0:[SYS0.SYSCOMMON.][SYSEXE]UCX$FTP.EXE
Object class name:        FILE
Object owner:             [GUESTS_P,NOBRE]
Object protection:        SYSTEM:RWED, OWNER:RWED, GROUP:RE, WORLD:RE
File name:                _DSA47:[NOBRE]DUNG.FTP;2
File ID:                  (3954,13,0)
Access requested:         READ,WRITE
Sequence key:             0178CE69
Status:                   %SYSTEM-F-NOPRIV, insufficient privilege or object
protection violation
**********************************************************************

 It works fine when having WRITE access .

$ set file/prot=(w:rew) dung.ftp

 The question is why FTP/INPUT needs an READ,WRITE access in this case ?,
while an READ ACCESS is sufficient
 
 Thanks,

 Youngy

    I can see what it did.
    
    Please file an IPMT case to get this problem resolved.