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

Verify RSA-2048 in certificates generated by the real CFSSL engine

Open
  • Is something wrong?
#9,173 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
53/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
php
Domain
backend, security, testing

Research direction

Start with the existing LibreSign test infrastructure and the certificate tests referenced by #8941, #8983, and #9170. Find how those tests use OpenSSL and CFSSL, then determine how to invoke real CFSSL issuance without adding an implicit dependency to regular PHPUnit suites. Done means a regression test inspects a newly issued leaf certificate and fails unless its public key is RSA-2048, with PHPUnit and Behat still passing.

Written by the indexing model from the issue text.

Description

backend php

Context

Issue #8941 introduced regression coverage for the LibreSign certificate profiles using OpenSSL and CFSSL. PR #8983 covers important certificate properties, and PR #9170 verifies RSA-2048 against an existing CFSSL certificate fixture.

The fixture test does not prove that a certificate newly generated by the real CFSSL engine still uses RSA-2048.

Goal

Add an automated regression test that checks the RSA-2048 public key in a leaf certificate issued by the real CFSSL engine.

Acceptance criteria

  • Generate a signing certificate using the real CFSSL engine.
  • Inspect the issued certificate, not the request or the CFSSL configuration.
  • Verify that the public key algorithm is RSA.
  • Verify that the public key size is 2048 bits.
  • Ensure the test fails if CFSSL issues a certificate with a different algorithm or key size.
  • Keep the existing PHPUnit and Behat suites passing.

Implementation notes

Prefer the existing LibreSign test infrastructure. Investigate how to test actual CFSSL issuance without adding an implicit dependency to the regular PHPUnit suites. Do not introduce standalone test scripts, unnecessary workflow changes, new Behat steps or changes to the production API solely for testing.

Out of scope

Changing certificate algorithms, CFSSL configuration, certificate-engine production code, or adding ML-DSA support.

Related

  • #8941
  • #8983
  • #9170
Dominant language
PHP
Stars
835
Forks
167
Avg merge
1d 4h
Merged PRs (30d)
388

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 LibreSign/libresign

All issues in LibreSign/libresign

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.