I suggest that you remove authority to
the command line for all users - they don't need it. If you require a new
version of WRKOUTQ, the old S/38 (pre TAATOOL) even then had examples of
converting the WRKOUTQ OUTPUT(*PRINT) command and from this you could build an a
program that allows them do everything else bar delete. In fact, you could
even ignore job logs, service dumps, etc.
In the world of "open" environments
there should always be doors that only open for a few.
----- Original Message -----
Sent: 03 November 2000 08:46
Subject: Re: QPJOBLOG security
That would be my first attempt at subverting
the security scheme :)
01:19 PM -0800, you wrote:
>>P.S. For you security sleuths out
there: there is at least one potential
>>security flaw in this design
that made us unable to gauranty that no one
>>their own spool files. Can you find
> The user can hold or delete the spool before it ever
> status. How'd I do?
| This is the Midrange System Mailing List!
submit a new message, send your mail to MIDRANGE-L@midrange.com.
subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
Questions should be directed to the list owner/operator: firstname.lastname@example.org
This thread ...
- RE: QPJOBLOG security, (continued)
This mailing list archive is Copyright 1997-2019 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 here. If you have questions about this, please contact