|
I've seen this happen before, and it usually means that the software house doesn't really understand security the way they need to. QSECOFR then becomes an easy way to install their code, and more importantly, keep it running. I'd get somebody to check them out. Run a security audit over that package.
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.