× 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.


  1.  Home
  2. MIDRANGE-L
  3. August 2017

Re: Rename WRKUSRPRF

what's the gain in renaming WRKUSRPRF. If someone has *SECOFR he can do a lot of damage.
You must think about auditing or rethink about the increased access rights.

-h




Am 29.08.2017 um 22:01 schrieb James Rich <james@xxxxxxxxxxx>:

For reasons beyond my control or influence, a user on a system has been granted QSECOFR authority. We're concerned about a number of problems with that, but mostly the use (abuse) of the WRKUSRPRF command.

Are there problems with renaming QSYS/WRKUSRPRF? Can I simply RNMOBJ OBJ(QSYS/WRKUSRPRF) OBJTYPE(*CMD) NEWOBJ(NEWUSRPRF) and still be ok?


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.