Article View: alt.folklore.computers
Article #292Re: Primos Rel 18/20 Security Hole
From: schw... Scott Schwartz
Date: Mon, 18 Dec 1989 03:40
Date: Mon, 18 Dec 1989 03:40
15 lines
1368 bytes
1368 bytes
The big problem with old versions of Primos (or pr1mos, as the manuals said) was that lots of programs relied on embedded passwords in executables to access protected directories. Editing, much less disassembling, a binary would give lots of programs away. Then when rev 20 came out (I think it was 20... maybe 19) with user accessible dynamic libraries, whole new worlds of hacking opened up. By searching for the DYNT entries in the binary and replacing them with your own you could wreak havoc. One systems programmer I knew (Hi Franz!) went to incredible lengths to hide the names of the DYNTs... even to the extent of building call frames by hand and then branching to them (shudder). -- Scott Schwartz <schw...@shire.cs.psu.edu> "More mips; cheaper mips; never too many." -- John Mashey
Technical Details
Message-ID:
<1989Dec18.034037.17203@psuvax1.cs.psu.edu>Path:
mbox-mo1.pugleaf.net!gmdzi!unido!mcsun!uunet!wuarchive!psuvax1!schwartzReferences:
<8456@ttidca.TTI.COM> <1989Dec17.190122.5909@sun.soe.clarkson.edu>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!gmdzi!unido!mcsun!uunet!wuarchive!psuvax1!schwartz From: schw...@psuvax1.cs.psu.edu (Scott Schwartz) Newsgroups: alt.folklore.computers Subject: Re: Primos Rel 18/20 Security Hole Message-ID: <1989Dec18.034037.17203@psuvax1.cs.psu.edu> Date: 18 Dec 89 03:40:37 GMT References: <8456@ttidca.TTI.COM> <1989Dec17.190122.5909@sun.soe.clarkson.edu> Organization: Penn State University Computer Science Lines: 15 Posted: Mon Dec 18 04:40:37 1989 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit