Introduce a CA registry with stable issuer identity and legacy compatibility

オープン
  • 何か問題がありますか？
#9,475 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
php
領域
backend, security

調査の方向性

The payload names no files, classes or tests, so start by finding where the active CA's configuration and identifiers are read during certificate issuance and CRL generation. Map the legacy instanceId, generation and engineType values to the proposed registry record. Done means a documented registry contract, legacy CA representable without key or certificate changes, and tests for isolation, identity collisions and invalid issuer lookup. This is design-heavy, so confirm scope with maintainers first.

索引モデルが issue の本文から書いたものです。

説明

backend enhancement php

Goal

Establish the backend registry and identity contract needed to manage multiple certificate authorities in one LibreSign installation.

Current state

The active CA is represented by application-level configuration and identifiers used throughout certificate issuance and CRL services.

Scope

  • Define a persistent CA record with an opaque public issuer identifier.
  • Represent CA identity, engine type, generation, lifecycle state and protected storage references.
  • Preserve the existing installation's CA without regeneration or certificate reissuance.
  • Support more than one registered CA, while leaving policy-based selection and administration UI for subsequent work.
  • Define how organizational contexts may reference a CA without using the Nextcloud group ID as its cryptographic identity.
  • Establish the identifier contracts needed by issuance, certificate inventory, revocation and CRL distribution.
  • Keep historical instanceId, generation and engineType information available for compatibility.
  • Define and verify the issuer-scoped identity of certificates, including cases where different issuers use the same serial number.
  • Establish backend ownership and authorization boundaries for privileged CA operations.

Acceptance criteria

  • Legacy CA configuration can be represented in the registry without changing its keys or issued certificates.
  • Multiple CA records have stable, unambiguous issuer identifiers.
  • A CA can be referenced independently of a group's name or lifecycle.
  • Missing or unauthorized issuer references fail safely.
  • Tests cover registry isolation, legacy compatibility, identity collisions and invalid issuer lookup.
  • Existing CRL URLs and certificate validation behavior remain unchanged.
  • The CA registry contract is documented for subsequent implementation.

Out of scope

New CRL routes, complete multiple-CA issuance, group administration UI, delegated CA creation and changes to signer certificate subject policies.

Handoff

Review the multi-CA epic's remaining implementation requirements against the registry contract before opening detailed CRL, provisioning and policy-selection issues.

主要言語
PHP
スター
844
フォーク
176
平均マージ
13時間 46分
マージ済み PR（30日）
299

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

LibreSign/libresign のほかの issue

LibreSign/libresign の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。