- Return Values
- This module allows one to (re)generate OpenSSL private keys. It uses the pyOpenSSL python library to interact with openssl. One can generate either RSA or DSA private keys. Keys are generated in PEM format.
parameter | required | default | choices | comments |
---|---|---|---|---|
force | no |
| Should the key be regenerated even it it already exists | |
path | yes | Name of the file in which the generated TLS/SSL private key will be written. It will have 0600 mode. | ||
size | no | 4096 | Size (in bits) of the TLS/SSL key to generate | |
state | no | present |
| Whether the private key should exist or not, taking action if the state is different from what is stated. |
type | no | RSA |
| The algorithm used to generate the TLS/SSL private key |
This module allows one to (re)generate OpenSSL public keys from their private keys. Linux generate rsa key. Keys are generated in PEM or OpenSSH format. The module can use the cryptography Python library, or the pyOpenSSL Python library. Oct 12, 2018 In this blog we will Setup SSH Key and initial user using Ansible Playbook. To create new user on ubuntu system, you need the following things. It will generate the public and private key file. Automate deployment of SSL private key using Ansible. Ask Question Asked 4 years. Encrypt the private key file (aescrypt, openssl, pgp). A third option would be to generate a new private key with each deployment and try to find a certificate provider who accommodates automatic certificate requests. This could be complicated. This module allows one to (re)generate OpenSSL private keys. It uses the pyOpenSSL python library to interact with openssl. One can generate either RSA or DSA private keys. I want to use a public aws keypair.pem file for running ansible playbooks. I want to do this without changing my /.ssh/idrsa.pub and I can't create a new keypair from my current /.ssh/idrsa.p.
It was there on anold XP CD SP2 I had around. Windows server 2003 standard edition product key generator free. Explore the CD and navigate to the i386 folder.Open the file UNATTEND.txt and scroll down to the last line.You will find your Windows XP Product key there. The CD I had has a key of 'CD87T-HFP4C-V7X7H-8VY68-W7D7M'.I wonder if that key will work for anyone else (my XP computers all havelegitimate Microsoft keys already)?Can you help me?I am now preparing a suit against Microsoft for misrepresenting their copyrightsunder the DMCA and so on. My guess is that these keys onthe CD are best to use as there would be the same CD key for thousands ofcomputers (all the CDs which were printed with that key) so Microsoft wouldhave a hard time invalidating a CD key which is used legitimately by thousandsof computers. If you find a CD key on your installationCD, please let me know how it works out.
Common return values are documented here Return Values, the following are the fields unique to this module:
name | description | returned | type | sample |
---|---|---|---|---|
size | Size (in bits) of the TLS/SSL private key | ['changed', 'success'] | integer | 4096 |
type | Algorithm used to generate the TLS/SSL private key | ['changed', 'success'] | string | RSA |
filename | Path to the generated TLS/SSL private key file | ['changed', 'success'] | string | /etc/ssl/private/ansible.com.pem |
This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.
This module is community maintained without core committer oversight.
For more information on what this means please read Module Support
For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Helping Testing PRs and Developing Modules.
- This module allows one to (re-)generate PKCS#12.
The below requirements are needed on the host that executes this module.
- python-pyOpenSSL
Parameter | Choices/Defaults | Comments |
---|---|---|
action string |
| export or parse a PKCS#12. |
attributes string | The attributes the resulting 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. The = operator is assumed as default, otherwise + or - operators need to be included in the string. | |
backup added in 2.8 |
| Create a backup file including a timestamp so you can get the original output file back if you overwrote it with a new one by accident. |
certificate_path path | The path to read certificates and private keys from. | |
force |
| Should the file be regenerated even if it already exists. |
friendly_name string | Specifies the friendly name for the certificate and private key. | |
group | Name of the group that should own the file/directory, as would be fed to chown. | |
iter_size integer | Default: | Number of times to repeat the encryption step. |
maciter_size integer | Default: | Number of times to repeat the MAC step. |
mode string | The permissions the resulting file or directory should have. 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 Ansible 1.8, the mode may be specified as a symbolic mode (for example, u+rwx or u=rw,g=r,o=r ).As of Ansible 2.6, the mode may also be the special string preserve .When set to preserve the file will be given the same permissions as the source file. | |
other_certificates list / elements=path | List of other certificates to include. Pre 2.8 this parameter was called ca_certificates | |
owner | Name of the user that should own the file/directory, as would be fed to chown. | |
passphrase string | ||
path | Filename to write the PKCS#12 file to. | |
privatekey_passphrase string | Passphrase source to decrypt any input private keys with. | |
privatekey_path path | ||
selevel | Default: 's0' | This is the MLS/MCS attribute, sometimes known as the range .When set to _default , it will use the level portion of the policy if available. |
serole string | When set to _default , it will use the role portion of the policy if available. | |
setype string | When set to _default , it will use the type portion of the policy if available. | |
seuser string | By default it uses the system policy, where applicable.When set to _default , it will use the user portion of the policy if available. | |
src path | ||
state |
| Whether the file should exist or not. All parameters except path are ignored when state is absent . |
unsafe_writes boolean |
| Influence when to use atomic operation to prevent data corruption or inconsistent reads from the target file. 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. |
See also Generate rsa public key android software.
- openssl_certificate – Generate and/or check OpenSSL certificates
- The official documentation on the openssl_certificate module.
- openssl_csr – Generate OpenSSL Certificate Signing Request (CSR)
- The official documentation on the openssl_csr module.
- openssl_dhparam – Generate OpenSSL Diffie-Hellman Parameters
- The official documentation on the openssl_dhparam module.
- openssl_privatekey – Generate OpenSSL private keys
- The official documentation on the openssl_privatekey module.
- openssl_publickey – Generate an OpenSSL public key from its private key
- The official documentation on the openssl_publickey module.
Common return values are documented here, the following are the fields unique to this module:
Key | Returned | Description |
---|---|---|
backup_file string | changed and if backup is yes | Sample: |
filename | changed or success | Path to the generate PKCS#12 file. /opt/certs/ansible.p12 |
privatekey string | changed or success | Path to the TLS/SSL private key the public key was generated from. /etc/ssl/private/ansible.com.pem |
- This module is not guaranteed to have a backwards compatible interface. [preview]
- This module is maintained by the Ansible Community. [community]
Authors¶
- Guillaume Delpierre (@gdelpierre)
Hint
Ansible Openssl Generate Private Key For Putty
If you notice any issues in this documentation, you can edit this document to improve it.