mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-03 22:56:33 +02:00
dirmngr: Support new gpgNtds parameter in LDAP keyserver URLs.
* dirmngr/ldap-parse-uri.c (ldap_parse_uri): Support a new gpgNtds
extension.
* dirmngr/ks-engine-ldap.c (my_ldap_connect): Do ldap_init always with
hostname - which is NULL and thus the same if not given. Fix minor
error in error code handling.
--
Note that "gpgNtds" is per RFC-4512 case insensitive and has not yet
been officially regisetered. Thus for correctness the OID can be
used:
1.3.6.1.4.1.11591.2.5 LDAP URL extensions
1.3.6.1.4.1.11591.2.5.1 gpgNtds=1 (auth. with current user)
Note that the value must be 1; all other values won't enable AD
authentication and are resevered for future use.
This has been cherry-picked from the 2.2 branch,
commit 55f46b33df
Signed-off-by: Werner Koch <wk@gnupg.org>
This commit is contained in:
parent
3fa1fa747b
commit
ab7dc4b524
5 changed files with 40 additions and 22 deletions
14
doc/gpg.texi
14
doc/gpg.texi
|
@ -1911,13 +1911,13 @@ Use @var{name} as your keyserver. This is the server that
|
|||
will communicate with to receive keys from, send keys to, and search for
|
||||
keys on. The format of the @var{name} is a URI:
|
||||
`scheme:[//]keyservername[:port]' The scheme is the type of keyserver:
|
||||
"hkp" for the HTTP (or compatible) keyservers, "ldap" for the LDAP
|
||||
keyservers, or "mailto" for the Graff email keyserver. Note that your
|
||||
particular installation of GnuPG may have other keyserver types
|
||||
available as well. Keyserver schemes are case-insensitive. After the
|
||||
keyserver name, optional keyserver configuration options may be
|
||||
provided. These are the same as the global @option{--keyserver-options}
|
||||
from below, but apply only to this particular keyserver.
|
||||
"hkp"/"hkps" for the HTTP (or compatible) keyservers or "ldap"/"ldaps"
|
||||
for the LDAP keyservers. Note that your particular installation of
|
||||
GnuPG may have other keyserver types available as well. Keyserver
|
||||
schemes are case-insensitive. After the keyserver name, optional
|
||||
keyserver configuration options may be provided. These are the same as
|
||||
the global @option{--keyserver-options} from below, but apply only to
|
||||
this particular keyserver.
|
||||
|
||||
Most keyservers synchronize with each other, so there is generally no
|
||||
need to send keys to more than one server. The keyserver
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue