Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!ucla-cs!zen!ucbvax!HWALHW50.BITNET!DEGROOT From: DEGROOT@HWALHW50.BITNET.UUCP Newsgroups: comp.os.vms Subject: Checking LOGINOUT.EXE for hackers-patches. Message-ID: <8708181201.AA23869@ucbvax.Berkeley.EDU> Date: Tue, 18-Aug-87 06:49:00 EDT Article-I.D.: ucbvax.8708181201.AA23869 Posted: Tue Aug 18 06:49:00 1987 Date-Received: Thu, 20-Aug-87 01:30:36 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 39 Checking LOGINOUT.EXE for hackers-patches ----------------------------------------- On the VMS 4.4 distribution tape I located LOGINOUT.EXE in the saveset REQUIRED. On the VMS 4.5 distribution tape I found LOGINOUT.VUP in the saveset VMS045.B. I copied the files to an empty work directory and tried to patch my private copy of LOGINOUT.EXE. Well, that didn't work at all. Using the command $ PATCH LOGINOUT.VUP resulted in the message: %PATCH-F-BADIDENT, unable to patch image with ident of R4 Question number one: Obviously I gave the wrong command or some editing in LOGINOUT.VUP is necessary? Ok, suppose I succeeded at last and I have a brand-new fresh unhacked LOGINOUT.EXE. Question number two: Is there a good way to compare this file with our suspected cluster-wide LOGINOUT.EXE? Perhaps the command DIFFERENCE/MODE=HEXADECIMAL or is there a better way? Tel. +31-8370- .KeesdeGroot (DEGROOT@HWALHW50.BITNET) o\/o THERE AINT NO (8)3557/ Wageningen Agricultural University [] SUCH THING AS 4030 Computer-centre, the Netherlands .==. A FREE LUNCH! DISCLAIMER: My opinions are my own alone and do not represent any official position of my employer. - if you go too far to the east, you find yourself in the west .. -