HP3000-L Archives

April 1998, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Andreas Schmidt <[log in to unmask]>
Reply To:
Date:
Thu, 23 Apr 1998 10:40:22 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
STREAMX.DATA.VESOFT knows $CHLOGON-FORBID, e.g. $chlogon-forbid @.@       @[log in to unmask]@
@.@
and $LOGON-EXECUTE in SECURCON.DATA.VESOFT may be helpful as well.

Best regards, Andreas Schmidt, CSC, Germany





[log in to unmask] on 22/04/98 07:23:00 PM

Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Andreas Schmidt/HI/CSC)
Subject:  Re[2]: CHGROUP COMMAND.




I've never heard of disabling certain commands in VESOFT security (and I use to
work there).  You can restrict anything you want in the security menus, but
there is nothing in security/3000 that does anything with MPE commands in terms
of trapping, allowing or disallowing.
shawn

______________________________ Reply Separator _________________________________
Subject: Re: CHGROUP COMMAND.
Author:  [log in to unmask] at Internet-Mail
Date:    4/22/98 10:13 AM

I am surprised that no one mentioned VeSoft's facility for disallowing
certain commands.
You would also want to do something for chdir, as well.
While I like the UDC approach, except for what it does to HELP CHGROUP,
we password certain sensitive groups that the authorized user is home to
(so that they don't need to specify the password, thus granting that
user transparent access). As for the UDC, if you provide no commands for
unauthorized users, they get the prompt back. No message, no error, just
the prompt.

ATOM RSS1 RSS2