mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-02 22:46:30 +02:00
Try a DNS-SD lookup to find a domain-specific LDAP server before
resorting to keys.{domain}.
This commit is contained in:
parent
830dae2873
commit
ab9a918bc2
4 changed files with 63 additions and 15 deletions
|
@ -1,3 +1,8 @@
|
|||
2009-07-23 David Shaw <dshaw@jabberwocky.com>
|
||||
|
||||
* gpg.texi (GPG Configuration Options): LDAP uses DNS-SD to locate
|
||||
a server before falling back to keys.{domain}.
|
||||
|
||||
2009-07-23 Werner Koch <wk@g10code.com>
|
||||
|
||||
* help.txt (gpgsm.crl-problem): New.
|
||||
|
|
|
@ -1376,8 +1376,9 @@ Locate a key using DNS CERT, as specified in rfc4398.
|
|||
Locate a key using DNS PKA.
|
||||
|
||||
@item ldap
|
||||
Locate a key using the PGP Universal method of checking
|
||||
@samp{ldap://keys.(thedomain)}.
|
||||
Using DNS Service Discovery, check the domain in question for any LDAP
|
||||
keyservers to use. If this fails, attempt to locate the key using the
|
||||
PGP Universal method of checking @samp{ldap://keys.(thedomain)}.
|
||||
|
||||
@item keyserver
|
||||
Locate a key using whatever keyserver is defined using the
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue