Issues

• Escape HTML entities.

  bug
  openmls/annotations#50 · Filter by author duesee opened on Jan 31, 2023

• [Annotation] Verify that the signature on the KeyPackage is valid using the public key in leaf_node.credential.

  annotationkey_package
  openmls/annotations#49 · Filter by author duesee opened on Jan 18, 2023

• [Annotation] Verify that the leaf_node of the KeyPackage is valid for a KeyPackage according to Section 7.3.

  annotationkey_package
  openmls/annotations#48 · Filter by author duesee opened on Jan 18, 2023

• [Annotation] Verify that the ciphersuite and protocol version of the KeyPackage match those in the GroupContext.

  annotationkey_package
  openmls/annotations#47 · Filter by author duesee opened on Jan 18, 2023

• [Annotation] If a client receives a KeyPackage carried within an MLSMessage object, then it MUST verify that the version field of the KeyPackage has the same value as the version field of the MLSMessage.

  annotationkey_package
  openmls/annotations#46 · Filter by author duesee opened on Jan 18, 2023

• [Annotation] A KeyPackage object with an invalid signature field MUST be considered malformed.

  annotationkey_package
  openmls/annotations#45 · Filter by author duesee opened on Jan 18, 2023

• [Annotation] Likewise, the leaf_node field MUST be valid for the ciphersuite, including both the encryption_key and signature_key fields.

  annotationkey_packageleaf_node
  openmls/annotations#44 · Filter by author duesee opened on Jan 18, 2023

• [Annotation] The value for init_key MUST be a public key for the asymmetric encryption scheme defined by cipher_suite, and it MUST be unique among the set of KeyPackages created by this client.

  annotationkey_package
  openmls/annotations#43 · Filter by author duesee opened on Jan 18, 2023

• [Annotation] KeyPackages are intended to be used only once and SHOULD NOT be reused except in the case of last resort (see Section 16.6).

  annotationkey_package
  openmls/annotations#42 · Filter by author duesee opened on Jan 18, 2023

• [Annotation] Verify that the value of leaf_node.encryption_key is different from the value of the init_key field.

  annotationkey_package
  openmls/annotations#41 · Filter by author duesee opened on Jan 17, 2023

• [Annotation] Extension included in the extensions or leaf_node.extensions fields MUST be included in the leaf_node.capabilities field.

  annotationkey_package
  openmls/annotations#40 · Filter by author duesee opened on Jan 17, 2023

• [Annotation] The field leaf_node.leaf_node_source of the LeafNode in a KeyPackage MUST be set to key_package.

  annotationkey_packageleaf_node
  openmls/annotations#39 · Filter by author duesee opened on Jan 17, 2023

• [Annotation] Proposal and extension types defined in this document are considered "default" and thus need not be listed, while any credential types the application wishes to use MUST be listed.

  annotationleaf_node
  openmls/annotations#38 · Filter by author duesee opened on Jan 17, 2023

• [ValSem / LeafNode / RequiredCapabilities] Check that leaf node supports all required capabilities.

  openmls/annotations#37 · Filter by author duesee opened on Jan 16, 2023

• [ValSem / LeafNode / Lifetime] Ensure that lifetimes are acceptable.

  validation
  openmls/annotations#36 · Filter by author duesee opened on Jan 11, 2023

• [Annotation] Each modification of LeafNode content MUST be reflected by a change in its signature.

  annotationleaf_node
  openmls/annotations#33 · Filter by author duesee opened on Jan 10, 2023
  1

• [Annotation] Applications MUST define a maximum total lifetime that is acceptable for a LeafNode, and reject any LeafNode where the total lifetime is longer than this duration.

  annotationleaf_node
  openmls/annotations#32 · Filter by author duesee opened on Jan 10, 2023

• [Annotation] Extensions that appear in the extensions field of a LeafNode MUST be included in the extensions field of the capabilities field, and the credential type used in the LeafNode MUST be included in the credentials field of the capabilities field.

  annotationcredentialleaf_node
  openmls/annotations#31 · Filter by author duesee opened on Jan 10, 2023

• [Annotation] The public key encoded in the subjectPublicKeyInfo of the end-entity certificate MUST be identical to the signature_key in the LeafNode containing this credential.

  annotationleaf_nodex509
  openmls/annotations#30 · Filter by author duesee opened on Jan 10, 2023

• [Annotation] The sender MUST include the reuse guard in the reuse_guard field of the sender data object, so that the recipient of the message can use it to compute the nonce to be used for decryption.

  annotation
  openmls/annotations#29 · Filter by author duesee opened on Jan 10, 2023

• [Annotation] To avoid this situation, the sender of a message MUST generate a fresh random four-byte "reuse guard" value and XOR it with the first four bytes of the nonce from the key schedule before using the nonce for encryption.

  annotation
  openmls/annotations#28 · Filter by author duesee opened on Jan 10, 2023

• [Annotation] A receiver MUST verify that there are no non-zero bytes in the padding field, and if this check fails, the enclosing PrivateMessage MUST be rejected as malformed.

  annotationcodec
  openmls/annotations#27 · Filter by author duesee opened on Jan 10, 2023

• [Annotation] The padding field MUST be filled with all zero bytes.

  annotationcodec
  openmls/annotations#26 · Filter by author duesee opened on Jan 10, 2023

• [Annotation] When decoding, a presence octet with a value other than 0 or 1 MUST be rejected as malformed.

  annotationcodec
  openmls/annotations#25 · Filter by author duesee opened on Jan 10, 2023

• feat: Add a link to the rendered document.

  enhancement
  openmls/annotations#23 · Filter by author duesee opened on Jan 10, 2023