Documentation

openssl_dhparam - Generate OpenSSL Diffie-Hellman Parameters

New in version 2.5.

Synopsis

  • This module allows one to (re)generate OpenSSL DH-params. This module uses file common arguments to specify generated file permissions.

Requirements

The below requirements are needed on the host that executes this module.

  • OpenSSL

Parameters

Parameter Choices/Defaults Comments
attributes
(added in 2.3)
Attributes the file or directory should have. To get supported flags look at the man page for chattr on the target system. This string should contain the attributes in the same order as the one displayed by lsattr.
= operator is assumed as default, otherwise + or - operators need to be included in the string.

aliases: attr
force
bool
    Choices:
  • no ←
  • yes
Should the parameters be regenerated even it it already exists
group
Name of the group that should own the file/directory, as would be fed to chown.
mode
Mode the file or directory should be. For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must either add a leading zero so that Ansible's YAML parser knows it is an octal number (like 0644 or 01777) or quote it (like '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Giving Ansible a number without following one of these rules will end up with a decimal number which will have unexpected results. As of version 1.8, the mode may be specified as a symbolic mode (for example, u+rwx or u=rw,g=r,o=r).
owner
Name of the user that should own the file/directory, as would be fed to chown.
path
required
Name of the file in which the generated parameters will be saved.
selevel Default:
s0
Level part of the SELinux file context. This is the MLS/MCS attribute, sometimes known as the range. _default feature works as for seuser.
serole
Role part of SELinux file context, _default feature works as for seuser.
setype
Type part of SELinux file context, _default feature works as for seuser.
seuser
User part of SELinux file context. Will default to system policy, if applicable. If set to _default, it will use the user portion of the policy if available.
size Default:
4096
Size (in bits) of the generated DH-params
state
    Choices:
  • present ←
  • absent
Whether the parameters should exist or not, taking action if the state is different from what is stated.
unsafe_writes
bool

(added in 2.2)
    Choices:
  • no ←
  • yes
By default this module uses atomic operations to prevent data corruption or inconsistent reads from the target files, but sometimes systems are configured or just broken in ways that prevent this. One example is docker mounted files, which cannot be updated atomically from inside the container and can only be written in an unsafe manner.
This option allows Ansible to fall back to unsafe methods of updating files when atomic operations fail (however, it doesn't force Ansible to perform unsafe writes). IMPORTANT! Unsafe writes are subject to race conditions and can lead to data corruption.

Examples

# Generate Diffie-Hellman parameters with the default size (4096 bits)
- openssl_dhparam:
    path: /etc/ssl/dhparams.pem

# Generate DH Parameters with a different size (2048 bits)
- openssl_dhparam:
    path: /etc/ssl/dhparams.pem
    size: 2048

# Force regenerate an DH parameters if they already exist
- openssl_dhparam:
    path: /etc/ssl/dhparams.pem
    force: True

Return Values

Common return values are documented here, the following are the fields unique to this module:

Key Returned Description
filename
string
changed or success
Path to the generated Diffie-Hellman parameters

Sample:
/etc/ssl/dhparams.pem
size
int
changed or success
Size (in bits) of the Diffie-Hellman parameters

Sample:
4096


Status

This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.

Maintenance

This module is flagged as community which means that it is maintained by the Ansible Community. See Module Maintenance & Support for more info.

For a list of other modules that are also maintained by the Ansible Community, see here.

Author

  • Thom Wiggers (@thomwiggers)

Hint

If you notice any issues in this documentation you can edit this document to improve it.