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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

1678.0. "NODE4 BY USER , BY PASSWORD" by STKMCC::LUND () Sun Oct 20 1991 16:42

I have a customer who use the following method to secure the NML object.

$NCP SHOW OBJ NML CHAR

Object Volatile Characteristics as of 18-OCT-1991 13:59:00

Object = NML

Number                   = 19
File id                  = NML.EXE
User id                  = NML$SERVER
Password                 = ZAWTSALLCA

The NML$SERVER user exists but the password in UAF doesn't match the one on the
object. Instead they have created a new account NET$SERVER wich has to be 
specified at all NML acceses. With ncp this works fine.

$ NCP tell stkmcc"net$server skrivbord" sh exe

Node Volatile Summary as of 18-OCT-1991 14:04:52

Executor node = 50.111 (STKMCC)

State                    = on
Identification           = DECnet-VAX V5.4-1,  VMS V5.4-2
Active links             = 2
                

But the same command in MCC gives the following result.

MAN/ENT

DECmcc (V1.1.0)

MCC>  show node4 stkmcc all status , by user net$server, by password skrivbord
Node4 stkmcc
AT 18-OCT-1991 13:58:36 Status

Access control information invalid at Node


I have reproduced the problem on my node STKMCC (VMS 5.4-2) it is on easynet.
What is the problem here ??


Regards Niklas
T.RTitleUserPersonal
Name
DateLines
1678.1TOOK::PURRETTAFri Nov 22 1991 20:078
    Yes, you found a problem and we've fixed it for v1.2.

    What's happening is when you make a request, the NODE4 firsts asks
    the entity to show idents.  This is part of its cluster checking routine.
    After that checking has completed it will issue the request specified
    on the command line.  The cluster checking routine was not using the
    "by user, by password" access control data and was failing.