Re: help needed: LSM acronym
On 05/01/18 14:42, Adam Borowski wrote:
> Background: I'm working on a kernel facility to set a policy for filenames,
> for security reasons. The recommended defaults are banning '\n' and 01..31,
> the user can also elect to ban invalid Unicode, initial and final spaces,
> initial '-', etc. The initial hard-coded patch was NACKed, and I was told
> to re-do this as a LSM.
>
> A LSM needs a name, and the tradition is to use bad acronyms, of which "Yet
> Another Meaningless Acronym" takes the cake.
Limiting Unwanted Trespass: Enforcing File Identifier Subsets in the
Kernel (LUTEFISK).
-RTT
Reply to: