Using the Build Tool Server › Security Considerations

Security Considerations

The client performs a login check whenever a new remote node is requested. If the login fails, a dialog message displays the error. After login, requests can be sent to the server for splits, builds, and to review results. Requests are evaluated for ownership on the remote host and appropriate error messages that are displayed if a request cannot be processed.

The default security on the Build Tool server is none. If you want to secure commands or paths, create a file in the IEFH/bt directory called user.security. Records in this file must be in the following format:
Userid or * followed by at least one blank followed by the command or path to be secured.

The * indicates that all users have access to the path or command.

The path security matches the path to the security rule, allowing the creation of specific rules.

Examples

User1 /aaa/bbb/ccc/ddd
User2 /aaa/bbb/ccc/
User3 /aaa/bbb/ccc/eeee
* /aaa

These rules are implemented as follows:

• User1 can access all directories and files under /aaa/bbb/ccc/ddd.
• User2 can access all directories and files under /aaa/bbb/ccc.
• User3 can access all directories and files under /aaa/bbb/ccc/eeee, but not files under /ddd.
• * /aaa means that all users can access any directories or files under /aaa.

If User4 /bbb/ccc is a profile, User4 would not have access to /aaa

To implement shutdown command

Userid/* shutdown

To establish security for a path on Windows

Userid/* c:\aaa\bbb

To establish security for a path on UNIX, Linux, and NonStop

Userid/* /aaa/bbb