Tickets :: Comment on [#11380] GPG keys are not fetched from the configured keyserver

* Your Email Address
* Spam protection	Enter the letters below: .__.. . ..__.. . \| \|\| \| \|\| \|\|\/\| \|__\\|___\|__\|\|__\|\| \|
Comment	> Actually there was even more wrong in this case. See my updated pull > request for a second patch which checks all fetched keyids if they > actually have a correct uid: > > > (git log) Fix: horde picks mismatching gpg-keys. > > We should only use gpg keys with an uid containing a matching email > address to encrypt mails. > > How a keyserver responds to a text search is not standardized. See > https://tools.ietf.org/html/draft-shaw-openpgp-hkp-00#page-3 > > 3.1.1.3. Text Searches > > How a keyserver handles a textual search is implementation defined. > See also the definition of the "exact" variable for a method to > give additional instructions to the server on how the search is to > be executed. > > We should therefore not rely to get the correct key, just because we > where searching for an email address. This patch removes all keys from > the candidates list, which do not contain the correct email address > between <> in the uid field. > > uid lines from the keyserver are constructed as follows: > > uid:escaped uid string:creationdate:expirationdate:flags > (s.openpgp-hkp rfc draft) > > where all pgp compatible tools that i know of use the following uid > format: > > name (comment) <email>
Attachment
Watch this ticket