Ft_access_control

struct Ft_access_control {
       struct Ft_access_control_element   *insert_ace;
       struct Ft_access_control_element   *delete_ace;
};

Ft_access_control Is Input To These Functions

Ft_access_control Is Output From These Functions

ft_cattributes()

ft_create()

ft_fcattributes()

ft_fopen()

None

Use Ft_access_control to add users to and delete users from the access list (Ft_access_control_elements) for a particular file. Both insert_ace and delete_ace are linked lists of Ft_access_control_element structures ( ). This structure specifies user access privileges for the file.

If insert_ace is NULL when creating a file (ft_create() and ft_fopen()), anyone can access the file.
If you use both insert_ace and delete_ace, HP-UX responders process delete_ace first.

Figure 3-7 Ft_access_control Structure

Ft_access_control_element

struct Ft_access_control_element {
      struct Ft_access_control_element  *next;
      Ft_file_actions                    action_list;
      Uint32                             conc_access;
      Ft_initiator_identity              identity;
      struct Ft_file_passwords           *access_passwords;
      Ae                                 *location;
};

Ft_access_control_element defines not only who can access a file, but also how they can access it. HP-UX initiators and responders use only the identity and action_list fields. You can set values in the other fields if another FTAM implementation uses them.

When interacting with an HP-UX FTAM responder, you can use at most three (3) access control elements, one each for user, group, and other. Other responders may have different requirements.

*next

Points to the next Ft_access_control_element structure in the linked list. For HP-UX FTAM responders, the maximum number in the linked list is three per file.

action_list

Specifies the allowable actions the designated users can perform on a file. An action is present if the corresponding bit is set (ON).

Change Attribute
Delete File
Erase
Extend
Insert
Read
Read Attribute
Replace

For ft_select() and ft_fopen(), the requested_access parameter must be a subset of the values stored in action_list.

For ft_open(), the processing_mode parameter must be a subset of the values stored in action_list.

The action_list is of type Ft_file_actions. Refer to the "Ft_file_actions" section for detailed information.

conc_access

The HP-UX implementation of FTAM ignores this value. You can set the bits in conc_access, but HP-UX initiators and responders will not use it. Other FTAM implementations might. If you are unsure of your situation, see the documentation for the other FTAM implementation.

Bits in conc_access correspond to the allowable actions listed in the action_list. Here are the allowed locks, in order, from least to most restrictive:

File Action Lock File Owner Can Others Can
Set by conc_access Perform the Action Perform the Action

Not Required No Yes
Shared Yes Yes Exclusive Yes No
No Access No No

Use the following defined constants to set any combination of conc_access bits for file actions. Again, note that these locks are ignored by HP-UX initiators and responders.

FT_AC_READ_NOTREQ    FT_AC_REPLACE_NOACC       FT_AC_READ_ATTRIB_EXCL
FT_AC_READ_SHARED    FT_AC_EXTEND_NOTREQ       FT_AC_READ_ATTRIB_NOACC
FT_AC_READ_EXCL      FT_AC_EXTEND_SHARED       FT_AC_CHANGE_ATTRIB_NOTREQ
FT_AC_READ_NOACC     FT_AC_EXTEND_EXCL         FT_AC_CHANGE_ATTRIB_SHARED
FT_AC_INSERT_NOTREQ  FT_AC_EXTEND_NOACC        FT_AC_CHANGE_ATTRIB_EXCL
FT_AC_INSERT_SHARED  FT_AC_ERASE_NOTREQ        FT_AC_CHANGE_ATTRIB_NOACC
FT_AC_INSERT_EXCL    FT_AC_ERASE_SHARED        FT_AC_DELETE_FILE_NOTREQ
FT_AC_INSERT_NOACC   FT_AC_ERASE_EXCL          FT_AC_DELETE_FILE_SHARED
FT_AC_REPLACE_NOTREQ FT_AC_ERASE_NOACC         FT_AC_DELETE_FILE_EXCL
FT_AC_REPLACE_SHARED FT_AC_READ_ATTRIB_NOTREQ  FT_AC_DELETE_FILE_NOACC
FT_AC_REPLACE_EXCL     FT_AC_READ_ATTRIB_SHARED

identity

Specifies the user to whom the access privileges pertain (the "owner" in the previous table). For HP-UX initiators and responders, identity must have one of the following values: user, group, or other.

The identity is of type struct Ft_initiator_identity. Refer to the "Ft_initiator_identity" section for detailed information.

*access_passwords

Specifies a user password for each element listed in the action_list. HP-UX initiators and responders do not use this information; access_passwords is only used with other FTAM implementations.

Points to the Ft_file_passwords structure. Refer to the "Ft_file_passwords" section for detailed information.

*location

A pointer of type Ae. HP-UX initiators and responders do not use this information; location is only used with other FTAM implementations.

Ft_access_control

Technical documentation

» Table of Contents

» Glossary

» Index

Ft_access_control_element