|
> And given the importance of protecting System Values,DST, and > QSECOFR's explicit access to the DST password reset, I'm > beginning to imagine a number of illegitimate reasons why a > vendor might "require" QSECOFR to be the loading profile. Reminds me of the <to-remain-nameless> vendor(s) that require QSECOFR so that they can, oh you know, use the virtual terminal API's to then use SST to patch their objects to system state after install...completely hidden from the poor guy doing the install... Not as easy now under V5R1 since SST is password protected. --phil
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.
midrange.com
