BJ> Squish places files in the outbound area in the 
 BJ> current setup with a umask of 600 instead of 660, 
 BJ> which then hangs BinkD from being able to properly 
 BJ> send outbound files.  Reception by BinkD and 
 BJ> processing by Squish is working.  So, I need to 
 BJ> change the umask for squish to 660, probably by 
 BJ> burring how squish is run under a shell script..... 
 BJ>  Or finding a rc file that is currently setting the 
 BJ> umask to 600 and change that to 660 for the account 
 BJ> squish is running under....
 WG>  
 WG> It's not the umask which is the problem -- it's 
 WG> actually the permissions maximus uses to create the 
 WG> files. A subtle difference -- here's how it works: 
 ...

Ah...  Ok....  I made an assumption that the easy route would take care of
things.....  Yes, we'll need to update the code for a unix/linux specific
issue.  I'll not worry about it for now....  I actually don't have a
problem with max's handling, because I intend to set the max binary to run
suid to the UID I install it on.  It's the Squish code that is causing the
problem, because squish deals with both Max and BinkD....  And I have BinkD
running under a differe UID but the same GID.

Keeping Max as is is probably more secure for how I am running at this
time.....  I'll admit that allowing GID setting would also be good for some
methods of running max....    Squish does need to be opened up.....

We may need to think more about this before making changes......

Take care.....

Bob Jones, 1:343/41
 

--- Maximus/2 3.01