×
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.
The auditors at my client have told the admins that QALWOBJRST needs to be
set to *ALWPTF because *ALL is a security risk. Is *ALL really a security
risk?
My argument for *ALWPGMADP is that if someone restores a program that adopts
authority and they do not have access to the owner profile, during the
restore the OS changes the owner to QDFTOWNER (or something like that) which
does not have any authority so who cares if it adopts its authority.
The other options (*ALWSYSSTT, *ALWSETUID, *ALWSETGID, *ALWVLDERR) I don't
really know what these are so I can't intelligently speak about them. Thus,
I am turning to the knowledgeable people of this group.
So, is there a good reason to not have *ALL?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
