summaryrefslogtreecommitdiffstats
path: root/sys/security/mac/mac_syscalls.c
diff options
context:
space:
mode:
authorrwatson <rwatson@FreeBSD.org>2006-09-20 13:23:40 +0000
committerrwatson <rwatson@FreeBSD.org>2006-09-20 13:23:40 +0000
commit6061806b7a2441113ad29326d460afa8b87659b2 (patch)
treebe65104b59db262d96b574c4eb7dba409c97727f /sys/security/mac/mac_syscalls.c
parente63183ab3b572f0c8ce58cab5b0d21f00ca66d06 (diff)
downloadFreeBSD-src-6061806b7a2441113ad29326d460afa8b87659b2.zip
FreeBSD-src-6061806b7a2441113ad29326d460afa8b87659b2.tar.gz
Rather than allocating all buffer memory for the completed BSM record
when allocating the record in the first place, allocate the final buffer when closing the BSM record. At that point, more size information is available, so a sufficiently large buffer can be allocated. This allows the kernel to generate audit records in excess of MAXAUDITDATA bytes, but is consistent with Solaris's behavior. This only comes up when auditing command line arguments, in which case we presume the administrator really does want the data as they have specified the policy flag to gather them. Obtained from: TrustedBSD Project MFC after: 3 days
Diffstat (limited to 'sys/security/mac/mac_syscalls.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud