[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

2023.0. "Change Password function" by KERNEL::SMITHERSJ (Living on the culinary edge....) Tue Dec 29 1992 12:15

    A customer is using 5.4-2 with ALL-IN-1 3.0.  He has set 
    the sysgen parameter LOAD_PWD_POLICY to be 1, so that the routine
    calls a site specific file called SYS$LIBRARY:VMS$PASSWORD_POLICY.EXE.
    You can compile the file so that when you change your password at
    DCL, you can add your own site specific routines.  If you use 
    the example in sys$help, when I use $set password it displays
    my password.
    
    However, this routine is not being called from within ALL-IN-1.
    Can anyone tell me how CHANGE_PASSWORD works and if it is possible
    to use this routine from within ALL-IN-1?
    
    Many thanks
    julia
    UK CSC

T.R Title User Personal
Name Date Lines

2023.1 Description of CHANGE_PASSWORD filtering SCOTTC::MARSHALL I'd rather be skiing Mon Jan 04 1993 10:26 36

T.R	Title	User	Personal Name	Date	Lines
2023.1	Description of CHANGE_PASSWORD filtering	SCOTTC::MARSHALL	I'd rather be skiing	`Mon Jan 04 1993 10:26`	36
	Hi Julia, >> can anyone tell me how CHANGE_PASSWORD works Yes. CHANGE_PASSWORD calls two VMS routines (as well as performing lots of checks itself): EXE$LOOKUP_HASH to check whether the new password is in the history list, and EXE$LOOKUP_PASSWORD, to check whether the password is in the system dictionary. These are the only details the VMS group gave us conerning the filtering performed by $ SET PASSWORD. They did not provide us with a call to invoke the site-specific filter you refer to, and I must confess that not being familiar with this, we did not prompt them for the information. I think also there was a naive assumption that EXE$LOOKUP_PASSWORD would call any site-specific routines, as I believe it handles site-specific dictionary lookups. >> and if it is possible to use this routine from within ALL-IN-1? As you may have guessed from the above, the answer is no for ALL-IN-1 V3.0. Please SPR/SRF/whatever this problem. However, I cannot guarantee it will be fixed, as it relies on the goodwill of the VMS group in providing us with the necessary, but undocumented, information. Unfortunately, this is yet another example of a VMS operation for which there is no satisfactory interface available to ALL-IN-1 (or any other layered product), so we have to write our own. Although it is designed to copy $ SET PASSWORD exactly there will inevitably be slight differences, as much of $ SET PASSWORD is undocumented. Maybe someone should submit a VMS SPR asking for $ SET PASSWORD to be available as a system service. :-) Best regards and a Happy New Year, Scott

    Hi Julia,
    
    >> can anyone tell me how CHANGE_PASSWORD works
    
    Yes.  CHANGE_PASSWORD calls two VMS routines (as well as performing
    lots of checks itself): EXE$LOOKUP_HASH to check whether the new
    password is in the history list, and EXE$LOOKUP_PASSWORD, to check
    whether the password is in the system dictionary.
    
    These are the only details the VMS group gave us conerning the
    filtering performed by $ SET PASSWORD.  They did not provide us with a
    call to invoke the site-specific filter you refer to, and I must
    confess that not being familiar with this, we did not prompt them for
    the information.  I think also there was a naive assumption that
    EXE$LOOKUP_PASSWORD would call any site-specific routines, as I believe
    it handles site-specific dictionary lookups.
    
    >> and if it is possible to use this routine from within ALL-IN-1?
    
    As you may have guessed from the above, the answer is no for ALL-IN-1
    V3.0.  Please SPR/SRF/whatever this problem.  However, I cannot
    guarantee it will be fixed, as it relies on the goodwill of the VMS
    group in providing us with the necessary, but undocumented, information.
    
    Unfortunately, this is yet another example of a VMS operation for which
    there is no satisfactory interface available to ALL-IN-1 (or any other
    layered product), so we have to write our own.  Although it is designed
    to copy $ SET PASSWORD exactly there will inevitably be slight
    differences, as much of $ SET PASSWORD is undocumented.
    
    Maybe someone should submit a VMS SPR asking for $ SET PASSWORD to be
    available as a system service.  :-)
    
    Best regards and a Happy New Year,
    Scott