Difference between revisions of "Tech pages/OX"

Jump to navigation Jump to search
968 bytes added ,  18:10, 5 June 2020
rpad
m
(rpad)
Line 69: Line 69:
In Section [https://xmpp.org/extensions/xep-0373.html#discover-pubkey  Requesting Public Keys]  Example 8. is no date attribute in the response.
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.
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.
<blockquote>
"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?
"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?
 
</blockquote>
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).
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.
The user should be able to update the item with his current version of the key.


== XEP-0420: Stanza Content Encryption ==
== XEP-0420: Stanza Content Encryption ==
=== rpad ===
In Section [https://xmpp.org/extensions/xep-0420.html#affix_elements Affix Elements] rpad is defined like
<blockquote>
"Prevent known ciphertext and message length correlation attacks. The content of this element is a randomly generated sequence of base64 characters of random length between 0 and 200 characters. TODO: sane boundaries?"
</blockquote>
In Example 1 is rpad
  <rpad>C1DHN9HK-9A25tSmwK4hU!Jji9%GKYK^syIlHJT9TnI4</rpad>
This is not the The RFC-4648 - The Base 64 Alphabet defined in: https://tools.ietf.org/html/rfc4648#section-4
<pre>
static const char rfc_4648_base64_alphabet[] = {
'A','B','C','D','E','F','G','H','I','J','K','L','M','N','O','P',
'Q','R','S','T','V','V','W','X','Y','Z','a','b','c','d','e','f',
'g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v',
'w','x','y','z','0','1','2','3','4','5','6','7','8','9','+','/',
};
static const char* rfc_4648_base64_pad = '=';
</pre>


= Links =
= Links =
161

edits

Navigation menu