Re: disable all Q* ibm supplied profiles and chaning default passwords -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hi, Jim,

One interesting wrinkle ... you can sign-on to a user profile that has a password set to *NONE, if you are on a system that is using EIM/SSO.

Only if you *DISABLE the profile, can you totally prevent it from being used to sign-on interactively.

This does not prevent those profile(s) from being used to run batch jobs or "services."

Just saying ...

Mark S. Waterbury

On Wednesday, October 9, 2019, 8:19:09 PM EDT, midrange <franz9000@xxxxxxxxx> wrote:

I think this thread has pointed out some of the misconceptions that surround
ibm i security.
One point that I've not seen yet - there is a difference between
a. disabling a profile
or
b. changing a default password to *NONE (to never be used to sign on)
Carol Woodbury's books recommended QPGMR, QSRV, QSRVBAS, QSYSOPR, QUSER all
to set to *NONE
The profile can be used by parts of the OS, but not to log in.
New releases come this way, but if you are carrying 30 years of baggage,
restoring to new hardware, it takes some cleanup.

Jim Franz

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.