Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ub!acsu.buffalo.edu
From: kalisiak@acsu.buffalo.edu (christophe m kalisiak)
Newsgroups: comp.sys.dec.micro
Subject: Re: P/OS security? (or how to break into a P/OS system)
Message-ID: <72945@eerie.acsu.Buffalo.EDU>
Date: 25 Apr 91 03:15:29 GMT
References: <1991Apr16.134937.47433@cc.usu.edu> <71506@eerie.acsu.Buffalo.EDU> <1991Apr22.154959.47516@cc.usu.edu>
Sender: news@acsu.Buffalo.EDU
Distribution: na
Organization: SUNY Buffalo
Lines: 35
Nntp-Posting-Host: lictor.acsu.buffalo.edu

In article <1991Apr22.154959.47516@cc.usu.edu> slsw2@cc.usu.edu writes:
>In article <71506@eerie.acsu.Buffalo.EDU>, kalisiak@acsu.buffalo.edu (christophe m kalisiak) writes:
>> In article <1991Apr16.134937.47433@cc.usu.edu> slsw2@cc.usu.edu writes:
>>>In article <41275@cup.portal.com>, Azog-Thoth@cup.portal.com (William Thomas Daugustine) writes:
[...]
deleted
>It was just PIP TO:=filename. Since the file was not encrypted, the passwords
>showed up.

This only works on versions of RSX in which the password file is not 
encrypted. I think they started encription at V3.0 of 11M/PLUS. 

>BTW, deleting the password file is probably not a good idea. If you do it on
>VMS, you just plain can't get in unless you do a conversational bootstrap and
>set the startup file to OPA0:...

I have never really had to worry about system protections... If I had 
to do it I would just hit ^c while the STARTUP.CMD file was executing
then type ABO AT.T0 to kill the IND.

>>>Since P/OS is related to RSX-11M, it might work. Wish I could remember the
>>>name of the account file, though...
>> 
>> [0,0]RSX11.SYS
>
>I dunno; sounds like the system image to me. I'd want to poke about the
>documentation for a while before I deleted that one.

I know for a fact that RSX11.SYS is the password file. I don't know 
what you would do with it though.


Chris Kalisiak
kalisiak@acsu.buffalo.edu
V076N3W7@ubvms.cc.buffalo.edu