Adoptable Cookbooks List

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Attributes

node['openvpn']['client_cn'] - The client's Common Name used with the openvpn::client recipe (essentially a standalone recipe) for the client certificate and key.

node['openvpn']['type'] - Valid values are 'client' (currently a work in progress), 'server' or 'server-bridge'. Default is 'server' and it will create a routed IP tunnel, and use the 'tun' device. 'server-bridge' will create an ethernet bridge and requires a tap0 device bridged with the ethernet interface, and is beyond the scope of this cookbook.

node['openvpn']['subnet'] - Used for server mode to configure a VPN subnet to draw client addresses. Default is 10.8.0.0, which is what the sample OpenVPN config package uses.

node['openvpn']['netmask'] - Netmask for the subnet, default is 255.255.0.0.

node['openvpn']['client_prefix'] - String. Name of the config that is created for clients. When imported into most vpn clients, this is the name that will be displayed for the connection. Default is 'vpn-prod'.

node['openvpn']['cookbook_user_conf'] - String. The cookbook used by the openvpn::users recipe for the client.conf.erb template. You can override this to your own, such as your wrapper cookbook. Default is 'openvpn'.

node['openvpn']['config']['script-security'] - Script Security setting to use in server config. Default is 1. The "up" script will not be included in the configuration if this is 0 or 1. Set it to 2 to use the "up" script.

The following attributes are used to populate the easy-rsa vars file. Defaults are the same as the vars file that ships with OpenVPN.

node['openvpn']['key']['ca_expire'] - In how many days should the root CA key expire - CA_EXPIRE.

node['openvpn']['key']['expire'] - In how many days should certificates expire - KEY_EXPIRE.

node['openvpn']['key"]['size'] - Default key size, set to 2048 if paranoid but will slow down TLS negotiation performance - KEY_SIZE.

The following are for the default values for fields place in the certificate from the vars file. Do not leave these blank.

node['openvpn']['key']['country'] - KEY_COUNTRY

node['openvpn']['key']['province'] - KEY_PROVINCE

node['openvpn']['key']['city'] - KEY_CITY

node['openvpn']['key']['org'] - KEY_ORG

node['openvpn']['key']['email'] - KEY_EMAIL

The following lets you specify the message digest used for generating certificates by OpenVPN
* node['openvpn']['key']['message_digest'] - Default is sha256 for a high-level of security.

Recipes

openvpn::default

Installs the OpenVPN package only.

openvpn::install

Installs the OpenVPN package only.

openvpn::server

Installs and configures OpenVPN as a server.

openvpn::client

Installs and configures OpenVPN as a client.

openvpn::service

Manages the OpenVPN system service (there is no need to use this recipe directly in your run_list).

openvpn::users

Utilizes a data bag called users to generate OpenVPN keys for each user.
chef-solo-search is required in order to use this recipe with Chef-Solo, although it is not a dependency of this cookbook.

To automatically create new certificates and configurations for users, create data bags for each user. The only content required is the id, but this can be used in conjunction with other cookbooks by Chef Software such as users or samba. See SSL Certificates below for more about generating client certificate sets.

{
"id": "jtimberman"
}

This cookbook also provides an 'up' script that runs when OpenVPN is started. This script is for setting up firewall rules and kernel networking parameters as needed for your environment. Modify to suit your needs, upload the cookbook and re-run chef on the openvpn server. For example, you'll probably want to enable IP forwarding (sample Linux setting is commented out). The attribute node['openvpn']["script_security"] must be set to 2 or higher to use this otherwise openvpn server startup will fail.

Customizing Server Configuration

To further customize the server configuration, there are two templates that can be modified in this cookbook.

templates/default/server.conf.erb

templates/default/server.up.sh.erb

The first is the OpenVPN server configuration file. Modify to suit your needs for more advanced features of OpenVPN. The second is an up script run when OpenVPN starts. This is where you can add firewall rules, enable IP forwarding and other OS network settings required for OpenVPN. Attributes in the cookbook are provided as defaults, you can add more via the openvpn role if you need them.

Using the LWRP

To create (possibly multiple) "conf" files on a server, use openvpn_conf "name". See the conf.rb file in the resources directory to find the supported attributes, or add some of your own. If you don't want to use the default "server.conf" from the default recipe, set node['openvpn']["configure_default_server"] to false, then use the LWRP to configure as many as you like.

SSL Certificates

Some of the easy-rsa tools are copied to /etc/openvpn/easy-rsa to provide the minimum to generate the certificates using the default and users recipes. We provide a Rakefile to make it easier to generate client certificate sets if you're not using the data bags above. To generate new client certificates you will need rake installed (either as a gem or a package), then run:

License & Authors

Copyright:: 2009-2018, Chef Software, Inc
Copyright:: 2018-2018, Xhost Australia
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.