inspec 1.51.6 → 1.51.15

data/docs/resources/aide_conf.md.erb

@@ -1,78 +1,78 @@
----
-title: The aide_conf Resource
----
-
-# aide_conf
-
-Use the `aide_conf` InSpec audit resource to test the rules established for the file integrity tool AIDE. Controlled by the aide.conf file typically at /etc/aide.conf.
-
-<br>
-
-## Syntax
-
-An `aide_conf` resource block can be used to determine if the selection lines contain one (or more) directories whose files should be added to the aide database:
-
-    describe aide_conf('path') do
-      its('selection_lines') { should include '/sbin' }
-    end
-
-where
-
-* `'selection_lines'` refers to all selection lines found in the aide.conf file
-* `('path')` is the non-default path to the `aide.conf` file (optional)
-* `should include 'value'` is the value that is expected
-
-Use the where clause to match a selection_line to one rule or a particular set of rules found in the aide.conf file:
-
-    describe aide_conf.where { selection_line == '/bin' } do
-      its('rules.flatten') { should include 'r' }
-    end
-
-    describe aide_conf.where { selection_line == '/sbin' } do
-      its('rules') { should include ['p', 'i', 'l', 'n', 'u', 'g', 'sha512'] }
-    end
-
-<br>
-
-## Supported Properties
-
-* `conf_path`, `content`, `rules`, `all_have_rule`
-
-## Property Examples
-
-The following examples show how to use this InSpec audit resource. 
-
-### Test if all selection lines contain the xattr rule
-
-    describe aide_conf.all_have_rule('xattr') do
-      it { should eq true }
-    end
-
-### Test whether selection line for /bin contains a particular rule
-
-    describe aide_conf.where { selection_line == '/bin' } do
-      its('rules.flatten') { should include 'r' }
-    end
-
-### Test whether selection line for /sbin consists of a particular set of rules
-
-    describe aide_conf.where { selection_line == '/sbin' } do
-      its('rules') { should include ['r', 'sha512'] }
-    end
-
-### The usage of all\_have\_rule will return whether or not all selection lines in audit.conf contain a particular rule:
-
-    describe aide_conf.all_have_rule('sha512') do
-      it { should eq true }
-    end
-    
-<br>
-
-## Matchers
-
-For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
-This InSpec audit resource uses the matchers `eq` and `include`. 
-
-For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).
-
-
+---
+title: The aide_conf Resource
+---
+
+# aide_conf
+
+Use the `aide_conf` InSpec audit resource to test the rules established for the file integrity tool AIDE. Controlled by the aide.conf file typically at /etc/aide.conf.
+
+<br>
+
+## Syntax
+
+An `aide_conf` resource block can be used to determine if the selection lines contain one (or more) directories whose files should be added to the aide database:
+
+    describe aide_conf('path') do
+      its('selection_lines') { should include '/sbin' }
+    end
+
+where
+
+* `'selection_lines'` refers to all selection lines found in the aide.conf file
+* `('path')` is the non-default path to the `aide.conf` file (optional)
+* `should include 'value'` is the value that is expected
+
+Use the where clause to match a selection_line to one rule or a particular set of rules found in the aide.conf file:
+
+    describe aide_conf.where { selection_line == '/bin' } do
+      its('rules.flatten') { should include 'r' }
+    end
+
+    describe aide_conf.where { selection_line == '/sbin' } do
+      its('rules') { should include ['p', 'i', 'l', 'n', 'u', 'g', 'sha512'] }
+    end
+
+<br>
+
+## Supported Properties
+
+* `conf_path`, `content`, `rules`, `all_have_rule`
+
+## Property Examples
+
+The following examples show how to use this InSpec audit resource. 
+
+### Test if all selection lines contain the xattr rule
+
+    describe aide_conf.all_have_rule('xattr') do
+      it { should eq true }
+    end
+
+### Test whether selection line for /bin contains a particular rule
+
+    describe aide_conf.where { selection_line == '/bin' } do
+      its('rules.flatten') { should include 'r' }
+    end
+
+### Test whether selection line for /sbin consists of a particular set of rules
+
+    describe aide_conf.where { selection_line == '/sbin' } do
+      its('rules') { should include ['r', 'sha512'] }
+    end
+
+### The usage of all\_have\_rule will return whether or not all selection lines in audit.conf contain a particular rule:
+
+    describe aide_conf.all_have_rule('sha512') do
+      it { should eq true }
+    end
+    
+<br>
+
+## Matchers
+
+For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
+This InSpec audit resource uses the matchers `eq` and `include`. 
+
+For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).
+
+

data/docs/resources/apache.md.erb

@@ -1,66 +1,66 @@
----
-title: About the apache Resource
----
-
-# apache
-
-Use the `apache` InSpec audit resource to test the state of the Apache server on Linux/Unix systems.
-
-<p class="warning">This resource is deprecated and should not be used. It will be removed in InSpec 3.0.</p>
-
-<br>
-
-## Syntax
-
-An `apache` InSpec audit resource block declares settings that should be tested:
-
-    describe apache do
-      its('setting_name') { should cmp 'value' }
-    end
-
-where
-
-* `'setting_name'` is description of the Apache configuration file
-* `{ should cmp 'value' }` is the value that is expected
-
-<br>
-
-## Supported Properties
-
-* 'service', 'conf_dir', 'conf_path', 'user'
-
-<br>
-
-## Property Examples
-
-The following examples show how to use this InSpec audit resource.
-
-### Test the service name.
-
-    describe apache do
-      its ('service') { should cmp 'apache2' }
-    end
-
-### Test the configuration location
-
-    describe apache do
-      its ('conf_dir') { should cmp '/etc/apache2' }
-    end
-
-### Test the path of the configuration file
-
-    describe apache do
-      its ('conf_path') { should cmp '/etc/apache2/apache2.conf' }
-    end
-
-### Test the apache user
-
-    describe apache do
-      its ('user') { should cmp 'www-data' }
-    end
-
-<br>
-
-## Matchers
-
-For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).
+---
+title: About the apache Resource
+---
+
+# apache
+
+Use the `apache` InSpec audit resource to test the state of the Apache server on Linux/Unix systems.
+
+<p class="warning">This resource is deprecated and should not be used. It will be removed in InSpec 3.0.</p>
+
+<br>
+
+## Syntax
+
+An `apache` InSpec audit resource block declares settings that should be tested:
+
+    describe apache do
+      its('setting_name') { should cmp 'value' }
+    end
+
+where
+
+* `'setting_name'` is description of the Apache configuration file
+* `{ should cmp 'value' }` is the value that is expected
+
+<br>
+
+## Supported Properties
+
+* 'service', 'conf_dir', 'conf_path', 'user'
+
+<br>
+
+## Property Examples
+
+The following examples show how to use this InSpec audit resource.
+
+### Test the service name.
+
+    describe apache do
+      its ('service') { should cmp 'apache2' }
+    end
+
+### Test the configuration location
+
+    describe apache do
+      its ('conf_dir') { should cmp '/etc/apache2' }
+    end
+
+### Test the path of the configuration file
+
+    describe apache do
+      its ('conf_path') { should cmp '/etc/apache2/apache2.conf' }
+    end
+
+### Test the apache user
+
+    describe apache do
+      its ('user') { should cmp 'www-data' }
+    end
+
+<br>
+
+## Matchers
+
+For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).

data/docs/resources/apache_conf.md.erb

@@ -1,67 +1,67 @@
----
-title: About the apache_conf Resource
----
-
-# apache_conf
-
-Use the `apache_conf` InSpec audit resource to test the configuration settings for Apache. This file is typically located under `/etc/apache2` on the Debian and Ubuntu platforms and under `/etc/httpd` on the Fedora, CentOS, RedHat Enterprise Linux, and ArchLinux platforms. The configuration settings may vary significantly from platform to platform.
-
-<br>
-
-## Syntax
-
-An `apache_conf` InSpec audit resource block declares configuration settings that should be tested:
-
-    describe apache_conf('path') do
-      its('setting_name') { should eq 'value' }
-    end
-
-where
-
-* `'setting_name'` is a configuration setting defined in the Apache configuration file
-* `('path')` is the non-default path to the Apache configuration file
-* `{ should eq 'value' }` is the value that is expected
-
-<br>
-
-## Examples
-
-The following examples show how to use this InSpec audit resource.
-
-### Test for blocking .htaccess files on CentOS
-
-    describe apache_conf do
-      its('AllowOverride') { should cmp 'None' }
-    end
-
-### Test ports for SSL
-
-    describe apache_conf do
-      its('Listen') { should cmp '443' }
-    end
-
-### Test multiple ports are listening
-
-    describe apache_conf do
-      its('Listen') { should =~ [ '80', '443' ] }
-    end
-
-<br>
-
-## Matchers
-
-For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).
-This InSpec audit resource matches any service that is listed in the Apache configuration file:
-
-    its('PidFile') { should_not eq '/var/run/httpd.pid' }
-
-or:
-
-    its('Timeout') { should cmp '300' }
-
-For example:
-
-    describe apache_conf do
-      its('MaxClients') { should cmp '100' }
-      its('Listen') { should cmp '443' }
-    end
+---
+title: About the apache_conf Resource
+---
+
+# apache_conf
+
+Use the `apache_conf` InSpec audit resource to test the configuration settings for Apache. This file is typically located under `/etc/apache2` on the Debian and Ubuntu platforms and under `/etc/httpd` on the Fedora, CentOS, RedHat Enterprise Linux, and ArchLinux platforms. The configuration settings may vary significantly from platform to platform.
+
+<br>
+
+## Syntax
+
+An `apache_conf` InSpec audit resource block declares configuration settings that should be tested:
+
+    describe apache_conf('path') do
+      its('setting_name') { should eq 'value' }
+    end
+
+where
+
+* `'setting_name'` is a configuration setting defined in the Apache configuration file
+* `('path')` is the non-default path to the Apache configuration file
+* `{ should eq 'value' }` is the value that is expected
+
+<br>
+
+## Examples
+
+The following examples show how to use this InSpec audit resource.
+
+### Test for blocking .htaccess files on CentOS
+
+    describe apache_conf do
+      its('AllowOverride') { should cmp 'None' }
+    end
+
+### Test ports for SSL
+
+    describe apache_conf do
+      its('Listen') { should cmp '443' }
+    end
+
+### Test multiple ports are listening
+
+    describe apache_conf do
+      its('Listen') { should =~ [ '80', '443' ] }
+    end
+
+<br>
+
+## Matchers
+
+For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).
+This InSpec audit resource matches any service that is listed in the Apache configuration file:
+
+    its('PidFile') { should_not eq '/var/run/httpd.pid' }
+
+or:
+
+    its('Timeout') { should cmp '300' }
+
+For example:
+
+    describe apache_conf do
+      its('MaxClients') { should cmp '100' }
+      its('Listen') { should cmp '443' }
+    end

data/docs/resources/apt.md.erb

@@ -1,70 +1,70 @@
----
-title: About the apt Resource
----
-
-# apt
-
-Use the `apt` InSpec audit resource to verify Apt repositories on the Debian and Ubuntu platforms, and also PPA repositories on the Ubuntu platform.
-
-<br>
-
-## Syntax
-
-An `apt` resource block tests the contents of Apt and PPA repositories:
-
-    describe apt('path') do
-      it { should exist }
-      it { should be_enabled }
-    end
-
-where
-
-* `apt('path')` must specify an Apt or PPA repository
-* `('path')` may be an `http://` address, a `ppa:` address, or a short `repo-name/ppa` address
-* `exist` and `be_enabled` are a valid matchers for this resource
-
-<br>
-
-## Examples
-
-The following examples show how to use this InSpec audit resource.
-
-### Test if apt repository exists and is enabled
-
-    describe apt('http://ppa.launchpad.net/juju/stable/ubuntu') do
-      it { should exist }
-      it { should be_enabled }
-    end
-
-### Verify that a PPA repository exists and is enabled
-
-    describe apt('ppa:nginx/stable') do
-      it { should exist }
-      it { should be_enabled }
-    end
-
-### Verify that a repository is not present
-
-    describe apt('ubuntu-wine/ppa') do
-      it { should_not exist }
-      it { should_not be_enabled }
-    end
-
-<br>
-
-## Matchers
-
-For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
-
-
-### be_enabled
-
-The `be_enabled` matcher tests if a package exists in the repository:
-
-    it { should be_enabled }
-
-### exist
-
-The `exist` matcher tests if a package exists on the system:
-
-    it { should exist }
+---
+title: About the apt Resource
+---
+
+# apt
+
+Use the `apt` InSpec audit resource to verify Apt repositories on the Debian and Ubuntu platforms, and also PPA repositories on the Ubuntu platform.
+
+<br>
+
+## Syntax
+
+An `apt` resource block tests the contents of Apt and PPA repositories:
+
+    describe apt('path') do
+      it { should exist }
+      it { should be_enabled }
+    end
+
+where
+
+* `apt('path')` must specify an Apt or PPA repository
+* `('path')` may be an `http://` address, a `ppa:` address, or a short `repo-name/ppa` address
+* `exist` and `be_enabled` are a valid matchers for this resource
+
+<br>
+
+## Examples
+
+The following examples show how to use this InSpec audit resource.
+
+### Test if apt repository exists and is enabled
+
+    describe apt('http://ppa.launchpad.net/juju/stable/ubuntu') do
+      it { should exist }
+      it { should be_enabled }
+    end
+
+### Verify that a PPA repository exists and is enabled
+
+    describe apt('ppa:nginx/stable') do
+      it { should exist }
+      it { should be_enabled }
+    end
+
+### Verify that a repository is not present
+
+    describe apt('ubuntu-wine/ppa') do
+      it { should_not exist }
+      it { should_not be_enabled }
+    end
+
+<br>
+
+## Matchers
+
+For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/). 
+
+
+### be_enabled
+
+The `be_enabled` matcher tests if a package exists in the repository:
+
+    it { should be_enabled }
+
+### exist
+
+The `exist` matcher tests if a package exists on the system:
+
+    it { should exist }