Dear Debian maintainer,
On Sunday, May 12, 2013, I notified you of the beginning of a review process
concerning debconf templates for nss-pam-ldapd.
The debian-l10n-english contributors have now reviewed these templates,
and the final proposed changes are attached to this update to the
original bug report.
Please review the suggested changes, and if you have any
objections, let me know in the next 3 days.
However, please try to avoid uploading nss-pam-ldapd with these changes
right now.
The second phase of this process will begin on Sunday, June 09, 2013, when I
will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Sunday, June 30, 2013. Please avoid uploading a package with fixed or
changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around Monday, July 01, 2013, I will contact you again and will send a final
patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
--
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-engl...@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
Template: nslcd/ldap-uris
Type: string
_Description: LDAP server URI:
Please enter the Uniform Resource Identifier of the LDAP server. The format
is ldap://hostname_or_IP_address:port/. Alternatively, ldaps:// or
ldapi:// can be used. The port number is optional.
.
When using an ldap or ldaps scheme it is recommended to use an IP address to
avoid failures when domain name services are unavailable.
.
Multiple URIs can be separated by spaces.
Template: nslcd/ldap-base
Type: string
_Description: LDAP server search base:
Please enter the distinguished name of the LDAP search base. Many sites use
the components of their domain names for this purpose. For example, the
domain example.net would use dc=example,dc=net as the distinguished name
of the search base.
Template: nslcd/ldap-auth-type
Type: select
__Choices: none, simple, SASL
_Description: LDAP authentication to use:
Please choose what type of authentication the LDAP database should
require (if any):
.
* none: no authentication;
* simple: simple bind DN and password authentication;
* SASL: any Simple Authentication and Security Layer mechanism.
Template: nslcd/ldap-binddn
Type: string
_Description: LDAP database user:
Please enter the name of the account that will be used to log in to the LDAP
database. This value should be specified as a DN (distinguished name).
Template: nslcd/ldap-bindpw
Type: password
_Description: LDAP user password:
Please enter the password that will be used to log in to the LDAP database.
Template: nslcd/ldap-sasl-mech
Type: select
Choices: auto, LOGIN, PLAIN, NTLM, CRAM-MD5, DIGEST-MD5, SCRAM, GSSAPI, SKEY,
OTP, EXTERNAL
_Description: SASL mechanism to use:
Please choose the SASL mechanism that will be used to authenticate to the LDAP
database:
.
* auto: auto-negotiation;
* LOGIN: deprecated in favor of PLAIN;
* PLAIN: simple cleartext password mechanism;
* NTLM: NT LAN Manager authentication mechanism;
* CRAM-MD5: challenge-response scheme based on HMAC-MD5;
* DIGEST-MD5: HTTP Digest compatible challenge-response scheme;
* SCRAM: salted challenge-response mechanism;
* GSSAPI: used for Kerberos;
* SKEY: S/KEY mechanism (obsoleted by OTP);
* OTP: One Time Password mechanism;
* EXTERNAL: authentication is implicit in the context.
Template: nslcd/ldap-sasl-realm
Type: string
_Description: SASL realm:
Please enter the SASL realm that will be used to authenticate to the LDAP
database.
.
The realm is appended to authentication and authorization identities.
.
For GSSAPI, this can be left blank to use information from the Kerberos
credentials cache.
Template: nslcd/ldap-sasl-authcid
Type: string
_Description: SASL authentication identity:
Please enter the SASL authentication identity that will be used to
authenticate to
the LDAP database.
.
This is the login used in LOGIN, PLAIN, CRAM-MD5, and DIGEST-MD5 mechanisms.
Template:
