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

Steve,

> >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.
>
>
> disagree. the way it is now, if QPGMR owns the exit pgm, anyone in
the Qpgmr
> group can replace an exit pgm that was registered by an *allobj
user. The
> new pgm will be run by many different users on the system, some with
*allobj
> authority. Code in the new pgm could then check that the user is a
known
> *allobj/*secadm aut user and then do whatever it wants on the
system.

I think you are at the core of the issue here, and think I understand
our difference of opinion.  I feel quite strongly that no production
program (exit or other) should be owned by anyone's Group Profile (and
certainly none of _our_ objects should be owned by an IBM profile like
QPGMR).  Ownership of an object confers (among other things) object
deletion rights.  IMHO, the proper way to secure _any_ object against
replacement (and trojan horse introduction) is to have that object
belong to an "Owner" profile.  That "Owner" profile should not be
anyone's user profile, and it should not be anyone's group profile.

Every application should have an "Owner" profile that has no password
and is not a group profile.  The only purpose of an "Owner" profile is
to be the defualt owner of application objects.  Access to the
applicaiton is managed separately from ownership of the applications
objects.

Following this model, concerns about replacement of an exit program
(or any program) disappear.

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
+---