|
Richard wrote:
I am currently evaluating two software packages. One requires it be installed by QSECOFR, the other only requires user class *PGMR. I have taken points off from the package requiring QSECOFR. When asked why, my response involved "having heard somewhere" it was an undesirable condition.
IMO, it depends on what the software package is going to do. If the package is not going to need any privileged capabilities, then requiring installation with a *SECOFR profile is mostly a cop out to avoid authority issues. If, however, the package is going to need privileged capabilities ... installing as with a *SECOFR profile is acceptable. Keep in mind, however, that sometimes the privileged capabilities a software package might need are not immediately apparent ... case in point: user profile handle switching without knowing the password requires higher privileges. If there's any situation where the package might have to switch user handles, a program in the package will need to adopt higher authority. david
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.