security-and-privacy/gnupg
security-and-privacy
/
gnupg
mirror of git://git.gnupg.org/gnupg.git
1
0
Fork 0
Code Releases Activity

doc: Explain LDAP keyserver parameters

This commit is contained in:
Werner Koch 2020-12-21 15:07:32 +01:00
parent 09dc59f6d4
commit 261fb98c6f
No known key found for this signature in database
GPG Key ID: E3FDFF218E45B72B
1 changed files with 20 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/dirmngr.texi
View File

@ -328,7 +328,26 @@ whether Tor is locally running or not. The check for a running Tor is
done for each new connection.
If no keyserver is explicitly configured, dirmngr will use the
built-in default of hkps://hkps.pool.sks-keyservers.net.
built-in default of @code{hkps://hkps.pool.sks-keyservers.net}.
Windows users with a keyserver running on their Active Directory
should use @code{ldap:///} for @var{name} to access this directory.
For accessing anonymous LDAP keyservers @var{name} is in general just
a @code{ldaps://ldap.example.com}. A BaseDN parameter should never be
specified. If authentication is required the value of @var{name} is
for example:
@example
keyserver ldaps://ldap.example.com/????bindname=uid=USERNAME
%2Cou=GnuPG%20Users%2Cdc=example%2Cdc=com,password=PASSWORD
@end example
Put this all on one line without any spaces and keep the '%2C' as given.
Replace USERNAME, PASSWORD, and the 'dc' parts according to the
instructions received from the LDAP administrator. Note that only
simple authentication (i.e. cleartext passwords) is supported and thus
using ldaps is strongly suggested.
@item --nameserver @var{ipaddr}
@opindex nameserver