Project

General

Profile

Actions
Copy link

Task #18

closed

Make authority objects capable of issuing certificates and CRLs

Added by Felix Tiede almost 14 years ago. Updated almost 14 years ago.

Status:
Completed
Priority:
Normal
Assignee:
Felix Tiede
Target version:
0.4.0
Start date:
12/29/2011
Due date:
12/31/2011
% Done:

100%

Estimated time:
(Total: 37:00 h)

Description

Authority objects are currently only capable of storing data regarding their own settings. They must also be able to actually sign certificate requests as well as issuing CRLs based on the certificates information stored in the database.

Subtasks 8 (0 open — 8 closed)

Bug #19: Support self-signing of requestsResolvedFelix Tiede12/29/201112/29/2011

Actions
Bug #20: Provide a method to create a certificate from a request using an authority's certificate as issuerClosedFelix Tiede12/29/201112/29/2011

Actions
Bug #21: Generate a CRL from stored certificate data using authority's certificate as issuerClosedFelix Tiede12/29/201112/30/2011

Actions
Bug #22: Support locking/unlocking of authorities and/or their private keysClosedFelix Tiede12/29/201112/31/2011

Actions
Bug #23: Add a flag defining if an authority's private key is actually a key or path to the key.ClosedFelix Tiede12/29/201112/29/2011

Actions
Bug #24: Include private key management facility into authoritiesClosedFelix Tiede12/29/201112/31/2011

Actions
Feature #25: Add icon to show private key status of authorityClosedFelix Tiede12/30/201112/31/2011

Actions
Task #26: Signal/Slot system requires objects to inherit from QObject - copy constructors and assignment operators requiredClosedFelix Tiede12/30/201112/31/2011

Actions
Actions
Copy link

Also available in: Atom PDF