×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Thanks for the feedback. Adding the "directory" directives was just a
shot in the dark since I am not sure how CGIDEV2 handles permissions to
read the files in the IFS. Your post straightened that out. So let me
run this by you....
If, as both you and Kevin said, these files should be accessible to
QTMHHTP1 because that is the profile CGIDEV2 will run under, then
changing the permissions to have *RX for QTMHHTP1 on those files and
removing permissions for QTMHHTTP should fix the permissions
(correct?). That would also solve any problems with "stray" directives
that I might have (like the one you mentioned) because it seems that PHP
and Apache run under the QTMHHTTP user profile (at least it looks like
most of the files in my php apps have *RX permissions for QTMHHTTP on
them). If the files have only QTMHHTP1 permissions, then QTMHHTTP
(browsing) wouldn't be able to read them. However, I WILL remove the
directive since it isn't helping me and potentially could come back to
haunt me.
Pete Helgren
Value Added Software, Inc
www.petesworkshop.com
GIAC Secure Software Programmer-Java
On 1/26/2012 11:26 AM, Scott Klement wrote:
CGI programs do not typically run under userid QTMHHTTP. They run under
QTMHHTP1 by default. (Though, my shop, and others I've worked with like
to change this to make the user sign-in and access files under their own
authority.)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.