× 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.



For a test I changed a test system to password level 2

After the IPL I was able to log on with the same password as before in
both uppercase and lowercase and mixed case would fail.

Eg

USERA PW: PASSWORD Successful logon

USERA PW: password Successful logon

USERA PW: PassWord Fail log on

OK That is what I expected from the reading I did.

Then if I change the password to say NEWPASS I can only log on in
uppercase

And when I run the PRTUSRPRF TYPE(*PWDLVL) I still see that for USERA *YES
for Passwords for level 0/1 and 2/3 and netserver.

So the old password will continue to work in either case but not mixed
case until the password is changed, then will only work in the new
passwords case.

And if no passwords were change to not meet password level 0/1
requirements then we could go back to level 0/1 without any issues.

OK I have also tested all other connections and everything seems to be
working as expected.

Yes I will more than likely just go straight to level 3 on the other
system where this is required.

Cheers

Don





From: "Rob Berendt" <robertowenberendt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 22/03/2023 10:09 PM
Subject: Re: Changing from password level 0/1 to 2 (QPWDLVL)
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



Do not mess with QPWDLVL 2. Go straight to 3. We tried baby stepping and
going to 2. All that caused was us doing another IPL midweek to get to
level 3. Since we're normally only allowed to IPL once per quarter this
was not popular. Level 2 is only useful over level 3 if you're running
extremely ancient versions of Windows. We have to pass audits so that's
not us.
Knowledge center has it well documented on how to get to higher levels and
what to watch out for. And, dropping to a lower release is more problem
than just an extra IPL. That's also documented at
https://www.ibm.com/docs/en/i/7.5?topic=security-planning-password-level-changes

Hey, I just noticed there's a password level 4! I'll have to check that
out.

On Tue, Mar 21, 2023 at 8:28 PM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Hi Team,

I have been reading up on this as one client we look after is wanting to
introduce longer passwords.

After reading, a couple of times I was not sure what issues may arise
for
intersystem connections if one or more are on password level 0/1 and one
is on password level 2.

For example we connect using telnet mostly secure on port 992 but also
some on port 23, we also use ftp between a lot of systems, ssh and we
have
PHP accessing with XMLSERVICE

As this requires an IPL to implement it is not a super quick option to
revert back to the previous level.

Can you share your experience and difficulties in changing QPWDLVL to 2

Thanks

Don



--
This email has been scanned for computer viruses. Although MSD has taken
reasonable precautions to ensure no viruses are present in this email,
MSD
cannot accept responsibility for any loss or damage arising from the use
of
this email or attachments..
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.