|
Mike, >2.) Think about the ability of users to run commands outside of the >command line process - remote commands, 3rd party software command >lines,etc. A PC user with the ability to run remote commands won't be >stopped by the limited access setting. I won't name names but we have a >3rd party software that provides their own menu system and command line >interface - guess what - limited capability is never brought into play. but object level security still applies for this kind of access, doesn't it? I see we will need to look into some of these security utilities. I understand, without some kind of exit-point programming, you can't stop this remote access? Thanks, OLiver
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.