Issues

Escape HTML entities.

bug

#50

· duesee opened

on Jan 31, 2023

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

annotation

key_package

#49

· 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.

annotation

key_package

#48

· duesee opened

on Jan 18, 2023

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

annotation

key_package

#47

· 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.

annotation

key_package

#46

· duesee opened

on Jan 18, 2023

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

annotation

key_package

#45

· 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.

annotation

key_package

leaf_node

#44

· 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.

annotation

key_package

#43

· 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).

annotation

key_package

#42

· 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.

annotation

key_package

#41

· 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.

annotation

key_package

#40

· 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.

annotation

key_package

leaf_node

#39

· duesee opened

on Jan 17, 2023

Navigation Menu

Uh oh!

All issues

Escape HTML entities.

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

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

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

[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.

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

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

[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.

[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).

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

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

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

Uh oh!

Search results