Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
duesee opened this issue Jan 10, 2023 · 0 comments

Comments

@duesee
Copy link
Collaborator

duesee commented Jan 10, 2023

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
{
  "@context": "http://www.w3.org/ns/anno.jsonld",
  "type": "Annotation",
  "body": [],
  "target": {
    "selector": [
      {
        "type": "TextQuoteSelector",
        "exact": "To avoid this situation, the sender of a message MUST generate a\n   fresh random four-byte \"reuse guard\" value and XOR it with the first\n   four bytes of the nonce from the key schedule before using the nonce\n   for encryption."
      },
      {
        "type": "TextPositionSelector",
        "start": 92836,
        "end": 93063
      }
    ]
  },
  "id": "#12f90ea8-02fd-43d9-8f66-5ce3aa33e656",
  "meta": null
}
@duesee duesee changed the title [Validation] 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] 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. Jan 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant