• help needed: LSM acronym

    From Adam Borowski@21:1/5 to All on Fri Jan 5 21:50:01 2018
    Hi!
    I'd like to ask for help with devising an acronym, as my ability with puns
    or other wordplay in any language is almost non-existant.

    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.

    The best I've been able to come up with was: kitteh "Kill Invalid Tree
    Terms, Evading Harm". This is groan-worthy, and especially "tree" is
    incorrect as files/dirs/sockets/fifos/etc are at most tree nodes.

    Thus, could someone suggest something betterer? It doesn't need to spell "kitteh", nor even anything cat themed, although obviously references to
    nasty things like dogs, Hitler or emacs (in decreasing order of badness)
    are unpreferred.

    Lamby suggested using a name that would be rejected by this module, but
    alas, I don't think a .c file by that name would get past the vfs
    maintainer.


    Meow!
    --
    // If you believe in so-called "intellectual property", please immediately
    // cease using counterfeit alphabets. Instead, contact the nearest temple
    // of Amon, whose priests will provide you with scribal services for all
    // your writing needs, for Reasonable And Non-Discriminatory prices.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marcin Sochacki@21:1/5 to All on Fri Jan 5 22:30:01 2018
    How about 'icanhaz'?

    Incorrect Characters Are Not HAZardous (anymore)

    Wanted

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robin Tarsiger@21:1/5 to Adam Borowski on Fri Jan 5 22:40:02 2018
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Armstrong@21:1/5 to Adam Borowski on Sat Jan 6 01:00:02 2018
    On Fri, 05 Jan 2018, Adam Borowski wrote:
    Thus, could someone suggest something betterer? It doesn't need to
    spell "kitteh", nor even anything cat themed, although obviously
    references to nasty things like dogs, Hitler or emacs (in decreasing
    order of badness) are unpreferred.

    Makes Evil Orthography Wrong

    or

    MEOWS: Evil Orthography Was Silenced


    Oooo. A bikeshed appears!

    --
    Don Armstrong https://www.donarmstrong.com

    I would like to be the air
    that inhabits you for a moment
    only. I would like to be that unnoticed
    & that necessary.
    -- Margaret Atwood "Poetry in Motion" p140

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ben Finney@21:1/5 to Adam Borowski on Sat Jan 6 08:10:01 2018
    Adam Borowski <kilobyte@angband.pl> writes:

    The best I've been able to come up with was: kitteh "Kill Invalid Tree
    Terms, Evading Harm". This is groan-worthy, and especially "tree" is incorrect as files/dirs/sockets/fifos/etc are at most tree nodes.

    Neuter Your Ambiguous Names

    --
    \ “I don't want to live peacefully with difficult realities, and |
    `\ I see no virtue in savoring excuses for avoiding a search for |
    _o__) real answers.” —Paul Z. Myers, 2009-09-12 | Ben Finney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Thomas Harding@21:1/5 to All on Sat Jan 6 10:10:02 2018
    Le 5 janvier 2018 21:42:31 GMT+01:00, Adam Borowski <kilobyte@angband.pl> a écrit :
    Hi!
    I'd like to ask for help with devising an acronym, as my ability with
    puns
    or other wordplay in any language is almost non-existant.

    Background: I'm working on a kernel facility to set a policy for
    filenames,

    While that will prevent as redirections nightmare as non-printables ones, I suggest something like a variation on :

    SCATTTY

    a) secure cat tty
    b) scat tty (like in jazz, yet pronunceable even meanless)
    c) shells can/could always type totally
    d) ? ...

    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.

    The best I've been able to come up with was: kitteh "Kill Invalid Tree
    Terms, Evading Harm". This is groan-worthy, and especially "tree" is >incorrect as files/dirs/sockets/fifos/etc are at most tree nodes.

    Thus, could someone suggest something betterer? It doesn't need to
    spell
    "kitteh", nor even anything cat themed, although obviously references
    to
    nasty things like dogs, Hitler or emacs (in decreasing order of
    badness)
    are unpreferred.

    Lamby suggested using a name that would be rejected by this module, but
    alas, I don't think a .c file by that name would get past the vfs
    maintainer.


    Meow!


    --
    Je suis née pour partager, non la haine, mais l'amour.
    Sophocle, Antigone, 442 av. J.C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Gunnar Wolf@21:1/5 to All on Sat Jan 6 23:30:01 2018
    Adam Borowski dijo [Fri, Jan 05, 2018 at 09:42:31PM +0100]:
    Hi!
    I'd like to ask for help with devising an acronym, as my ability with puns
    or other wordplay in any language is almost non-existant.

    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.

    A plus point for YAMA is that, in Spanish, we say "¿cómo se llama?"
    meaning "how is it called?" ("y" and "ll" are mostly homophone in this
    spot).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Enrico Zini@21:1/5 to Adam Borowski on Mon Jan 8 15:00:02 2018
    On Fri, Jan 05, 2018 at 09:42:31PM +0100, Adam Borowski wrote:

    Thus, could someone suggest something betterer? It doesn't need to spell "kitteh", nor even anything cat themed, although obviously references to nasty things like dogs, Hitler or emacs (in decreasing order of badness)
    are unpreferred.

    Because I am somewhat disturbed by your ranking, you get the acronym
    M-BLONDI:

    M-BLONDI Bans, Limits, Or Not, Damaging Identifiers.


    Enrico

    --
    GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.org>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Kenneth C. Rich@21:1/5 to Adam Borowski on Mon Jan 8 14:30:01 2018
    On 1/5/2018 3:42 PM, Adam Borowski wrote:
    The best I've been able to come up with was: kitteh "Kill Invalid Tree
    Terms, Evading Harm". This is groan-worthy, and especially "tree" is incorrect as files/dirs/sockets/fifos/etc are at most tree nodes.

    Meow!

    CUTEN

    Cull Undesirable Terminology & Evil Names

    --
    -Ken Rich
    System Administrator
    Asher Group
    585-643-8719
    585-586-0020 x119

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)