View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000407 | Main CAcert Website | account administration | public | 2007-02-04 00:10 | 2013-05-01 01:08 |
Reporter | dlehman | Assigned To | Uli60 | ||
Priority | low | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Platform | Main CAcert Website | OS | N/A | OS Version | stable |
Summary | 0000407: Need to deal with passing away users | ||||
Description | We'll need to deal with users passing away We could add : - a death flag when someone reports a user to be passed away. Each logging to the account will be logged and reported to the support@ - a DOPA field (Date of Passing Away) when CAcert has gotten a Death Certificate copy - a mean for the admin to revoke the user certificates as/if stated in the users last wills. | ||||
Additional Information | Revocation of certificates after death may lead to some data,encrypted by that cert, to be unreadable. This may be a legal issue in some countries. Perhaps a flag notating the death of the user and preventing the user's account from issuing any more certificates. | ||||
Tags | No tags attached. | ||||
Reviewed by | |||||
Test Instructions | |||||
|
What about users that haven't passed away but stated that they wanted their certificates to be revoked (etc.) in their Living Will? |
|
We need proper policy on the subject, then code that follows the policy. Please refer to the cacert-policy mailing list. |
|
handled in Software Assessment telco 2013-01-22 https://wiki.cacert.org/Software/Assessment/20130122-S-A-MiniTOP * [[https://bugs.cacert.org/view.php?id=407|bug 0000407]] deceased members case (orig bug report date 2007, Policies not in effect, later replaced by CCA, DRP arbitration / support procedures) problem handled under arbitration general procedure via Support/Arbitration/Support Emergency Arbitration case -> Delete Account procedure under Arbitration no software issue. bug#407 closed |
|
fixed under arbitration procedure |
Date Modified | Username | Field | Change |
---|---|---|---|
2007-02-04 00:10 | homer | New Issue | |
2007-02-04 00:15 | homer | Assigned To | => Sourcerer |
2007-02-04 00:15 | homer | Status | new => confirmed |
2007-04-30 21:34 | dlehman | Reporter | homer => dlehman |
2007-04-30 21:34 | dlehman | Status | confirmed => needs feedback |
2007-04-30 21:34 | dlehman | Additional Information Updated | |
2007-09-02 19:24 | jonathanyu | Note Added: 0000888 | |
2007-10-24 04:18 | evaldo | Note Added: 0000898 | |
2007-10-24 04:18 | evaldo | Priority | normal => low |
2007-10-24 04:18 | evaldo | Status | needs feedback => confirmed |
2007-10-24 04:18 | evaldo | Resolution | open => suspended |
2007-10-24 04:19 | evaldo | Assigned To | Sourcerer => |
2013-01-08 05:36 | Werner Dworak | Status | confirmed => needs work |
2013-01-18 00:36 | INOPIAE | Relationship added | related to 0000893 |
2013-01-18 00:37 | INOPIAE | Relationship added | related to 0001138 |
2013-01-29 17:26 | Uli60 | Note Added: 0003734 | |
2013-01-29 17:28 | Uli60 | Note Added: 0003735 | |
2013-01-29 17:28 | Uli60 | Status | needs work => solved? |
2013-01-29 17:28 | Uli60 | Resolution | suspended => fixed |
2013-01-29 17:28 | Uli60 | Assigned To | => Uli60 |
2013-05-01 01:08 | INOPIAE | Status | solved? => closed |