Seriously, I never install anything under QSECOFR. If something did
actually require use of QSECOFR to install I would tell the vendor to
fix it before I would install it. If IBM can avoid requiring QSECOFR
access for everything except the OS I would say that everyone else
should too.

I read statements like this and shrug my shoulders. Do you refuse to use
TAATOOL because it requires installation as QSECOFR? So much the worse
for you.

Does your change management software install as QPGMR? If so, how does it
promote software to production level, which presumably is run as something
other the QPGMR? If your change management software can truly control
what gets moved into production, what difference does it make whether it's
installed as QSECOFR or not? It already has access to the very reason for
having the system.

Even more questionable: if I install IBM's Advanced Scheduler, I do so as
QSECOFR since it's "part of the operating system". If I choose to use
Robot, I shouldn't install it under QSECOFR because it isn't? They both
do the same thing. What's the difference?

I'll certainly agree that too many packages run under faulty security
schemes. But saying that you won't install anything other than the
operating system as QSECOFR either limits the usefulness of your system or
is completely disingenuous.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.