## 08/09/02 gww ##
Don't preselect for the "as" audit class
or remap
295:AUE_PF_POLICY_ADDRULE:Add IPsec policy rule:as
296:AUE_PF_POLICY_DELRULE:Delete IPsec policy rule:as
297:AUE_PF_POLICY_CLONE:Clone IPsec policy:as
298:AUE_PF_POLICY_FLIP:Flip IPsec policy:as
299:AUE_PF_POLICY_FLUSH:Flush IPsec policy rules:as
300:AUE_PF_POLICY_ALGS:Update IPsec algorithms:as
to something not preselected.
Gary..
If you look at my attached files, you will see that I had selected:
flags: lo,ad,ex
in audit_control, and:
root:lo:no
in audit_user. That's it. So, in terms of workarounds, do you need to be sure the administrative meta-classes are also
not selected (ad and perhaps am)? Is this accurate or will remapping the events currently in "as" to something else cause
them to get automagically excluded by "ad"?
A simple workaround is this:
echo "{raddr 1.1.1.1 dir both} bypass {}" > /etc/inet/ipsecinit.conf
reboot
Now you have policy on boot.
Alternatively, before using punchin or running ipsecconf -f, run this:
echo "{raddr 1.1.1.1 dir both} bypass {}" | ipsecconf -a -
which will load a policy.
## 08/09/03 gww ##
Yes I looked at the attached files. That's why I asked for them.
"ad" is a meta class that includes "as", feel free to choose
the individual classes except for "as".
VIZ.ss,ua,aa
OR the alternative is to remap for example to "no"
VIZ.
295:AUE_PF_POLICY_ADDRULE:Add IPsec policy rule:no
296:AUE_PF_POLICY_DELRULE:Delete IPsec policy rule:no
297:AUE_PF_POLICY_CLONE:Clone IPsec policy:no
298:AUE_PF_POLICY_FLIP:Flip IPsec policy:no
299:AUE_PF_POLICY_FLUSH:Flush IPsec policy rules:no
300:AUE_PF_POLICY_ALGS:Update IPsec algorithms:no
And then reload the kernel event to class mappings.
VIZ.
sync;sync;reboot
Gary..
Gary, the workaround I posted before your update (having an ipsec policy that does nothing) is actually much better because it retains the auditing of the as class.