Bay Networks 6300 Supplement Manual page 265

Book A Chapter 15 Using RA 6300 Security
For the acp_regime and acp_restrict files, the entry looks like this:
username=chris;time="9:00am – 10:30pm Monday-Friday";annex=annex03
For the acp_userinfo file, the entry looks like this:
user username=chris;time="9:00am–10:30pm Monday-
Friday";annex=annex03
A profile criteria specification cannot exceed 80 characters.
After the profile criteria specification, you specify the security measure(s)
to be applied if the criteria are met. The following is an example from the
acp_userinfo file:
user username=chris;time="9:00am-10:30pm Monday-Friday";annex=annex03
climask ppp end
end
When user chris connects to annex03, erpcd records all the conditions
related to the connection – the userid and any group associations (as
defined in the acp_group or /etc/group file), the RA 6300 and port that
chris connects to, the time of connection, and the connection
protocol – CLI, PPP, or SLIP. erpcd saves these connection conditions
for comparison with profile criteria specifications in the acp_regime,
acp_userinfo, and acp_restrict files.
All of the profile criteria in a specification must be met in order for erpcd
to consider that the specification matches the connection conditions
recorded. The specification for Chris is considered a match if he gives a
user name of chris and connects to annex03 between
9:00 A.M. and 10:30 P.M Monday through Friday. If all of these criteria
are met, user chris is prevented (via the climask entry) from issuing the
ppp command while he is logged into annex03.
Note that, in the example cited, the profile criteria specification replaces
the username field in acp_userinfo. The user field can be specified
instead, for compatibility with earlier RA 6300 releases. For more
information, see Creating the acp_userinfo File on page 15-249.
Remote Annex 6300 Supplement to the Remote Annex Administrator's Guide for UNIX
A-237