|
Booth, this is less of an issue than it might appear. Although I'm NOT necessarily contradicting what Leif has been saying. The 3rd party vendors that I've dealt with back in the days of yore (JDE, Lawson, Synon, and ProData too, probably) ALREADY took whatever authority they wanted. Almost EVERY package I've EVER loaded had the first instruction of the install state "Sign on as Security Officer". Never much cottoned to that, but it was "Generally Accepted Computer Practice", back 10 or 20 years ago... I'm guessing it still is these days. jt | [mailto:midrange-l-admin@midrange.com]On Behalf Of Booth Martin | So, what you are saying is that any third-party vendor with a | bloated sense | of self importance could decide he needs a trifle more authority | to make his | software as effective as he'd like it to be, so he could quietly just take | what ever he wants and no one would be the wiser? | | It isn't malware thats the serious problem, its egoware. These 3rd-party | vendors have the know-how and resources to do just what you have laid out. | If I've read you right this could become our own version of "DLL Hell"? | | Suddenly I feel this real cold draft blowing down my shirt collar.
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.