|
Given that you can write a command processor program, so can anyone else. All someone needs to do is call their own command processor to get around yours. And really neither exit points nor routing entries nor command overrides will be able to change that. If you want to completely prevent any program that could possibly act as a command processor from circumventing your specific command restrictions, then you are going to have to have the source of them all because none of them have to use the exit points or routing entries. You are left with object security, and all that can do is allow or disallow access to an object for a particular user or group of users.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.