Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary SSSD GPL-3.0 0 0 0 0 0 0 0
sssd GPL-3.0 0 0 0 0 60 0 0
sssd-1-16 GPL-3.0 0 0 0 0 70 0 0
SSSD-2-7 GPL-3.0 0 0 0 0 39 0 0
SSSD-2-8 GPL-3.0 0 0 0 0 49 0 0
SSSD-2-9 GPL-3.0 0 0 0 0 59 0 0
sssd-manpage GPL-3.0 0 0 0 0 535 0 3
sssd-manpages-1-16 GPL-3.0 0 0 0 0 732 0 0

Overview

Project website sssd.io
Instructions for translators

Mailing list for translators: <<trans@lists.fedoraproject.org>
Project maintainers User avatar pbrezina User avatar atikhonov
Translation license GPL-3.0 SSSD sssd-manpages-1-16 SSSD-2-8 sssd sssd-manpage SSSD-2-9 sssd-1-16 SSSD-2-7
2 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 8,667 97,601 704,837
Translated 100% 8,667 100% 97,601 100% 704,837
Needs editing 0% 0 0% 0 0% 0
Read-only 99% 8,663 99% 97,596 99% 704,793
Failing checks 17% 1,544 16% 16,193 19% 139,612
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

229 changes 0 changes 626 changes 62 changes 49 changes 716 changes 23 changes 1 change 0 changes 0 changes 12 changes 26 changes 703 changes 0 changes 3 changes 0 changes 128 changes 12 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

97,601
Hosted words
8,667
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
+100%
User avatar None

Resource updated

  1. SSSD
  2. SSSD-2-9
  3. English
The "po/sssd.pot" file was changed. 2 months ago
User avatar atikhonov

Resource updated

  1. SSSD
  2. SSSD-2-9
  3. English
The "po/sssd.pot" file was changed. 4 months ago
User avatar atikhonov

Resource updated

  1. SSSD
  2. sssd-manpage
  3. English
The "src/man/po/sssd-docs.pot" file was changed. 4 months ago
User avatar None

String updated in the repository

  1. SSSD
  2. sssd-manpage
  3. English
[sssd]
services = nss, pam, sudo
domains = EXAMPLE

[domain/EXAMPLE]
id_provider = ldap
sudo_provider = ldap
ldap_uri = ldap://example.com
ldap_sudo_search_base = ou=sudoers,dc=example,dc=com
[sssd]
services = nss, pam, sudo
domains = EXAMPLE

[domain/EXAMPLE]
id_provider = ldap
sudo_provider = ldap
ldap_uri = ldap://example.com
ldap_sudo_search_base = ou=sudoers,dc=example,dc=com
4 months ago
User avatar None

String updated in the repository

  1. SSSD
  2. sssd-manpage
  3. English
Note that <emphasis>dyndns_update_per_family</emphasis> parameter does not apply for PTR record updates. Those updates are always sent separately.
Note that <emphasis>dyndns_update_per_family</emphasis> parameter does not apply for PTR record updates. Those updates are always sent separately.
4 months ago
User avatar None

String updated in the repository

  1. SSSD
  2. sssd-manpage
  3. English
Specifies that the id_provider connection must also use <systemitem class="protocol">tls</systemitem> to protect the channel. <emphasis>true</emphasis> is strongly recommended for security reasons.
Specifies that the id_provider connection must also use <systemitem class="protocol">tls</systemitem> to protect the channel. <emphasis>true</emphasis> is strongly recommended for security reasons.
4 months ago
User avatar None

String updated in the repository

  1. SSSD
  2. sssd-manpage
  3. English
LDAP back end supports id, auth, access and chpass providers. If you want to authenticate against an LDAP server either TLS/SSL or LDAPS is required. <command>sssd</command> <emphasis>does not</emphasis> support authentication over an unencrypted channel. Even if the LDAP server is used only as an identity provider, an encrypted channel is strongly recommended. Please refer to the <quote>ldap_access_filter</quote> config option for more information about using LDAP as an access provider.
LDAP back end supports id, auth, access and chpass providers. If you want to authenticate against an LDAP server either TLS/SSL or LDAPS is required. <command>sssd</command> <emphasis>does not</emphasis> support authentication over an unencrypted channel. Even if the LDAP server is used only as an identity provider, an encrypted channel is strongly recommended. Please refer to the <quote>ldap_access_filter</quote> config option for more information about using LDAP as an access provider.
4 months ago
User avatar None

String updated in the repository

  1. SSSD
  2. sssd-manpage
  3. English
[sssd]
domains = LDAP
services = nss, pam

[nss]
filter_groups = root
filter_users = root

[pam]

[domain/LDAP]
id_provider = ldap
ldap_uri = ldap://ldap.example.com
ldap_search_base = dc=example,dc=com

auth_provider = krb5
krb5_server = kerberos.example.com
krb5_realm = EXAMPLE.COM
cache_credentials = true

min_id = 10000
max_id = 20000
enumerate = False
[sssd]
domains = LDAP
services = nss, pam

[nss]
filter_groups = root
filter_users = root

[pam]

[domain/LDAP]
id_provider = ldap
ldap_uri = ldap://ldap.example.com
ldap_search_base = dc=example,dc=com

auth_provider = krb5
krb5_server = kerberos.example.com
krb5_realm = EXAMPLE.COM
cache_credentials = true

min_id = 10000
max_id = 20000
enumerate = False
4 months ago
User avatar None

String updated in the repository

  1. SSSD
  2. sssd-manpage
  3. English
Default: not set by default, you have to take an existing pam configuration or create a new one and add the service name here. As an alternative you can enable local authentication with the local_auth_policy option.
Default: not set by default, you have to take an existing pam configuration or create a new one and add the service name here. As an alternative you can enable local authentication with the local_auth_policy option.
4 months ago
User avatar None

String updated in the repository

  1. SSSD
  2. sssd-manpage
  3. English
Please note that if local Smartcard authentication is enabled and a Smartcard is present, Smartcard authentication will be preferred over the authentication methods supported by the backend. I.e. there will be a PIN prompt instead of e.g. a password prompt.
Please note that if local Smartcard authentication is enabled and a Smartcard is present, Smartcard authentication will be preferred over the authentication methods supported by the backend. I.e. there will be a PIN prompt instead of e.g. a password prompt.
4 months ago
Browse all changes for this language