Re: Weak LAN Manager hashing permitted -- 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.

Subject: Re: Weak LAN Manager hashing permitted
From: Rob Berendt <rob@xxxxxxxxx>
Date: Wed, 4 May 2016 07:09:56 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

<snip>
What's your QPWDLVL set too?

LM passwords are not allowed at level 1 or level 3.
</snip>

<snip>
If IBM i bind non specific issue I suspect the resolution will be to
upgrade our QPWDLVL from 0. We're planning on going to 2 shortly anyway.
Already increased it to 2 on one sandbox lpar.
</snip>

Is level 2 no good in resolving this then?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Weak LAN Manager hashing permitted , Charles Wilt
Re: Weak LAN Manager hashing permitted , Rob Berendt

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.