Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Different certinfo output for versions from `brew` and released binary

Open
  • Is something wrong?
#1,307 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cryptography, security

Research direction

Start by reproducing cfssl certinfo -csr some.csr.pem with the Homebrew and release 1.6.4 binaries on the reported macOS environment, then compare their Go runtimes and certificate parsing behavior. Trace the certinfo output path to determine why the Homebrew result has an empty PublicKey.Curve.Name; done means the outputs consistently report the curve information.

Written by the indexing model from the issue text.

Description

Problem:

  • Two different output for certinfo using cfssl installed from brew and downloaded from Release page on GitHub.
  • Public.Curve.Name part of the output is empty in case cfssl is installed using brew.

Tested environment:

  • M1 Pro Macbook,
  • OS version - Ventura 13.3.1 (a)

Examples of results:

Result for the version installed via brew 
>>> cfssl certinfo -csr some.csr.pem
{
  "Raw": <redacted>,
  "RawTBSCertificateRequest": <redacted>,
  "RawSubjectPublicKeyInfo": <redacted>,
  "RawSubject": <redacted>,
  "Version": 0,
  "Signature": <redacted>,
  "SignatureAlgorithm": 10,
  "PublicKeyAlgorithm": 3,
  "PublicKey": {
    "Curve": {},
    "X":<some value>,
    "Y": <some value>
  },
  "Subject": {
    "Country": null,
    "Organization": null,
    "OrganizationalUnit": null,
    "Locality": null,
    "Province": null,
    "StreetAddress": null,
    "PostalCode": null,
    "SerialNumber": "",
    "CommonName": <redacted>,
    "Names": [
      {
        "Type": [
          2,
          5,
          4,
          3
        ],
        "Value": <redacted>
      }
    ],
    "ExtraNames": null
  },
  "Attributes": null,
  "Extensions": null,
  "ExtraExtensions": null,
  "DNSNames": null,
  "EmailAddresses": null,
  "IPAddresses": null,
  "URIs": null
}

>>> cfssl version
Version: 1.6.4
Runtime: go1.20.3

>>> brew --version
Homebrew 4.0.21
Homebrew/homebrew-core (git revision 9d0b7361d; last commit 2023-06-06)
Result for the version downloaded via curl from release page for darwin arm 64, version 1.6.4 
>>> ./cfssl_1.6.4_darwin_arm64 certinfo -csr some.csr.pem
{
  "Raw": <redacted>,
  "RawTBSCertificateRequest": <redacted>,
  "RawSubjectPublicKeyInfo": <redacted>,
  "RawSubject": <redacted>,
  "Version": 0,
  "Signature": <redacted>,
  "SignatureAlgorithm": 10,
  "PublicKeyAlgorithm": 3,
  "PublicKey": {
    "Curve": {
      "P": <some value>,
      "N": <some value>,
      "B": <some value>,
      "Gx": <some value>,
      "Gy": <some value>,
      "BitSize": 256,
      "Name": "P-256"
    },
    "X": <some value>,
    "Y": <some value>
  },
  "Subject": {
    "Country": null,
    "Organization": null,
    "OrganizationalUnit": null,
    "Locality": null,
    "Province": null,
    "StreetAddress": null,
    "PostalCode": null,
    "SerialNumber": "",
    "CommonName": <redacted>,
    "Names": [
      {
        "Type": [
          2,
          5,
          4,
          3
        ],
        "Value": <redacted>
      }
    ],
    "ExtraNames": null
  },
  "Attributes": null,
  "Extensions": null,
  "ExtraExtensions": null,
  "DNSNames": null,
  "EmailAddresses": null,
  "IPAddresses": null,
  "URIs": null
}
>>> ./cfssl_1.6.4_darwin_arm64 version
Version: 1.6.4
Runtime: go1.18

I can see that Runtime version is different, but not sure if it matters in this situation.
Also I tried to find a template for issue that is mentioned in contributing guidelines, but couldn't find it. So my apologies in advance.

Dominant language
Go
Stars
9.5k
Forks
1.2k
Avg merge
12h 48m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudflare/cfssl

All issues in cloudflare/cfssl

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.