lab06: different output

[stejoo]

I got different output on lab06 in the sealert part where one uses audit2allow:

[stefan@localhost lab06-sealert-and-audit-log]$ sudo ausearch -c 'testprog' --raw | audit2allow -M my-testprog
******************** IMPORTANT ***********************
To make this policy package active, execute:

semodule -i my-testprog.pp

[stefan@localhost lab06-sealert-and-audit-log]$ ll
total 20
-rw-r--r--. 1 stefan stefan 1243 Feb  5 10:49 my-testprog.pp
-rw-r--r--. 1 stefan stefan  377 Feb  5 10:49 my-testprog.te
-rw-r--r--. 1 stefan stefan 9542 Feb  5 09:35 README.md
[stefan@localhost lab06-sealert-and-audit-log]$ cat my-testprog.te

module my-testprog 1.0;

require {
	type testprog_t;
	type user_devpts_t;
	type testprog_exec_t;
	class chr_file { append read write };
	class file map;
}

#============= testprog_t ==============

#!!!! This avc can be allowed using the boolean 'domain_can_mmap_files'
allow testprog_t testprog_exec_t:file map;
allow testprog_t user_devpts_t:chr_file { append read write };

The require{ } and allow statements are quite different.
And I do not see the var_run_t type in the list either.

Did I go wrong somewhere?
I performed this on my own VM, which is a Rocky 9.5.
Had testprog running as a service and as background process at times.

[stejoo]

Not a big issue, because you do nothing with this result. But it feels weird to me as a trainee that it is different. One starts to doubt oneself. I will try it again later on a clean machine or the lab to see if I can reproduce this issue.