Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #22205

Closed
Open
Created May 09, 2017 by Yawning Angel@yawning

Figure out how to fix `crypto/tls`.

Most of the Go crypto isn't constant time. I'm not sure if this matters for the install/version check/update and validation mechanisms, but if there is an easy way to fix this problem, it would be the sensible thing to do.

The status as of today is:

  • RSA - Vartime.
  • ECC - X25519/P-224/P-256 constant time.
  • AES - Vartime unless there is AES-NI.
  • GHASH - Vartime unless there is PCLMULQDQ (AES-NI).
  • Poly1305/ChaCha20 - Constant time.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking