Raylene, (01)
That was just the information I was looking for! I'm now able to look
through the ioexec file. (02)
Thanks! (03)
Jonathan (04)
Raylene Pak wrote:
> Jonathan,
> Augment has its own private file protection seperate from the TOPS20
> file protection. The <>Set <>Protection command allows you to set the
> protection status for a file. The Augment protection status restricts
> file access based on user idents. The ident(s) of user(s) allowed to
> access a file are placed in a specially formatted string in the origin
> statement of that file. This is also applicable to journal documents
> via the restricted access email header field.
> The ioexec file contains the code that implements this Augment file
> protection. In the past, knowledgeable users were spoofing their idents
> to gain access to files that they weren't supposed to have access to.
> At one point in time, I changed the code to prevent this type of ident
> spoofing. To keep the rogue users from examining the new code to
> determine a means of circumventing it, I restricted the access to that
> file to Doug and myself. To access the ioexec file, log in as pak - the
> password for that should be the same as that for the operator. When you
> enter Augment, if you are prompted for an ident, use rdp.bi. If you run
> into any problems, let me know; I'm not entirely sure how I left my
> account on the released version of Augment. Once you are viewing the
> file, you probably want to add the prog.chm ident to the access list in
> the origin statement and do an Update New command. Then you should be
> able to access the file logging in as programmer.
> Raylene (05)
_________________________________________________________________
Message Archives: http://chm.cim3.net/forum/nls-technical/
Shared Files: http://chm.cim3.net/file/work/project/nls-restore/
Community Portal: http://www.computerhistory.org/
To Post: mailto:nls-technical@chm.cim3.net
Community Wiki: http://chm.cim3.net/cgi-bin/wiki.pl?NLS_Restoration (06)
|