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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

3307.0. "PASSWORD VERIFICATION PROBLEM: (cont'd)" by PEACHS::MITCHAM (Andy in Alpharetta (near Atlanta)) Wed Sep 05 1990 17:01

Scenario:

Created a TELNET window on a VT1000 and logged into a VAX 6420 via TCP/IP 
(UCX):

$ SET DISPLAY/CREATE/NODE=XTERM/TRANSPORT=TCPIP
$ SHOW DISPLAY:

    Device:    WSA15:  [super]
    Node:      XTERM
    Transport: TCPIP
    Server:    0
    Screen:    0

$ RUN/AUTHORIZE/DETACH/OUTPUT=WSA15: SYS$SYSTEM:DECW$SESSION

DECwindows session manager starts and appears to work normally.  Paused the 
session and tried entering the password from the pause screen.  Got the
following in a dialog box:   PASSWORD VERIFICATION PROBLEM:

If the session manager is SPAWN'd instead of run DETACH'd, I have no problem:

$ SPAWN/NOWAIT RUN SYS$SYSTEM:DECW$SESSION

I am unable to determine the reason for this behavior.  I located another note
in this conference (topic 1675.0) that discussed "Password Verification Problem"
but it is not applicable here.  My customer was given that info and it didn't
help (and I've been able to reproduce the problem here as well and I have
enough quotas).

Ideas?

-Andy
T.RTitleUserPersonal
Name		DateLines
3307.1Running the session manager remotely is unsupportedCSC32::M_MURRAYThu Sep 06 1990 13:118
Andy,

You could tell the customer that running the session manager
remotely is unsupported.

See the Interoperability Compliance Matrix SSA 01.25.00, page 3.

Mike
3307.2BTW, where might I find an online version of the v5.3-1 SSA?PEACHS::MITCHAMAndy in Alpharetta (near Atlanta)Thu Sep 06 1990 15:4013
> You could tell the customer that running the session manager
> remotely is unsupported.

Thanx for your response.  Yes, I understand it is unsupported and the customer
has been made aware of this.

Support issues aside, I am still puzzled why it works when spawn'd and not
when detach'd.  The session manager has privileges to read my UAF file but
it doesn't appear it's even getting that far.  In short, I'd appreciate any
assistance in determining what is preventing the password from being read
thus causing the error.

-Andy
3307.3maybe it needs DCL context...GSRC::WESTSCARY : A programmer with a screwdriver.Thu Sep 06 1990 19:2717
  I would have say that the session manager needs to run in the context
of DCL.

  Try this:

	$ run/detach/input=SM.COM/<any other params> sys$system:loginout.exe

  Where SM.COM is a com file that contains the following:

	$ set disp/crea/node=<node_of_choice>
	$ run sys$system:decw$session.exe
	$ set disp/dele


						-=> Jim <=-