HP3000-L Archives

February 1995, Week 1

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:
Reply To:
Date:
Sat, 4 Feb 1995 16:59:10 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
   Well, I do agree that MPE systems are not infallible.  In my experiences,
I've had quite a time trying to keep certain security holes covered up from
potential hackers.  The Native Mode Debug routines are unfortunately much
more user friendly than the old Compat. Mode Debug of the MPE/V systems.
That is, the Debug on the MPE/iX systems seems to aid hackers with it's
built in user friendliness, whereas the Debug on MPE/V was not as easy to
use without reading the manual.
   I am a high school student who once headed the Computer Club of a high
school in Maryland.  As the head of the organization, I was occasionally
requested by teachers (who used the system for programming classes) to
go through the system and make sure that all areas were secured, so I found
potential hazards, which were corrected.  HP probably doesn't intend to
have it's MPE systems put in the hands of hackers, since some things which
should be better protected are not necessarily protected very well.
   A friend of mine wrote a huge security package for his HP 3000 Series 48;
it is completely infallible, using Turbo Image databases to store extra
info about users, and incorporating his own capabilities list, which checks
user priviliedges as the log in, and logging all of their actions.  I never
expected such a thing on a 16 bit 3000.
 
 
Daniel Kosack -=PROUD user of Linux 1.1.86=-
Former Student Account Supervisor for Eleanor Roosevelt High School
working with an HP-3000 Series 947 and Series 48

ATOM RSS1 RSS2