• Subject: Re: V5R1 DST passwords
  • From: "Leif Svalgaard" <leif@xxxxxxxx>
  • Date: Sun, 8 Jul 2001 10:02:48 -0500

IBM clearly panicked here (possibly because of the recent password
flaws and other security exposures). Making it more complicated to
manage is not the right way of tightening security; on the contrary,
you force people to take countermeasures (such as writing the
current password on a sticker attached to the console)
.

----- Original Message -----
From: <barsa@barsaconsulting.com>
To: <MIDRANGE-L@midrange.com>
Sent: Sunday, July 08, 2001 9:36 AM
Subject: RE: V5R1 DST passwords


>
> To make matters worse, you password has to be different from the last 4
> passwords.
>
> Al
>
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
>
> 400>390
>
> 914-251-1234
> 914-251-9406 fax
>
> http://www.barsaconsulting.com
> http://www.taatool.com
>
>
>
>
>
>
>                     "Hall, Philip"
>                     <phall@spss.com>           To:
"'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
>                     Sent by:                   cc:
>                     owner-midrange-l@mi        Subject:     RE: V5R1 DST
passwords
>                     drange.com
>
>
>                     07/07/01 11:49 PM
>                     Please respond to
>                     MIDRANGE-L
>
>
>
>
>
>
> > They've added the CHGDSTPWD command to reset DST QSECOFR to
> > QSECOFR. Now
> > here's the kicker - the password for DST is case sensitive
> > (as I forgot
> > today, typing in qsecofr time and time again when only
> > QSECOFR will work).
> >  You then need to change the password, but it seems that this
> > follows its
> > own rules - even if QPWDRQDDIF is set to 0, you can't
> > duplicate an old
> > password for the DST profile.
> >
> > So pretty easily, DST password management can become an issue
> > - especially
> > since you may not be going into SST that often.
>
> If I remember correctly, the passwords also auto expire after 180 days, to
> give you even more of a potential headache...
>
> --phil
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
>
>
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.