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



Rob,

Actually this:
 
> EDTOBJAUT OBJ(MYLIB/MYOUTQ) OBJTYPE(*OUTQ)
> And removed access for *PUBLIC, wouldn't that be more effective?  You
may
> have to modify the
> CHGOUTQ OUTQ(xxxxxx) AUTCHK(???????)

...is not nearly as effect as you would hope.  Because spool file
security does not follow the normal rules of object level security,
removing access to an out queue does not prevent a user with *SPLCTL
special authority from seeing and/or manipulating spooled files on that
queue.  There are a number of methods of accessing the entries on the
queue that don't check a user's authority to the queue itself.  WRKSPLF
USER(JOHN) is the most obvious.

So while your suggestion is appropriate for most OS/400 object types,
and would actually thwart some access attempts (like WRKOUTQ
OUTQ(PRT09)), in the case of spool files, Special Authority trumps
again.

jte



John Earl - john.earl@powertechgroup.com
The PowerTech Group - Seattle, WA 
+1-253-872-7788 - www.powertech.com



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.