mirror of
https://github.com/inspec/inspec
synced 2024-11-23 21:23:29 +00:00
c280e9a816
* Fix host resolution on Darwin, use dig wherever possible The `host` and `dig` commands do not return non-zero if a query returns NXDOMAIN or NOERROR, but the DarwinHostProvider was expecting it when deciding whether to fall back to IPv4 if a IPv6 query failed. Therefore, the `host` resource would not function properly when resolving hostnames on Darwin. The logic has been changed to use `dig` short output and query for both v6 and v4 addresses. Additionally, the LinuxHostProvider has been modified to prefer `dig` if it's available to keep behavior similar between Darwin and Linux whenever possible. This has the added benefit of providing v6 and v4 resolution if possible where `getent hosts` only returns v6 if v6 records exist. Signed-off-by: Adam Leff <adam@leff.co>
94 lines
2.3 KiB
Text
94 lines
2.3 KiB
Text
---
|
|
title: About the host Resource
|
|
---
|
|
|
|
# host
|
|
|
|
Use the `host` InSpec audit resource to test the name used to refer to a specific host and its availability, including the Internet protocols and ports over which that host name should be available.
|
|
|
|
## Syntax
|
|
|
|
A `host` resource block declares a host name, and then (depending on what is to be tested) a port and/or a protocol:
|
|
|
|
.. code-block:: ruby
|
|
|
|
describe host('example.com', port: 80, protocol: 'tcp') do
|
|
it { should be_reachable }
|
|
it { should be_resolvable }
|
|
its('ipaddress') { should include '12.34.56.78' }
|
|
end
|
|
|
|
where
|
|
|
|
* `host()` must specify a host name and may specify a port number and/or a protocol
|
|
* `'example.com'` is the host name
|
|
* `port:` is the port number
|
|
* `protocol: 'name'` is the Internet protocol: TCP (`protocol: 'tcp'`), UDP (`protocol: 'udp'` or ICMP (`protocol: 'icmp'`))
|
|
|
|
|
|
## Matchers
|
|
|
|
This InSpec audit resource has the following matchers:
|
|
|
|
### be
|
|
|
|
<%= partial "/shared/matcher_be" %>
|
|
|
|
### be_reachable
|
|
|
|
The `be_reachable` matcher tests if the host name is available:
|
|
|
|
it { should be_reachable }
|
|
|
|
### be_resolvable
|
|
|
|
The `be_resolvable` matcher tests for host name resolution, i.e. "resolvable to an IP address":
|
|
|
|
it { should be_resolvable }
|
|
|
|
### cmp
|
|
|
|
<%= partial "/shared/matcher_cmp" %>
|
|
|
|
### eq
|
|
|
|
<%= partial "/shared/matcher_eq" %>
|
|
|
|
### include
|
|
|
|
<%= partial "/shared/matcher_include" %>
|
|
|
|
### ipaddress
|
|
|
|
The `ipaddress` matcher tests if a host name is resolvable to a specific IP address:
|
|
|
|
its('ipaddress') { should include '93.184.216.34' }
|
|
|
|
### match
|
|
|
|
<%= partial "/shared/matcher_match" %>
|
|
|
|
## Examples
|
|
|
|
The following examples show how to use this InSpec audit resource.
|
|
|
|
### Verify host name is reachable over a specific protocol and port number
|
|
|
|
describe host('example.com', port: 80, protocol: 'tcp') do
|
|
it { should be_reachable }
|
|
end
|
|
|
|
### Verify that a specific IP address can be resolved
|
|
|
|
describe host('example.com') do
|
|
it { should be_resolvable }
|
|
its('ipaddress') { should include '192.168.1.1' }
|
|
end
|
|
|
|
### Review the connection setup and socket contents when checking reachability
|
|
|
|
describe host('example.com', port: 12345, protocol: 'tcp') do
|
|
it { should be_reachable }
|
|
its('connection') { should_not match /connection refused/ }
|
|
its('socket') { should match /STATUS_OK/ }
|
|
end
|