Juan Antonio Osorio

> I believe this should be already feasible without changing libsemanage. Given that it usually runs in its own image, the image could be built with modified `semanage.conf`. this is...

@bachradsusi seems to me that the tests themselves is broken which is an issue unrelated to this PR 😕 this is happening also for simple dependency upgrades

> Note: version.go could print quite a few more information if we switched to go 1.18... why don't we?

@jhrozek what about instead changing to a purely GH-action based release model? I've been experimenting with this a bit and it's quite clean and simple https://github.com/metal-toolbox/auditevent/blob/main/.github/workflows/release.yml all you need to...

> Your action uses the GH's ghcr.io registry, did you not have to give the keys to the action? Maybe the GH's registry is better integrated with GH actions? GitHub's...

@jhrozek supporting quay wouldn't be too problematic, all we need is a token and admin access to this repo. With admin access we're able to store the token in GitHub's...

I agree with this change (as noted by me clicking approve in this PR). While @andy-v-h 's default change may not be a silver bullet for security, it does set...

Thanks a lot for taking the time to submit this! I agree that it's unfortunate that it changes whitespaces within the file and it would be great if we would...

Seems the nginx hash changed again... it's not a very reliable image to use for tests

> I agree. In the other unit test I have used kubernetes 1.20 because of EOL, I don't think their hashes will change. What do you think? If yes, then...