Path: utzoo!attcan!uunet!bcstec!evtprp0b!root From: root@evtprp0b.UUCP (Eric T. Smith) Newsgroups: comp.sys.apollo Subject: Re: Registry problems AGAIN Keywords: registry security Message-ID: <221@evtprp0b.UUCP> Date: 29 Oct 90 17:22:35 GMT References: <302@camdev.comm.mot.com?> Organization: Boeing Computer Services Everett Propulsion, Everett WA Lines: 41 In article <9010250649.AA01789@vlsi-mentor.jpl.nasa.gov> you write: >What is this? I am logged in as 'root' and edrgy tells me I am >"not authorized to perform operation"? > >According to the properties, my SID *owns* the registry and the >files the registry is based on. What gives? > If you are running the cvtrgy program to convert from SR9 to SR10 and the SR9 registry is writable this is your problem: 1) The SR10 registry has some internal verification code it uses to denote the "owner" of the registry. You set this with the -owner option of the cvtrgy program. 2) Every time you run the cvtrgy program this internal number is changed, even though the "owner" is the same person, group, org. 3) If you log in as root and then run cvtrgy you are the root user with the old verification code, not the new one, and will get the error message if you try to change things with rgy_admin. 4) The cure is to log in again, or crp on without the -me, or run login in a window. This makes you the root with the new verification key and works fine... If you're not running cvtrgy from 9 to 10 you may have a problem with the key resulting from SR10.1, if you had/have nodes at 10.1 you might want to call Apollo/HP and talk to them about it. -- |----------------------------------------------------------------| |Eric Smith (206) 342-9681 (wk) | |Boeing Computer Services ....uunet!bcstec!evtprp0b!root | |M/S 03-87, P.O. Box 24346, Seattle, WA 98124-0346 | |----------------------------------------------------------------| |The answer is 42... | | --but-- | | What was the question? | |----------------------------------------------------------------| | Needless to say my opinions are MINE, not Boeings... | |----------------------------------------------------------------|