Paul Nicolay wrote:
If security means "obtaining a valid license for a licensed program"
then he needs it as hard as a standard user profile... having *ALLOBJ
won't help him a bit.
I don't disagree ... the security functions I'm talking about are things that you CAN do with higher authority ... case in point: The SCM product I work (MKS Implementer) has to adopt higher authority on occasion to do things that can't normally be done with the default authority we operate with. In those cases the we do bind by copy of modules so that the higher authority that we have cannot be hijacked.
In these cases, someone with *ALLOBJ authority generally doesn't *NEED* to hijack the higher authority, as they already have it.
As far as licensed product keys, I really don't know much about that mechanism ... as we have our own licensing system.
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