Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
GnuTLS
GnuTLS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 214
    • Issues 214
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 12
    • Merge Requests 12
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gnutls
  • GnuTLSGnuTLS
  • Issues
  • #717

Closed
Open
Opened Feb 26, 2019 by Andreas Schneider@cryptomilkContributor

Document that the returned size by gnutls_cipher_get_iv_size() might not be the correct size for the nonce

In case of AES-CCM 12 is returned, which is in most cases wrong.

The RFC states:

  1. A nonce N of 15-L octets. Within the scope of any encryption key K, the nonce value MUST be unique. That is, the set of nonce values used with any given key MUST NOT contain any duplicate values. Using the same nonce for two different messages encrypted with the same key destroys the security properties of this mode.

Valid values of L range between 2 octets and 8 octets (the value L=1 is reserved).

So the documentation of the function should tell the user to check the RFC and implementation if the size is fixed or needs to be calculated differently!

Assignee
Assign to
Release of GnuTLS 3.6.7
Milestone
Release of GnuTLS 3.6.7 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gnutls/gnutls#717