pcmoore
commented
5 years ago We've treated similar issues as bugs haven't we? For example, look at the other issue you recently filed (#109) which considers a similar issue as a bug.
Closed rgbriggs closed 5 years ago
pcmoore
commented
5 years ago We've treated similar issues as bugs haven't we? For example, look at the other issue you recently filed (#109) which considers a similar issue as a bug.
rgbriggs
commented
5 years ago On 2019-03-12 06:48, Paul Moore wrote:
We've treated similar issues as bugs haven't we? For example, look at the other issue you recently filed (#109) which considers a similar issue as a bug.
Yes, that's a very reasonable argument.
-- Richard Guy Briggs rgb@redhat.com Sr. S/W Engineer, Kernel Security, Base Operating Systems Remote, Ottawa, Red Hat Canada IRC: rgb, SunRaycer Voice: +1.647.777.2635, Internal: (81) 32635
rgbriggs
commented
5 years ago rgbriggs
commented
5 years ago Staged in audit/next: 73e65b88feb9 audit: connect LOGIN record to its syscall record
rgbriggs
commented
5 years ago
Currently the AUDIT_LOGIN event is a standalone record that isn't connected to any other records that may be part of its syscall event. To avoid the confusion of generating two events, this record should be connected by using the audit_context() call rather than NULL.