Re: Question about support related to Windows 7

Just to bring an orderly close to the topic. The Windows 7 issue has been
resolved.

In iSeries Navigator Properties, The entry "require clients to sign
requests" has three possibilities - Yes, No, and Optional. It needs to be
set to Optional, and then the server needs to be started.

It is changed on a box titled (on v5r4 anyway) iSeries NetServer Security
Next Start.

John McKee.


On Mon, May 20, 2013 at 11:14 AM, CRPence <CRPbottle@xxxxxxxxx> wrote:

So to be sure... You are confirming that the password of Q7CHARLIE
*is* [treated] the same as 7CHARLIE and thus that the documentation is
lacking that clarification [just as there is no mention on the limit to
the password length] because it seems to allude only to all-digit
passwords [just like the other link I provided].? Therefore the
documentation might best have stated instead of "and the password is
numeric", suggested that "and the first character of the password is
numeric" and to have used an example that was not all-digits to avoid
false inferences from the example.? And presumably the rules are
consistent with what happens for the User Profile names as well.?

Regards, Chuck

On 20 May 2013 05:21, Raul A. Jager W. wrote:

The Q will allow a password that begins with a digit, it may have
letters after. The password that begins with Qdigit can only have
9 characters (10 counting the Q)

CRPence wrote:

A password can start with the letter Q with no more issues nor
restrictions, than whatever would be the concerns for a password
that starts instead with the letter P. The Q prefix shenanigans is
specific to a password that is [or should be recognized as being]
all digits. That is why the password Q1234 is *the same as* 1234. I
am almost positive that a password of Q7CHARLIE is *not* the same
as 7CHARLIE; I am not interested in trying, and I can not find any
documentation about the effects.

I did however find one presumably reliable source that states the
issue is specific to when the letter Q is "followed only by digits"
as applied to either a User Profile name or a password of a
*USRPRF:
http://securemyi.com/nl/wDec052012.html

I guess had I continued reading the above, I would have seen that
the documentation can be found in the "Help text of the CRTUSRPRF
(Create User Profile) command." Thus a doc link, even if not a very
thorough explanation is included below. No surprise I could not
find it, because neither "letter Q" nor "all digits" appear. There
is no clarification that the Q prefix implicitly limits an
all-digit name or an all-digit password to only nine characters
instead of the typical ten:
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/cl/crtusrprf.htm
"_User profile (USRPRF)_
Specifies the user profile to be created. A numeric user profile
can be specified. If the user profile is numeric, it must begin
with a Q.
...
_User password (PASSWORD)_ When the system is operating at
password level 0 or 1 and the password is numeric, then the
password must begin with a Q, for example, Q1234 where 1234 is
the password used for signing on the system."

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.