HP3000-L Archives

July 1999, Week 2

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:
Joe Geiser <[log in to unmask]>
Reply To:
Joe Geiser <[log in to unmask]>
Date:
Thu, 8 Jul 1999 11:59:06 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (54 lines)
On Thursday, July 08, 1999 11:36, Mike Hornsby writes,

> For examples:
> a) Released files (BTW, releasing files is not a good idea, (any user can
> purge the file) but it is very common)

Very true, but any file in PUB.SYS should be executable by anyone --- the
security on this group and files in it should be left alone...

> b) User segments in the system SL (yes, this is still a frequent issue)

The sooner vendors learn to leave SL and XL alone, and use their own, the
sooner this issue will go away.  These are for HP's use, not anyone elses.

> c) Modification of network defaults in NET.SYS

Network defaults should be in files named with their appropriate names.
HP's examples/defaults end with "SAMP" - example:  RESLVCNF is the DNS
pointer file - RSLVSAMP is the sample of that file.  The defaults should be
in RESLVCNF and not in RSLVSAMP.

> d) CICAT changes for security purposes

This is a tough one because I agree that a lot of the messages in there are
too "hacker friendly".  Given that there are some updates to this file with
every release, I usually don't mess with this file - maybe others have an
answer to this one.

> e) Octcompted, or NM versions of programs like QUERY, FCOPY ...

NM Query is already out there -- it's called QUERYNM.PUB.SYS.  We rename
QUERY to QUERYCM, and QUERYNM to QUERY.  As for FCOPY - you'll either have
to "re-octcomp" it, or keep a copy of it stashed elsewhere, or restore it
from backup.  My vote is to re-octcomp it.

> Any others?

The only thing I can think of is that there are have been a defined set of
accounts, and now that the freeware is being released (SYSLOG, BIND, SAMBA,
etc.), these accounts are now finding their way onto FOS tapes.  This is
usually shown in the Communicator, but basically, why can't these utilities
be made part of the SYS account in separate groups as opposed to using new
accounts?  Just curious.

Regards,
Joe

====================================================
Joe Geiser, Managing Partner
BizNetTech.net LLC
Phone: +1(215) 945.8100   Fax: +1(215) 943.8408
Toll Free (US/Canada): (877) 945.8100
====================================================

ATOM RSS1 RSS2