home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!bradford.ac.uk!R.M.Hepworth
- From: R.M.Hepworth@bradford.ac.uk (RM HEPWORTH)
- Newsgroups: comp.os.ms-windows.apps
- Subject: Making Progman Secure
- Message-ID: <1992Aug20.080805.7335@bradford.ac.uk>
- Date: 20 Aug 92 08:08:05 GMT
- Organization: University of Bradford, UK
- Lines: 37
- Originator: 91609717@muser
- Nntp-Posting-Host: muser
-
- First of all I apologise to the bloke who actually brought up the
- subject of secure shells in the first place - I emailed you and then
- lost your address so I have had to find the time to post this instead.
-
- Anyway, on with the show. It is not necessary in Windows 3.1 to trwal
- around for a secure shell. Progman can be fortified very easily by
- simply making an addition to progman.ini.
-
- To make your copy of progman free of dangerous edges simply add a
- section in progman.ini headed [Restrictions].
- The following security features are available:
-
- NoRun=<number> -value 1 prevents use of File-Run command
- NoClose=<number> -value 1 prevents exiting Windows from the Program
- Manager
- NoSaveSettings=<number> -value 1 prevents use of Options-Save Settings
- NoFileMenu=<number> -value 1 removes File Menu completely
- Edit Level=<number>
-
- The following numbers are available for EditLevel:
- 1 prevents creation, deletion and renaming groups.
- 2 as 1 but also restricts the creation, deletion and renaming of program
- items
- 3 as 2 but also stops the user from changing the command line for a
- program item
- 4 prevents the user changing any program item information
-
- Any features you don't want, simply set to 0 or don't enter in the ini
- file.
-
- Hope this is of use to someone.
-
- Gratitudes to Mike Hardaker, contibutor to PCW and Windows USer, whose
- booklet I gleaned this from.
-
- RiK
-