Security Enhancement for EDITOR A.08.00 [ COMMUNICATOR 3000 MPE/iX Release 5.0 (Core Software Release X.50.20) ] MPE/iX Communicators
COMMUNICATOR 3000 MPE/iX Release 5.0 (Core Software Release X.50.20)
Security Enhancement for EDITOR A.08.00
by Robert Holdsworth
Software Technology Division
Overview
EDITOR A.08.00 has been enhanced with a long-requested security feature;
the optional ability to pass on security attributes of the TEXT file to
the KEEP file. This is implemented through a new global option on the
SET command. The syntax is:
/SET SECURE Activates KEEP file security
/VERIFY SECURE Display status of KEEP file security
as shown below
SECURE = TRUE (I.E. NOSECURE = FALSE) Indicates security is active
/SET NOSECURE Deactivates KEEP file security
/VERIFY SECURE Display status of KEEP file security
as shown below
NOSECURE = TRUE (I.E. SECURE = FALSE) Indicates security is not active
Note that when SECURE is FALSE, the KEEP command behaves as it always
has, creating a file with standard EDITOR new file default security. The
default setting for SECURE upon first entering EDITOR is FALSE, thereby
preserving EDITOR's original behavior. However, some users may wish to
enter EDITOR with the initial value of SECURE set TRUE. Two methods are
available for doing so: EDITOR can be run with PARM=1 or the JCW
EDITORSETSECURE can be set to 1. Examples are shown below:
:RUN EDITOR.PUB.SYS;PARM=1 Initial value of SECURE is TRUE
:SETJCW EDITORSETSECURE=1
:EDITOR Initial value of SECURE is TRUE
:DELETEVAR EDITORSETSECURE
:EDITOR Initial value of SECURE is FALSE
Regardless of the chosen initial value, once within EDITOR you can
control the setting of SECURE with SET as shown above.
Details of Operation
Passing of security attributes from the TEXT file to the KEEP file occurs
only when the following conditions apply:
* SECURE is TRUE. This must be done prior to the first KEEP command
for which security is desired, and is described in detail above.
* The most recently TEXTed file is a permanent disk file.
* The KEEP file is a permanent disk file.
Note that when the above three conditions apply, KEEP applies TEXT file
security in all of the following cases:
* When the KEEP file is a new permanent disk file.
* When the KEEP file is an existing permanent disk file that is not
the TEXT file.
* When the KEEP file is the TEXT file. This allows preservation of
existing security when modifying and KEEPing an existing permanent
disk file.
The value of the SECURE option, TRUE or FALSE, remains in effect through
the editing session until modified with SET or until EDITOR is exited and
re-entered.
NOTE EDITOR does not apply security to EDITOR work files ("K" files)
that are created while SECURE is TRUE, and does not apply security
to workfiles that are renamed as a result of the KEEPQ command.
File Security Attributes
The file security attributes that are mapped from the TEXT file to the
KEEP file when SECURE is TRUE are:
* Security matrix
* LOCKWORD
* SECURE/RELEASE status of file
* Access Control Definitions
Example
The following LISTFs show SECURFIL with a lockword, non-default security
matrix, released, and with an ACD in effect. EDITOR is run, and the SET
SECURE command is entered. File SECURFIL is TEXTed and a KEEP is done to
NEWFILE. The final LISTFs show correct transfer of lockword, security
matrix, released status, and ACD.
:LISTF SECURFIL,-3
********************
FILE: SECURFIL.TEST.EDIT
FILE CODE : 0 FOPTIONS: STD,ASCII,FIXED
BLK FACTOR: 3 CREATOR : BOB
REC SIZE: 72(BYTES) LOCKWORD: LOCK
BLK SIZE: 108(WORDS) SECURITY--READ : ANY,AC,GU
EXT SIZE: 2(SECT) WRITE : ANY,AC,GU
NUM REC: 1 APPEND : ANY,AC,GU
NUM SEC: 2 LOCK : ANY,AC,GU
NUM EXT: 1 EXECUTE : ANY,AC,GU
MAX REC: 1 **SECURITY IS OFF
MAX EXT: 1 COLD LOAD ID: %37540
NUM LABELS: 0 CREATED : WED, 20 JAN 1993
MAX LABELS: 0 MODIFIED: WED, 20 JAN 1993 11:46 AM
DISC DEV #: 1 ACCESSED: FRI, 5 FEB 1993
DISC TYPE : 4 LABEL ADDR: %405654
DISC SUBTYPE: 2 SEC OFFSET: %1
CLASS: DISC FLAGS: NO ACCESSORS
FCB VECTOR: %0 %0
EXT MAP: %100405654
:LISTF SECURFIL,-2
ACCOUNT= EDIT GROUP= TEST
FILENAME ------------ACD ENTRIES--------------
SECURFIL BOB.EDIT : R,W,X,A,L
@.SYS : R,W,X,A,L
:EDITOR
HP32201A.08.00 EDIT/3000 FRI, FEB 5, 1993, 1:52 PM
(C) HEWLETT-PACKARD CO. 1993
/T SECURFIL
FILE UNNUMBERED
/SET SECURE
/K NEWFILE,UNN
/EXIT
END OF SUBSYSTEM
:LISTF NEWFILE,-3
********************
FILE: NEWFILE.TEST.EDIT
FILE CODE : 0 FOPTIONS: STD,ASCII,FIXED
BLK FACTOR: 3 CREATOR : BOB
REC SIZE: 72(BYTES) LOCKWORD: LOCK
BLK SIZE: 108(WORDS) SECURITY--READ : ANY,AC,GU
EXT SIZE: 2(SECT) WRITE : ANY,AC,GU
NUM REC: 1 APPEND : ANY,AC,GU
NUM SEC: 2 LOCK : ANY,AC,GU
NUM EXT: 1 EXECUTE : ANY,AC,GU
MAX REC: 1 **SECURITY IS OFF
MAX EXT: 1 COLD LOAD ID: %37540
NUM LABELS: 0 CREATED : FRI, 5 FEB 1993
MAX LABELS: 0 MODIFIED: FRI, 5 FEB 1993 1:53 PM
DISC DEV #: 1 ACCESSED: FRI, 5 FEB 1993
DISC TYPE : 4 LABEL ADDR: %1410224
DISC SUBTYPE: 2 SEC OFFSET: %1
CLASS: DISC FLAGS: NO ACCESSORS
FCB VECTOR: %0 %0
EXT MAP: %101410224
:LISTF NEWFILE,-2
ACCOUNT= EDIT GROUP= TEST
FILENAME ------------ACD ENTRIES--------------
NEWFILE BOB.EDIT : R,W,X,A,L
@.SYS : R,W,X,A,L
Error Conditions
The following new warning messages may occur when SECURE is TRUE. The
messages indicate that something went wrong in trying to obtain TEXT file
security attributes or in applying these attributes to the KEEP file or
both. When any of the following messages occur, you should check the
security disposition of the KEEP file at the end of the editing session
and if necessary use appropriate MPE commands to apply the desired
security.
*** WARNING *** CAN'T APPLY TEXTFILE SECURITY TO KEEPFILE
This message can occur prior to closing the KEEP file and indicates a
failure during transfer of security information from the TEXT file. More
detail will be provided from the following possible messages:
* TEXTFILE FOPEN FAILURE
The TEXT file could not be opened. This error could occur if the TEXT
file were purged prior to the KEEP command.
* TEXTFILE TO KEEPFILE HPACDPUT FAILURE
The HPACDPUT intrinsic failed when EDITOR attempted to map the ACD from
the TEXT file to the KEEP file. Note that read access to the TEXT file
is not adequate to retrieve ACD information, you must also have read
access to the TEXT file ACD (be the file creator, account manager, system
manager, or be granted explicit RACD access in the ACD).
* DUMMY FOPEN FAILURE
Indicates failure to open a temporary work file for ACD transfer.
* TEXTFILE TO DUMMY HPACDPUT FAILURE
Indicates failure to transfer ACD information to the temporary work file.
* DUMMY TO KEEPFILE HPACDPUT FAILURE
Indicates failure to transfer ACD information from the temporary work
file.
* FLABELINFO FAILURE
The FLABELINFO intrinsic failed when called to obtain the TEXT file
security matrix and secure bit setting.
If the KEEP file is successfully closed and SET SECURE is in effect,
EDITOR may attempt to perform ALTSEC, RENAME, and RELEASE commands if
required. The failure of any of these will result in one of the
following warning messages:
* ALTSEC FAILURE ON CLOSED KEEPFILE
* RENAME FAILURE ON CLOSED KEEPFILE
* RELEASE FAILURE ON CLOSED KEEPFILE
MPE/iX Communicators