Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • 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 18
    • Merge requests 18
  • 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
  • gnutls
  • GnuTLSGnuTLS
  • Issues
  • #881
Closed
Open
Created Dec 18, 2019 by Dimitri John Ledkov@xnoxContributor

gnutls serv / gnutls_certificate_set_x509_key_file do not check certificate against policy

gnutls serv loads keyfile & cert, but doesn't bother to check if it should trust it or if it is acceptable as per policy.

For example, one can start gnutls serv with 512 RSA keys in the cert chain, even if no sane client will trust to connect to it.

Some checks are performed e.g. gnutls_check_key_cert_match, but it should also check if the cert meets the minimum profile security standard w.r.t. algos / key sizes / hashes / etc. Such that, for example, daemons fail to start with bogus certs instead of waiting for clients to fail to establish a connection.

Assignee
Assign to
Time tracking