Sometimes a key that was uploaded and published on the PGP Global Directory cannot be found over the LDAP or HTTP protocols.
A key might be published i.e. only via LDAP or only via HTTP on one server but not on the other one.
The key cannot be deleted and a new key cannot be uploaded.
The issue might be caused by clustering issues on the PGP Global Directory.
You can verify if the key is found on the single cluster nodes keyserver1.pgp.com and keyserver2.pgp.com.
Use for example PGP Desktop GUI or "ldapsearch" commandline to verify if the key is available via LDAP on any of the servers.
# ldapsearch -x -H "ldap://keyserver1.pgp.com:389" -b 'o=PGP keys' -s subtree "(pgpUserIDfirstname.lastname@example.org*)"
# ldapsearch -x -H "ldap://keyserver2.pgp.com:389" -b 'o=PGP keys' -s subtree "(pgpUserIDemail@example.com*)"
Use for example a browser or "wget" to verify if the key is available via HTTP on any of the servers.
# wget http://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x1234567890ABCDEF
# wget http://keyserver2.pgp.com/vkd/DownloadKey.event?keyid=0x1234567890ABCDEF
Please contact PGP Technical Support to have the affected key removed from the PGP Global Directory. After the key is deleted, the key can be re-uploaded to the PGP Global Directory.
Login to Subscribe
Please login to set up your
For security reasons, your link to this document has expired. Please click on the attachment link to access this file.
The attachment that you are looking for no longer exists.
There has been an issue retrieving your attachment. Please try again.
Get support for your product, with downloads, knowledge base articles, documentation, and more.
Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments.
Submit a suspected infected file to Symantec.
Report a suspected erroneous detection (false positive).
Set default language
Do you wish to save this as your future site?