David Gibbs wrote:
Replacing or renaming an existing object is probably harder than
putting a new object higher on the library list. One would assume
the existing object is secured so it can't be changed in a production
environment. Creating a new object and putting it higher on the
library list isn't going to be nearly has hard.

I'm picturing that you work for a software house, and that the "security software" is to check to make sure the user has a valid, non-expired, license code.

In that case, you may very well have users with *ALLOBJ authority who are trying to bypass your security, so securing the object won't help you.

I agree that a *LIBL exploit is easier -- but not much easier.

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].