Joe Pluta wrote:
I was thinking more along the lines of binding the security into the
bound program, not a service program.

I concur.

I would not bind the security routines into a service program for the reason I stated previously.

Also, the signature isn't quite enough - you'd have to do a
man-in-the middle attack, although that's pretty simple. Just write
your own procedure with the same signature that calls the existing procedure, and record the inputs and outputs until you figure out how
to respond affirmatively to a challenge.

Depends on what kind of mischief you want to accomplish ... if it's just modifying some data that the secured routine has authority to, then your new routine doesn't necessarily need to do anything after that. Maybe throw an exception message after the mischief is completed and chalk it up to a bug.

david



This thread ...

Replies:

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