Re: Fix Security (was: Paging file)

["John Earl" <john.earl@xxxxxxxxxxxxxxxxxx>]

Vern,

>
> IIRC, one reason for having QSECOFR sign on is related to the transfer of
> ownership and authority when restoring things.

That is a reason to signon with *ALLOBJ and maybe with *SECADM special
authority, but I can't imagine a legitimate reason for a software vendor to
require a "QSECOFR" signon.

And given the importance of protecting System Values,DST, and QSECOFR's
explicit access to the DST password reset, I'm beginning to imagine a number
of illegitimate reasons why a vendor might "require" QSECOFR to be the
loading profile.

jte

--
John Earl - CTO
The Powertech Group Inc. Seattle, Washington
www.powertechgroup.com  john.earl@powertechgroup.com

Phone: +1-253-872-7788
Fax:      +1-253-872-7904
--