MU-VMS Archives

May 1997

MU-VMS@LISTSERV.MIAMIOH.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:
Randy Kaelber <[log in to unmask]>
Reply To:
Miami University OpenVMS <[log in to unmask]>
Date:
Mon, 5 May 1997 10:39:59 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Kent Covert ([log in to unmask]) wrote:
> In article <[log in to unmask]>, Michael Clarkson <clarksmr@
titan.sas.muohio.edu> writes:
> > David Munday <[log in to unmask]> wrote:
> > Another example of OpenVMS ""security through obscurity""?
 
> Obscure - yes.
> Secure - what does this have to do with security?
 
> I also think you'll hard pressed to find people referring to OpenVMS as
> security through obscurity.
 
A perception that carries through from the days of just plain 'ol VMS
(Remember when a VAX 11/780 was the ultimate?). I recall silly things DEC
did, like purposely create flawed instructions in the system manuals on
how to tell VMS that SYSUAF.DAT was corrupt. To get the proper
instructions, you had to contact DEC. That does little to improve
security, but it sure made system managers blow their tops.
 
Thankfully, DEC has largely grown up, now.
 
It seems well nigh impossible to hack an OpenVMS box without "social
engineering".
 
--
   Randy Kaelber:  [log in to unmask]  http://avian.dars.muohio.edu/~randy/
        DARS Programmer/Analyst, Miami University, Oxford, OH 45056 USA

ATOM RSS1 RSS2