From df36e2cd9c463897997815d432ebf7b39d267344 Mon Sep 17 00:00:00 2001 From: felixfontein Date: Wed, 23 Oct 2024 09:07:42 +0000 Subject: [PATCH] deploy: 7c93b61532beba699b85e67ceb14a174aac2f04b --- branch/main/openssh_cert_module.html | 10 +++++----- branch/main/openssh_keypair_module.html | 10 +++++----- branch/main/openssl_csr_module.html | 10 +++++----- branch/main/openssl_dhparam_module.html | 10 +++++----- branch/main/openssl_pkcs12_module.html | 10 +++++----- branch/main/openssl_privatekey_convert_module.html | 10 +++++----- branch/main/openssl_privatekey_module.html | 10 +++++----- branch/main/openssl_publickey_module.html | 10 +++++----- branch/main/x509_certificate_convert_module.html | 10 +++++----- branch/main/x509_certificate_module.html | 10 +++++----- branch/main/x509_crl_module.html | 8 ++++---- 11 files changed, 54 insertions(+), 54 deletions(-) diff --git a/branch/main/openssh_cert_module.html b/branch/main/openssh_cert_module.html index 7fc5c0e4..3621a860 100644 --- a/branch/main/openssh_cert_module.html +++ b/branch/main/openssh_cert_module.html @@ -226,8 +226,8 @@ see string

The attributes the resulting filesystem object 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.

+

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.

@@ -248,7 +248,7 @@ see

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

@@ -278,7 +278,7 @@ 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.

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

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.

diff --git a/branch/main/openssh_keypair_module.html b/branch/main/openssh_keypair_module.html index a8d228d7..56959b50 100644 --- a/branch/main/openssh_keypair_module.html +++ b/branch/main/openssh_keypair_module.html @@ -228,8 +228,8 @@ see string

The attributes the resulting filesystem object 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.

+

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.

@@ -271,7 +271,7 @@ see

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

@@ -280,7 +280,7 @@ 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.

@@ -292,7 +292,7 @@ see

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.

diff --git a/branch/main/openssl_csr_module.html b/branch/main/openssl_csr_module.html index 45dcc3ea..9ba6b187 100644 --- a/branch/main/openssl_csr_module.html +++ b/branch/main/openssl_csr_module.html @@ -230,8 +230,8 @@ see string

The attributes the resulting filesystem object 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.

+

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.

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

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

@@ -494,7 +494,7 @@ 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.

@@ -586,7 +586,7 @@ see

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.

diff --git a/branch/main/openssl_dhparam_module.html b/branch/main/openssl_dhparam_module.html index e76fe31a..379c0adc 100644 --- a/branch/main/openssl_dhparam_module.html +++ b/branch/main/openssl_dhparam_module.html @@ -230,8 +230,8 @@ see string

The attributes the resulting filesystem object 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.

+

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.

@@ -263,7 +263,7 @@ see

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

@@ -272,7 +272,7 @@ 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.

@@ -284,7 +284,7 @@ see

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.

diff --git a/branch/main/openssl_pkcs12_module.html b/branch/main/openssl_pkcs12_module.html index 9248e9cd..66ce56a5 100644 --- a/branch/main/openssl_pkcs12_module.html +++ b/branch/main/openssl_pkcs12_module.html @@ -239,8 +239,8 @@ see string

The attributes the resulting filesystem object 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.

+

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.

@@ -305,7 +305,7 @@ see

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

@@ -333,7 +333,7 @@ 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.

@@ -368,7 +368,7 @@ see

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.

diff --git a/branch/main/openssl_privatekey_convert_module.html b/branch/main/openssl_privatekey_convert_module.html index da977e4e..e3571f0c 100644 --- a/branch/main/openssl_privatekey_convert_module.html +++ b/branch/main/openssl_privatekey_convert_module.html @@ -228,8 +228,8 @@ see string

The attributes the resulting filesystem object 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.

+

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.

@@ -277,7 +277,7 @@ see

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

@@ -286,7 +286,7 @@ 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.

@@ -298,7 +298,7 @@ see

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.

diff --git a/branch/main/openssl_privatekey_module.html b/branch/main/openssl_privatekey_module.html index 8da23399..92748c2d 100644 --- a/branch/main/openssl_privatekey_module.html +++ b/branch/main/openssl_privatekey_module.html @@ -230,8 +230,8 @@ see string

The attributes the resulting filesystem object 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.

+

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.

@@ -338,7 +338,7 @@ see

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

@@ -347,7 +347,7 @@ 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.

@@ -359,7 +359,7 @@ see

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.

diff --git a/branch/main/openssl_publickey_module.html b/branch/main/openssl_publickey_module.html index 31d11f9b..13b13f0f 100644 --- a/branch/main/openssl_publickey_module.html +++ b/branch/main/openssl_publickey_module.html @@ -229,8 +229,8 @@ see string

The attributes the resulting filesystem object 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.

+

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.

@@ -274,7 +274,7 @@ see

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

@@ -283,7 +283,7 @@ 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.

@@ -295,7 +295,7 @@ see

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.

diff --git a/branch/main/x509_certificate_convert_module.html b/branch/main/x509_certificate_convert_module.html index 1de24567..27d8d708 100644 --- a/branch/main/x509_certificate_convert_module.html +++ b/branch/main/x509_certificate_convert_module.html @@ -216,8 +216,8 @@ To check whether it is installed, run string

The attributes the resulting filesystem object 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.

+

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.

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

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

@@ -266,7 +266,7 @@ 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.

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

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.

diff --git a/branch/main/x509_certificate_module.html b/branch/main/x509_certificate_module.html index b5b5a086..fd2caf19 100644 --- a/branch/main/x509_certificate_module.html +++ b/branch/main/x509_certificate_module.html @@ -274,8 +274,8 @@ see string

The attributes the resulting filesystem object 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.

+

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.

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

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

@@ -459,7 +459,7 @@ 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.

@@ -598,7 +598,7 @@ see

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.

diff --git a/branch/main/x509_crl_module.html b/branch/main/x509_crl_module.html index bcbf2a9a..3c474993 100644 --- a/branch/main/x509_crl_module.html +++ b/branch/main/x509_crl_module.html @@ -231,8 +231,8 @@ see string

The attributes the resulting filesystem object 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.

+

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.

@@ -302,7 +302,7 @@ see

group

string

-

Name of the group that should own the filesystem object, as would be fed to chown.

+

Name of the group that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.

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

owner

string

-

Name of the user that should own the filesystem object, as would be fed to chown.

+

Name of the user that should own the filesystem object, as would be fed to chown.

When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.

Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.