🚀 go-pugleaf

In article <452@marque.mu.edu> kcb@marque.UUCP (Kent Brodie) writes:
>one of the largest security "holes", as it were, is the fact that the
>default "welcome" message on VAX/VMS systems is just that-- it WELCOMES
>the user to the system.  In the case of an unauthorized access to your
>precious system, the existance of this message can cause ALL SORTS of
>legal headaches, depending on your state/local laws.
> [text and command file deleted]

Kent, thanks for letting those of who were unaware of this legal loophole
know of it's existance, and for writing and debugging a command file to
help us coa. I installed it on all 9 of my VAXen. Works like a champ!

One one comment. The f$getsyi("nodename") lexical function gets it's
information from the SCSNODE sysgen parameter. If this value is null
then no value appears for nodename in the unwelcome message. A workaround
for system managers who do not need/want to assign an SCSNODE value for their
system is to get the value from the system logical SYS$NODE.

Replace the lines

$ lineone = "      You are on node ''f$getsyi("NODENAME")' running " + -
  "VAX/VMS version ''f$edit(f$getsyi("VERSION"),"TRIM")'. " 

with the following lines

$ nodename = f$trnlnm("sys$node") - "_" - "::"
$ lineone = "      You are on node ''nodename' running " + -
  "VAX/VMS Version ''f$edit(f$getsyi("VERSION"),"TRIM")'. "

That fixes it up nicely.

Thanks again.



Zack Sessions                          | Utilizing the computing facilities
General Electric                       | at the University of North Carolina 
Nuclear Fuels & Component Manufacturing| at Wilmington 
Wilmington, NC                         |

"If it ain't broke, then don't fix it!"