Tickets :: [#13246] S/MIME: need of more than only one cert/keypair per address

Summary	S/MIME: need of more than only one cert/keypair per address
Queue	IMP
Queue Version	Git master
Type	Enhancement
State	Accepted
Priority	1. Low
Owners
Requester	lauffer (at) ph-freiburg (dot) de
Created	6/5/14 (4327 days ago)
Due
Updated	11/6/19 (2347 days ago)
Assigned
Resolved
Milestone
Patch	No

06.11.2019 07:16:24	Ralf Lang	Comment #3	Reply to this comment
There is partial support for this in the current git tree. It allows to store an optional second private S/MIME key for read-only.

05.06.2014 10:40:06	Jan Schneider	Comment #2 State ⇒ Accepted	Reply to this comment
See also request #7093

05.06.2014 05:52:48	lauffer (at) ph-freiburg (dot) de	Comment #1 Priority ⇒ 1. Low Patch ⇒ No Milestone ⇒ Queue ⇒ IMP Summary ⇒ S/MIME: need of more than only one cert/keypair per address Type ⇒ Enhancement State ⇒ New	Reply to this comment
If a key got lost, in foreign hands... whatever... and needs to be revoked the user will install a new keypair & cert. Since Horde can handle only one cert the user could not keep his old key in horde. This means: The user could no longer read his old,crypted mails with his old key. My wish would something like this: Manage several private certs/keys and then let the user decide which cerst should be used per identity/address. F.e. let the user pick the right cert in the "Personal Information" menue and manage all installed cerst (still) in the S/MIME menue.