DataMuseum.dk

Presents historical artifacts from the history of:

Rational R1000/400 Tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about Rational R1000/400 Tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download
Index: ┃ T V

⟦232a98746⟧ TextFile

    Length: 2111 (0x83f)
    Types: TextFile
    Names: »V«

Derivation

└─⟦5f3412b64⟧ Bits:30000745 8mm tape, Rational 1000, ENVIRONMENT 12_6_5 TOOLS 
    └─ ⟦91c658230⟧ »DATA« 
        └─⟦458657fb6⟧ 
            └─⟦a5bbbb819⟧ 
                └─⟦this⟧ 
└─⟦d10a02448⟧ Bits:30000409 8mm tape, Rational 1000, ENVIRONMENT, D_12_7_3
    └─ ⟦fc9b38f02⟧ »DATA« 
        └─⟦9b46a407a⟧ 
            └─⟦eec0a994f⟧ 
                └─⟦this⟧ 

TextFile

procedure Set_Universe_Acls (Level               : Natural := 0; -- none
                             Implementation_Okay : Boolean := True;
                             Network_Read_Okay   : Boolean := True;
                             Network_Write_Okay  : Boolean := True;
                             Trace_Only          : Boolean := False;
                             Produce_Tables      : Boolean := False;
                             Tables_Output_File  : String  := "acl_tables");


-- Level = 0 => none   : anyone can do anything.
--       = 1 => Open   : anyone can do anything, but they may have to change
--                       acls to do it.
--       = 2 => Safe   : System and users are protected.  The operator must
--                       change acls to create new areas and allow others to
--                       things that users can do under level=1.
--       = 3 => Secure : Like safe, but more limited network access and less
--                       read access.

-- Set acls for the standard universe to be as described above.
-- Level 3 is about the most restrictive the system can be and still
-- run.  Level 3 will prevent most users other than Operator from
-- successfully executing operator commands even if they have operator
-- capability via write access to !Machine.Operator_Capability.

-- Implementation_Okay => access is given to !Implementation and
-- !Compiler_Interface.  Actually, !Compiler_Interface needs to be
-- readable anyway because it contains the switch file for the
-- standard universe.

-- Network_Read_Okay => Network_Public is granted read to most things, except
-- when Secure (level=3) is specified.

-- Network_Write_Okay is analogous to Network_Read but for Write access.

-- Be sure to update !machine.[user_acl_suffix,user_default_acl_siffix]
-- so that new users will get the acls you wish.
-- Don't forget about !machine.operator_capability, either.

-- Produce_Tables true causes previous parameters to be ignored, and a
-- file (specified by Tables_Output_File) to be written showing all
-- combinations of acls for documentation purposes.