[Info-vax] Need to set up a special purpose account

[Tom Adams]

On Monday, October 10, 2016 at 10:16:37 AM UTC-4, Steven Schweda wrote:
> > It works if I set the OWNER of the file:
> > SYS$SYSDEVICE:[TCPIP$FTP]TCPIP$FTP_ANONYMOUS.LOG
> > to [ANONY,ANONYMOUS]
> > it was set to [SYSTEM]
> 
>    It might also work if you set it (back) to what it should
> be.

I think a found the root of the problem.

There was an old SYS$SYSDEVICE:[TCPIP$FTP]TCPIP$FTP_ANONYMOUS.LOG
file from 1995.  I don't know how it was created.  It might date
back to UCX since some files somehow have alias names for UCX and
TCPIP.

If I get rid of that file and then run tcpip$config.com to add the optional anonymous tcpip, then it all works.

It's not a bug it's a feature.  When you enable the ANONYMOUS TCPIP option, it does not create a new TCPIP$FTP_ANONYMOUS.LOG, so if the one there is screwed up, then you are screwed.

The file TCPIP$FTP_ANONYMOUS.LOG, when properly created, has an ACL that gives [ANONY, ANONYMOUS] access.

On our system TCPIP$FTP_ANONYMOUS.LOG got created back in 1995. Perhaps someone experimented with turning on anonymous ftp and then removed the account and directory but not the log file. The protections of the file somehow became incompatible with TCPIP, perhaps due to upgrades of UCX and TCPIP.