On 08-Mar-2012 10:44 , CRPence wrote:
On 08-Mar-2012 10:18 , Jon Paris wrote:

<<SNIP>> Funny thing is the problem came to light in a scenario
where a utility is QTEMP adding QTEMP to the LIBL, but it fails
because it is already there in the _System_ portion!

Now that's security.


Since the OS intends to prevent QTEMP from ever being in the SYS
portion of the library list, e.g. by error cpd0009 "Parameter
SYSLIBLE value cannot be QTEMP." for CHGSBSD SYSLIBLE(QTEMP), and I
believe similarly for the LIB parameter of the command CHGSYSLIBL,
there is already something suspect about the /security/ on any system
where that error could have transpired as described.


That should have noted cpd0090 "Parameter ...". And I believe I had recalled incorrectly that CHGSYSLIBL also does not allow QTEMP. So an "Oops" on that too probably, as I believe the error on CHGSBSD was merely a false reinforcement for my poor recollection.

The restriction I believe was instead via the typical [default] /security/ per authority to the command being *PUBLIC *EXCLUDE, such that there is the general inability for a _user_ to effect QTEMP being in the system portion of *LIBL; i.e. generally the change is effected only via adopted authority. I actually tried to test my recollection in advance of posting, but the system to which I have access, I am prevented by authority from using the CHGSYSLIBL :-(

Regards, Chuck

This thread ...


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

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 on our policy page. If you have questions about this, please contact [javascript protected email address].