Neil Horman
Neil Horman
@vdukhovni do you have a proposal for change here? you revived this conversation 2 years ago, I assume you have a proposal for what you would like to see done...
I have a question regarding the container id assignment mechanism. Curently the patch in the v4 posted series loosely defines a container by virtue of the fact that a nonce...
>I'm replying strictly from memory here, so I might have some of the minor details wrong, but managing the audit container ID should require CAP_AUDIT_ADMIN. The idea being that only...
@rgbriggs @pcmoore Forgive me for consolidating your above responses, but the conversation it getting lengthy and I'm having trouble keeping up with all the comments. To abbreviate your thoughts on...
@rgbriggs Hey, thanks for the response. Answers to your thoughts: >I will have to look at setsid more closely. I assumed you were talking about the audit sessionid which has...
I would strongly agree with that. Even if the kernel is not responsible for computation of a unique id, it should be able to validate the uniqueness of an id...
marking as inactive, to be closed at the end of 3.4 dev barring further input
@paulidale you're right, this was mislabeled on my part this should be marked for a future minor version
Engines are deprecated, its unlikely this will ever be addressed Marking as inactive, to be closed at the end of 3.4 dev barring further input
@t8m @mattcaswell can you elaborate on what the documentation update here might entail?