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
  • M m2crypto
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 9
    • Merge requests 9
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • m2crypto
  • m2crypto
  • Issues
  • #85
Closed
Open
Created Dec 02, 2015 by Matěj Cepl@mceplOwner

Certificate fingerprint seems to have left-padding zeroes removed

(originally filed as https://github.com/martinpaljak/M2Crypto/issues/38)

I'm having an issue right now where I have an original fingerprint calculated using:

fingerprint = cert.get_fingerprint(md='sha1').lower()

However, I later calculate it myself during certificate-based authentication. I just ran into a situation where a certificate wasn't found because the M2Crypto version had a leading zero that was removed.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking