Re: chgc0100 exit point. was Default for command without default value?

>>You must have *AllObj and *SecAdm to register an exit pgm.  Should
not
> the exit pgm itself have to be owned by a profile with
*AllObj/*SecAdm ?
>
> That sounds like a good idea.

Not really.  It's possible that I may want to use an exit program that
would adopt it's owner's authority, but not necessarily *ALLOBJ
authority.  The restriction of requiring *ALLOBJ and *SECADM to
register the exit program is sufficient, requiring the exit program to
be owned by an *ALLOBJ profile would be onerous.


> >>Otherwise, careless managing of the exit pgm could result in an
exit pgm
> running code you dont want it to run.
>
> What you are talking about is using this as another way of
introducing a
> Trojan horse into the system. The exposure you describe is basically
the
> same exposure that exists for other exit programs. If you care about
> security you need to manage the public and private authorities of:
> - All programs and commands that are run by someone with lots of
authority.
> - The validity checking program that has been added to any CL
command.
> - All commands placed in a library that is ahead of QSYS in the
library
> list.
> - Any library that is placed ahead of QSYS in the system part of the
> library list. Anyone that has authority to create a new program or
command
> in this library has the ability to create a Trojan horse program or
> command.


All of the above are just examples of how a person who has *ALLOBJ
authority can compromise your system in an infinite number of ways.  A
good approach is to make security work right up to the point that
someone acquires *ALLOBJ authority.  At that point, it is impossible
to secure anything from that person, so stop trying. The restriction
on exit program registration is sufficient, more than that and you
start to limit function without providing additional security.

jte






+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To 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: david@midrange.com
+---