lynis/plugins
hlein b595cc0fb5 Various cleanups (#363)
* Typo fix.

* Style change: always use $(), never ``.

The Lynis code already mostly used $(), but backticks were sprinkled
around.  Converted all of them.

* Lots of minor spelling/typo fixes.

FWIW these were found with:

  find . -type f -print0 | xargs -0 cat | aspell list | sort -u | egrep '^[a-z]+$' | less

And then reviewing the list to pick out things that looked like
misspelled words as opposed to variables, etc., and then manual
inspection of context to determine the intention.
2017-03-06 07:41:21 +00:00
..
custom_plugin.template Improved templates and examples 2016-03-24 10:34:16 +01:00
plugin_pam_phase1 Various cleanups (#363) 2017-03-06 07:41:21 +00:00
plugin_systemd_phase1 Various cleanups (#363) 2017-03-06 07:41:21 +00:00
README Added note about community plugins and support address 2015-02-25 20:38:20 +01:00

##########################################################################
#
# This directory contains plugins
#
##########################################################################


  General notes
  ---------------

  Custom plugins should be added to this directory, so they are included
  in an audit.

  Notes:

    - File permissions of a plugin should be 600, 640 or the least
      restrictive 400.
    - Each plugin should be enabled in the profile, before it will be
      activated.
    - Custom plugins should use a test ID's with a "CUS-" prefix.

    A generic example can be found in the custom_plugin.template file,
    which includes several code snippets to assist in creating customer
    plugins.

    Community plugins are available under a restricted license.


**************************************************************************
    Would your plugin or individual test benefit Lynis and others?
   Share and be part of the Free and Open Source Software community!

   Support address: lynis-dev@cisofy.com
**************************************************************************