The problem is due to the change from objects to applications.
There is not a predefined application called TASK (the default way of
using DECNET Objects by the OSU Server).
Applications must be defined each time the system is rebooted under
DECNET Plus. I have yet to figure out how to correctly create
the application using NCL. However the NCP emulator will correctly
create the application using the following command:
$ mcr ncp set object task number 0
Thanks again for everyone's help. This allows me not to bother with
going back to DECNET Phase IV which I understand will correct the
problem as well.
Rick Cadruvi
R&D Performance Group, Inc.
ri...@rdperf.com
> $ mcr ncp set object task number 0
%NCP-W-UNRCP, Unrecognized component , Object
--
-- "From:" line deliberatly munged to prevent harvesting by spambots.
-- Alan E. Frisbie Frisbie "@" Flying-Disk.Com
-- Flying Disk Systems, Inc. (Remove quotes before replying)
In article <336093DF...@RDPERF.COM>, RICK <RI...@RDPERF.COM> writes:
[snip]
|>Applications must be defined each time the system is rebooted under
|>DECNET Plus. I have yet to figure out how to correctly create
|>the application using NCL. However the NCP emulator will correctly
|>create the application using the following command:
|>
|> $ mcr ncp set object task number 0
I think I've missed a bit of the thread here but if all you want is
the application that the OSU HTTP Server requires, try this in NCL:
CREATE SESSION CONTROL APPLICATION WWWEXEC
SET SESSION CONTROL APPLICATION WWWEXEC -
IMAGE NAME "WWWEXEC.COM", USER NAME "whatever-the-username-is"
--
Antonio Carlini Mail: car...@marvin.enet.dec.com
DECnet-Plus for OpenVMS Engineering
Digital Equipment Corporation Worton Grange, Reading, England
(Reply-To: address mangled in header)
>Applications must be defined each time the system is rebooted under
>DECNET Plus. I have yet to figure out how to correctly create
>the application using NCL. However the NCP emulator will correctly
>create the application using the following command:
>
> $ mcr ncp set object task number 0
Just to complete the picture, in NCL-speak it'll be something like:
$ mc ncl create session control application <app_name>
$ mc ncl set session control application <app_name> addresses {name=<app_name>}
$ mc ncl set session control application <app_name> image name <full_image_name>
$ mc ncl set session control application <app_name> user name "<some_userid>"
Regards,
Steve Lock.
BT SM Project, UK.
I've no experience with NCL, but it looks like what this command would set up
is for any (DECNET) client requesting WWWEXEC will connect to said object
running under the specified username. This would be a security hole, you
should instead to set the application to get the username via incomming proxy
(or access control string) so that only the server account itself can start
wwwexec under its username.
David L. Jones | Phone: (614) 292-6929
Ohio State Unviversity | Internet:
2070 Neil Ave. Rm. 122 | jon...@kcgl1.eng.ohio-state.edu
Columbus, OH 43210 | vm...@osu.edu
Disclaimer: Dogs can't tell it's not bacon.
The supported way to modify the applications
database is to use the net$configure tool to
modify the NCL application startup script:
$ @sys$manager:net$configure advanced
Select Option 7 - Configure Application Database.
Net$configure will prompt you for the necessary
information. If you don't understand a question,
you can answer "?", for help. If you answer "yes"
to "Do you want to generate NCL scripts?", the
sys$manager:net$application_startup.ncl script
will be modified so that your session control
application will be created each time you reboot.
If you prefer not to wait until the first reboot
for your application to be created, you can
do this to manually execute the new script that
net$configure created:
$ mcr ncl @sys$manager:net$application_startup
Just be prepared to ignore the "process failure"
errors that will result because many of the
applications will already exist.
For further information, please refer to the
DECnet-Plus for OpenVMS Applications Installation
and Advanced Configuration manual.
- LindaLeigh Aberdale
DECnet-Plus Engineering
> Applications must be defined each time the system is rebooted under
> DECNET Plus. I have yet to figure out how to correctly create
> the application using NCL. However the NCP emulator will correctly
> create the application using the following command:
>
If its the same for DECNET Plus as for OSI then the NCL> CREATE SESSION
CONTRAL APPLICATION ...
and NCL> SET SESSION CONTROL APPLICATION ... stuff needs to go into
SYS$STARTUP:NET$APPLICATION_STARTUP.NCL
in order to be executed at each system boot.
> $ mcr ncp set object task number 0
>
In article <5k1s5o$fsm$1...@charm.magnus.acs.ohio-state.edu>, JON...@er6.eng.ohio-state.edu (David Jones) writes:
|>In message <5k1gl7$n6e$1...@nntpd.lkg.dec.com>,
|> car...@krakar.enet.dec.com (Antonio Carlini) writes:
|>>I think I've missed a bit of the thread here but if all you want is
|>>the application that the OSU HTTP Server requires, try this in NCL:
|>>
|>>
|>>CREATE SESSION CONTROL APPLICATION WWWEXEC
|>>SET SESSION CONTROL APPLICATION WWWEXEC -
|>> IMAGE NAME "WWWEXEC.COM", USER NAME "whatever-the-username-is"
|>
|>I've no experience with NCL, but it looks like what this command would set up
|>is for any (DECNET) client requesting WWWEXEC will connect to said object
|>running under the specified username. This would be a security hole, you
|>should instead to set the application to get the username via incomming proxy
|>(or access control string) so that only the server account itself can start
|>wwwexec under its username.
|>
|>
Joe Random User won't be able to get past Session Control unless they happen
to have a proxy for "whatever-the-username-is".