|
John Earl wrote: >2. Have someone like the CEO change the QSECOFR >password and put the password in a safe so that it is never >used. It might also be a good idea to disable QSECOFR. That way it could only be used to sign-on from the system console. >If you did that, what functions would you ever need to open >the safe for? So far I can think of only two. >Am I missing any others? Is there something obvious that I >am overlooking? The CHGDSTPWD command requires the person using it to be signed on as QSECOFR. Ed Fishel, edfishel@xxxxxxxxxx
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.