161
edits
Line 60: | Line 60: | ||
I think it will be better to use the same keyring and homedir like GnuPG us it. | I think it will be better to use the same keyring and homedir like GnuPG us it. | ||
= XEP Review = | |||
== XEP-0373: OpenPGP for XMPP == | |||
=== Date of a public key === | |||
In Section [https://xmpp.org/extensions/xep-0373.html#announcing-pubkey The OpenPGP Public-Key Data Node] Example 3 is a date attribute in the pubkey tag. | |||
In Section [https://xmpp.org/extensions/xep-0373.html#discover-pubkey Requesting Public Keys] Example 8. is no date attribute in the response. | |||
The Text "Note that the result may contain multiple pubkey elements. Only the public keys found in the most recent item MUST be used." may reference to the date attribute. | |||
"Requesters may want to limit the results to the most recent item using the 'max_items' attribute set to '1'." Does this constrain guarantee that the response is always the most recent item? | |||
I think there is no need to have more than one version of a public key on the PEP. Within OpenPGP (local Keyring, Keyserver, Web Key Directory, doesn't support a version of public key AFAIK). | |||
The user should be able to update the item with his current version of the key. | |||
= Links = | = Links = |
edits