Introduce a per-user certificate inventory and migrate legacy PFX storage
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start from SignEngineHandler, where the single signature.pfx filename is used, and trace how certificate creation, lookup and deletion assume one certificate per account. The work is a schema and storage design plus an idempotent migration, so read the existing storage code before proposing a data contract. Done means the acceptance criteria hold: existing PFX files are discoverable without reissuance, repeated migration is a no-op, accounts cannot read each other's material, and legacy signing still works.
由索引模型根据 Issue 内容生成。
描述
Goal
Introduce a persistent inventory capable of representing multiple signing certificates per Nextcloud account, while preserving all existing reusable PFX certificates.
Current state
SignEngineHandler uses a single signature.pfx filename. Certificate creation, lookup and deletion assume one reusable certificate per account.
Scope
- Introduce individual certificate records with stable identifiers and strict account ownership.
- Store certificate metadata separately from protected PKCS#12 material.
- Include issuer reference, subject, serial number, SHA-256 fingerprint, validity period, source, status and optional organizational context where applicable.
- Support multiple inventory records for the same user without requiring multiple CAs.
- Define a storage reference that does not expose private certificate material.
- Migrate existing
signature.pfxfiles idempotently, preserving their contents and password protection. - Retain compatibility with existing certificate lookup and signing paths during migration.
- Establish backend contracts for later certificate-specific operations and UI development.
- Avoid assuming that every certificate is LibreSign-issued or belongs to a Nextcloud group.
Acceptance criteria
- Existing certificates are discoverable through the inventory without reissuance.
- Two certificates belonging to one account have distinct records and protected storage references.
- An account cannot retrieve another account's certificate material.
- Repeated migration does not create duplicate records, overwrite PFX files or revoke certificates.
- Listing certificate metadata does not require reading every PFX.
- Missing files and inconsistent legacy records produce safe, recoverable behavior.
- Tests cover ownership, migration, duplicate detection, storage failures and legacy signing compatibility.
- The backend data contract and migration behavior are documented.
Out of scope
The complete CRUD UI, policy-based CA selection, certificate delegation, cloud certificates and interactive signing selection.
- 主要语言
- PHP
- 星标
- 844
- 派生
- 176
- 平均合并
- 13 小时 46 分钟
- 30 天内合并 PR
- 299
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
LibreSign/libresign 的其他 Issue
-
backend enhancement good first issue php
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
OpenSSL engine: leaf certificates get O=Internet Widgits Pty Ltd, ST=Some-State from system openssl.cnf可能已有人在做 @vitormattos 于 2 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
LibreSign/libresign#9366 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 83/100
LibreSign/libresign#9007 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
good first issue
难度 2/5 1-3 小时 新手友好度 78/100
LibreSign/libresign#8284 · 5 条评论 ·
维护者通常 1 天内回复
-
backend enhancement php
难度 5/5 一周以上 新手友好度 12/100
维护者通常 1 天内回复
查看 LibreSign/libresign 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 89/100
backdrop-contrib/commerce#65 ·
-
enhancement good first issue help wanted
难度 2/5 1-3 小时 新手友好度 78/100
Evalogical-Inc/devReady#66 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
mollie/PrestaShop#1627 ·
维护者通常 5 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
FriendsOfFlarum/follow-tags#118 ·
-
WebP — PHP 8.5 deprecation "Using null as an array offset" in url_to_path() for relative image URLs未关闭✨️ai-candidate effort: [XS] module: webp cache priority: low type: bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复