home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!cs.utexas.edu!ut-emx!slcs.slb.com!BRYDON@linus.slcs.slb.com
- From: brydon@asl.slb.com (Harvey Brydon (713)274-8281)
- Newsgroups: comp.os.vms
- Subject: Re: Am I in SYLOGIN?
- Message-ID: <1992Jul23.132025.14097@slcs.slb.com>
- Date: 23 Jul 92 13:20:25 GMT
- References: <1992Jul22.113259.1@utxvms.cc.utexas.edu>
- Sender: news@slcs.slb.com (News Administrator)
- Reply-To: brydon@asl.slb.com
- Organization: Schlumberger/Anadrill Sugar Land, TX
- Lines: 25
- Nntp-Posting-Host: 129.87.14.202
-
- In article <1992Jul22.113259.1@utxvms.cc.utexas.edu>,
- ccdk001@utxvms.cc.utexas.edu writes:
- >Anyone know of a simple, fairly fullproof way to determine if an image
- >is being run from SYLOGIN.COM or some other known place (step) during
- >process creation?
- >
- >I have an installed privileged application that I want executed during the
- >login process, but I don't want users to be able to execute it directly.
- >It does "things" based on an assumed state of that process/environment at
- >that time particular time. Allowing users to change their environment
- >(logical names, devices, etc.) and then rerunning this image could be
- >a problem in some instances.
-
- If you check whether it is running from SYLOGIN.COM or not may be an
- inferior test for this type of program. What if somebody does:
-
- $ @sys$sylogin
-
- after they log in? Since it is installed and privileged, I would suggest
- you do something privileged such as create an identifier and check for the
- presence of the identifier as a 'never previously executed' check.
- ____________________________________________________________________________
- Harvey Brydon | Internet: brydon@dsn.SINet.slb.com
- Dowell Schlumberger | P.O.T.S.: (918)250-4312
- "If you don't become current, you can't be deleted"
-