Re: Using QSYRUPWD to write a script file

[Bruce Vining <bvining@xxxxxxxxxxxxxxx>]

True for the Validate Password exit, but the Check Password exit program
(available since V5R4 and documented at
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/xsyckphr.htm)
gives you control for CRTUSRPRF, CHGUSRPRF, CHGPWD, and the QSYCHGPW API.

Bruce
On Thu, Sep 27, 2012 at 6:50 AM, <rob@xxxxxxxxx> wrote:

> Catching up on email...
> But the change password exit point could then be used to store the new
> password (encrypted).  Exit point is only called on CHGPWD (and it's gui
> equivalents).  Not on CHGUSRPRF.
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   "Monnier, Gary" <Gary.Monnier@xxxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
> Date:   09/24/2012 04:10 PM
> Subject:        RE: Using QSYRUPWD to write a script file
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> Cyndi,
>
> Have you thought of using the Encrypt data api QC3ENCDT and Decrypt data
> api Q3DECDT to build your own secured storage for the user ID and
> password?  You could then change your RPG program to decrypt the user ID
> and password when the ftp script is written.
>
> If you don't want to create your own secured storage there are companies
> out there that sell encryption solutions.  Townsend Security is one that
> comes to mind.
>
> Gary
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [
> mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Cyndi Bradberry
> Sent: Monday, September 24, 2012 12:57 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Using QSYRUPWD to write a script file
>
> I had planned on changing it to clear the script file immediately after
> the FTP process, and yes, these are hundreds of batch processes.
> Currently, the user name and password are hard-coded into the RPG that
> writes the script. Was looking for another way. We have just begun the
> SAS70/SAE16 audit of IT. I figured that they would catch it eventually, so
> I thought I'd start looking.
>
> Thanks again.
>
> Cyndi
> --
> 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.
>
> --
> 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.
>
>
> --
> 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.