On Wed, 4 Sep 2019, Andrew Cagney wrote:
Look in nic.console.verbose.txt
type=SYSCALL msg=audit(1567646808.958:61): arch=c000003e syscall=165
success=yes exit=0 a0=0 a1=55cef7279d60 a2=0 a3=1031 items=1 ppid=1 pid=486
auid=429496729
5 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none)
Should it not only trigger for the console.txt's? instead of looking at
the verbose console.txt's? If it did that, we could add a sanitizer to
strip out: tty=(none)
I'm not sure what to do with them. Same with the KERNEL barfs we're triggering.
On Wed, 4 Sep 2019 at 23:48, D. Hugh Redelmeier <[email protected]> wrote:
A number of tests seem to be failing for a reason I don't understand.
testing/pluto/ikev1-algo-esp-null-01 failed nic:%NULL
testing/pluto/ikev1-hostpair-01 failed east:output-different nic:%NULL
road:output-different
testing/pluto/ikev1-hostpair-02 failed nic:%NULL
testing/pluto/ikev2-hostpair-02 failed nic:%NULL
testing/pluto/ikev2-hostpair-03-initial-contact failed nic:%NULL
testing/pluto/newoe-18-cop-cop failed nic:%NULL
testing/pluto/newoe-18-cop-clear failed nic:%NULL
testing/pluto/newoe-18-private-poc failed nic:%NULL
testing/pluto/newoe-18-private-private failed nic:%NULL
testing/pluto/newoe-18-private-clear failed nic:%NULL
We could also excempt nic from the null check. Since it never runs
libreswan.
Paul
_______________________________________________
Swan-dev mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan-dev
