Skip to content

GitLab Next

    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Menu
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • GnuTLS GnuTLS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 242
    • Issues 242
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 17
    • Merge requests 17
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 has launched! Please visit Breaking changes in 15.0 and 15.0 Removals to see which breaking changes may impact your workflow.

  • gnutls
  • GnuTLSGnuTLS
  • Issues
  • #61
Closed
Open
Created Dec 22, 2015 by Nikos Mavrogiannopoulos@nmavOwner

max-fragment TLS extension is negotiated under DTLS but ignored for fragmenting handshake packets

(This is a copy of http://lists.gnutls.org/pipermail/gnutls-devel/2015-December/007850.html )

I am testing a development build of the BouncyCastle DTLS client against the MacPorts build of GnuTLS (gnutls-serv 3.3.19).

At first it was not connecting, the client dropping packets after the ServerHello for some reason. I eventually noticed that the client was requesting max_fragment_length extension, and the server was accepting it, agreeing on MaxFragmentLength.2^9(1). The client then appears to ignore the Certificate message as it is too large. (Without that extension, connections work fine).

See attached capture of the handshake start, noting the ServerHello with max_fragment_length=1, and the Certificate message with Fragment Length 932.

Assignee
Assign to
Time tracking