Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
K
k3s
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Jacklull
  • k3s
  • Repository

Switch branch/tag
  • k3s
  • pkg
  • authenticator
  • passwordfile
  • passwordfile.go
Find file
BlameHistoryPermalink
  • Brad Davidson's avatar
    Consistently use constant-time comparison of password hashes · 239021e7
    Brad Davidson authored May 08, 2023
    As per https://github.com/golang/go/issues/47001 even subtle.ConstantTimeCompare should never be used with variable-length inputs, as it will return 0 if the lengths do not match. Switch to consistently using constant-time comparisons of hashes for password checks to avoid any possible side-channel leaks that could be combined with other vectors to discover password lengths.
    Signed-off-by: 's avatarBrad Davidson <brad.davidson@rancher.com>
    239021e7
passwordfile.go 2.78 KB
EditWeb IDE

Replace passwordfile.go

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.