diff --git a/branch/main/openssh_cert_module.html b/branch/main/openssh_cert_module.html index abb4ffaf..b397f513 100644 --- a/branch/main/openssh_cert_module.html +++ b/branch/main/openssh_cert_module.html @@ -280,12 +280,12 @@ see

any

The permissions the resulting filesystem object should have.

-

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

+

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

Giving Ansible a number without following either 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).

-

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

-

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

-

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

+

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).

+

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

+

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

+

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

@@ -375,7 +375,7 @@ see

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -391,7 +391,7 @@ see

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -399,7 +399,7 @@ see

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -407,8 +407,8 @@ see

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.

diff --git a/branch/main/openssh_keypair_module.html b/branch/main/openssh_keypair_module.html index 760df672..e3f06803 100644 --- a/branch/main/openssh_keypair_module.html +++ b/branch/main/openssh_keypair_module.html @@ -282,12 +282,12 @@ see

any

The permissions the resulting filesystem object should have.

-

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

+

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

Giving Ansible a number without following either 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).

-

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

-

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

-

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

+

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).

+

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

+

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

+

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

@@ -364,7 +364,7 @@ see

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -372,7 +372,7 @@ see

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -380,7 +380,7 @@ see

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -388,8 +388,8 @@ see

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.

diff --git a/branch/main/openssl_csr_module.html b/branch/main/openssl_csr_module.html index 25f3bea9..c130f6ff 100644 --- a/branch/main/openssl_csr_module.html +++ b/branch/main/openssl_csr_module.html @@ -496,12 +496,12 @@ see

any

The permissions the resulting filesystem object should have.

-

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

+

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

Giving Ansible a number without following either 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).

-

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

-

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

-

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

+

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).

+

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

+

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

+

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

@@ -658,7 +658,7 @@ see

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -666,7 +666,7 @@ see

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -674,7 +674,7 @@ see

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -682,8 +682,8 @@ see

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.

diff --git a/branch/main/openssl_dhparam_module.html b/branch/main/openssl_dhparam_module.html index 1a48d1ed..bf98b575 100644 --- a/branch/main/openssl_dhparam_module.html +++ b/branch/main/openssl_dhparam_module.html @@ -274,12 +274,12 @@ see

any

The permissions the resulting filesystem object should have.

-

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

+

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

Giving Ansible a number without following either 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).

-

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

-

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

-

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

+

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).

+

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

+

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

+

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

@@ -334,7 +334,7 @@ see

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -342,7 +342,7 @@ see

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -350,7 +350,7 @@ see

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -358,8 +358,8 @@ see

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.

diff --git a/branch/main/openssl_pkcs12_module.html b/branch/main/openssl_pkcs12_module.html index 7cf628e9..b5576596 100644 --- a/branch/main/openssl_pkcs12_module.html +++ b/branch/main/openssl_pkcs12_module.html @@ -335,12 +335,12 @@ see

any

The permissions the resulting filesystem object should have.

-

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

+

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

Giving Ansible a number without following either 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).

-

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

-

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

-

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

+

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).

+

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

+

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

+

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

@@ -450,7 +450,7 @@ see

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -458,7 +458,7 @@ see

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -466,7 +466,7 @@ see

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -474,8 +474,8 @@ see

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.

diff --git a/branch/main/openssl_privatekey_convert_module.html b/branch/main/openssl_privatekey_convert_module.html index 2bcee64f..1176b85d 100644 --- a/branch/main/openssl_privatekey_convert_module.html +++ b/branch/main/openssl_privatekey_convert_module.html @@ -288,12 +288,12 @@ see

any

The permissions the resulting filesystem object should have.

-

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

+

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

Giving Ansible a number without following either 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).

-

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

-

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

-

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

+

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).

+

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

+

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

+

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

@@ -311,7 +311,7 @@ see

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -319,7 +319,7 @@ see

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -327,7 +327,7 @@ see

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -335,8 +335,8 @@ see

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.

diff --git a/branch/main/openssl_privatekey_module.html b/branch/main/openssl_privatekey_module.html index 2f63a71c..4c0d18b8 100644 --- a/branch/main/openssl_privatekey_module.html +++ b/branch/main/openssl_privatekey_module.html @@ -347,12 +347,12 @@ see

any

The permissions the resulting filesystem object should have.

-

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

+

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

Giving Ansible a number without following either 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).

-

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

-

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

-

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

+

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).

+

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

+

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

+

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

@@ -436,7 +436,7 @@ see

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -444,7 +444,7 @@ see

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -452,7 +452,7 @@ see

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -460,8 +460,8 @@ see

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.

diff --git a/branch/main/openssl_publickey_module.html b/branch/main/openssl_publickey_module.html index e7828d39..42cb59a5 100644 --- a/branch/main/openssl_publickey_module.html +++ b/branch/main/openssl_publickey_module.html @@ -285,12 +285,12 @@ see

any

The permissions the resulting filesystem object should have.

-

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

+

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

Giving Ansible a number without following either 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).

-

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

-

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

-

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

+

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).

+

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

+

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

+

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

@@ -366,7 +366,7 @@ see

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -374,7 +374,7 @@ see

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -382,7 +382,7 @@ see

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -390,8 +390,8 @@ see

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.

diff --git a/branch/main/x509_certificate_convert_module.html b/branch/main/x509_certificate_convert_module.html index bbaf1d04..a857abae 100644 --- a/branch/main/x509_certificate_convert_module.html +++ b/branch/main/x509_certificate_convert_module.html @@ -268,12 +268,12 @@ To check whether it is installed, run

any

The permissions the resulting filesystem object should have.

-

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

+

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

Giving Ansible a number without following either 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).

-

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

-

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

-

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

+

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).

+

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

+

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

+

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

@@ -291,7 +291,7 @@ To check whether it is installed, run

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -299,7 +299,7 @@ To check whether it is installed, run

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -307,7 +307,7 @@ To check whether it is installed, run

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -315,8 +315,8 @@ To check whether it is installed, run

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.

diff --git a/branch/main/x509_certificate_module.html b/branch/main/x509_certificate_module.html index 1935d4ef..f1bd7833 100644 --- a/branch/main/x509_certificate_module.html +++ b/branch/main/x509_certificate_module.html @@ -461,12 +461,12 @@ see

any

The permissions the resulting filesystem object should have.

-

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

+

For those used to /usr/bin/chmod remember that modes are actually octal numbers. You must give Ansible enough information to parse them correctly. For consistent results, quote octal numbers (for example, '644' or '1777') so Ansible receives a string and can do its own conversion from string into number. Adding a leading zero (for example, 0755) works sometimes, but can fail in loops and some other circumstances.

Giving Ansible a number without following either 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).

-

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

-

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

-

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

+

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).

+

If mode is not specified and the destination filesystem object does not exist, the default umask on the system will be used when setting the mode for the newly created filesystem object.

+

If mode is not specified and the destination filesystem object does exist, the mode of the existing filesystem object will be used.

+

Specifying mode is the best way to ensure filesystem objects are created with the correct permissions. See CVE-2020-1736 for further details.

@@ -686,7 +686,7 @@ see

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -764,7 +764,7 @@ see

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -772,7 +772,7 @@ see

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -780,8 +780,8 @@ see

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.

diff --git a/branch/main/x509_crl_module.html b/branch/main/x509_crl_module.html index 910d4843..753592a0 100644 --- a/branch/main/x509_crl_module.html +++ b/branch/main/x509_crl_module.html @@ -580,7 +580,7 @@ see

The level part of the SELinux filesystem object context.

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.

+

When set to _default, it will use the level portion of the policy if available.

@@ -603,7 +603,7 @@ see

string

The role part of the SELinux filesystem object context.

-

When set to _default, it will use the role portion of the policy if available.

+

When set to _default, it will use the role portion of the policy if available.

@@ -611,7 +611,7 @@ see

string

The type part of the SELinux filesystem object context.

-

When set to _default, it will use the type portion of the policy if available.

+

When set to _default, it will use the type portion of the policy if available.

@@ -619,8 +619,8 @@ see

string

The user part of the SELinux filesystem object context.

-

By default it uses the system policy, where applicable.

-

When set to _default, it will use the user portion of the policy if available.

+

By default it uses the system policy, where applicable.

+

When set to _default, it will use the user portion of the policy if available.