permissions issue on print to a file

[Richard D. Williams]

Fairlight wrote:

>This was something I'd never have seen had it not been up for approval, but
>it's just as well I did.  It deserves comment.
>
>----- Forwarded message from filepro-list-owner at lists.celestial.com -----
>  
>
>>From: "Brian K. White" <brian at aljex.com>
>>Date: Fri, 1 Dec 2006 16:15:31 -0500
>>Subject: Re: permissions issue on print to a file
>>
>>You need to create the file with open permissions beforehand, instead of 
>>allowing filepro to create it.
>>    
>>
>
>[snip]
>
>  
>
>>then: system "umask 0;>"{ee<";rreport ... -pc 
>>    
>>
>
>NEVER take this advice on using this methodology.  EVER.  Not if you value
>the security and integrity of the resultant files.
>
>Anyone intentionally using 'umask 0' deserves to have their system access
>yanked immediately, IMNSHO.  Anyone that can't see the inherent problems in
>doing so shouldn't even be using a *nix system that lets them gain access
>to a command prompt, but since someone lets them anyway, read this:
>
>http://www.fairlite.com/fc/articles/mode-essay.shtml
>
>'nuff said.
>
>mark->
>_______________________________________________
>Filepro-list mailing list
>Filepro-list at lists.celestial.com
>http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>
>  
>
Mark,

The sky in not falling.  These files are utilitory.  They are deleted 
soon after they are used.
After all, they do not contain secret information and I doubt someone is 
going to have access to the system in that directory, on that day, at 
that time and read the file within it's 5 or 10 minute life.

I will keep my *nix card and use Brian's suggestion.  It get's the job 
done and solves a filepro issue.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.celestial.com/pipermail/filepro-list/attachments/20061203/5ba6fa58/attachment.html