6.0.0-alpha14
6/30/25

[#13240] Import, renew public S/MIME Cert
Summary Import, renew public S/MIME Cert
Queue IMP
Queue Version Git master
Type Enhancement
State Rejected
Priority 1. Low
Owners
Requester lauffer (at) ph-freiburg (dot) de
Created 06/03/2014 (4045 days ago)
Due
Updated 01/28/2016 (3441 days ago)
Assigned
Resolved 01/28/2016 (3441 days ago)
Milestone
Patch No

History
01/28/2016 01:38:47 PM Jan Schneider Comment #4
State ⇒ Rejected
Reply to this comment
Exchanging the cert of a key is not possible with the openssl 
extension of PHP that we use for all S/MIME features.
06/04/2014 09:33:00 AM lauffer (at) ph-freiburg (dot) de Comment #3 Reply to this comment
What's not user friendly about doing two steps to update the key? 
Delete, then import.
Depending on your infrastructure the user just get the new cert and 
now needs to build a new p12 file. If (for example) he just stored his 
key in horde (after creating it and yes, that is not the best idea) he 
needs to download and save the key, use openssl f.e. to build a new 
p12 with the CA-certs, the personal cert and the keys...

Maybe the user holds his keypair not only in hord he needs to build 
the p12 anyway somewhere (import, export in thinderbird, firefox... 
wherevere) in any way.

So imho it would nice and consequent if there is a way in Horde to 
import a new cert for the existing keys.
06/04/2014 08:45:36 AM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
What's not user friendly about doing two steps to update the key? 
Delete, then import.
06/03/2014 10:34:44 AM lauffer (at) ph-freiburg (dot) de Comment #1
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Import, renew public S/MIME Cert
Type ⇒ Enhancement
State ⇒ New
Reply to this comment
If the validity of a cert ends and the user get a new cert from his 
PKI there is no userfriendly way to change/replace the old cert.

It would be very nice if there would be a replace/change dialog next 
to the "[View] [Details]" links.

Btw: If this feature would be added we maybe should check if the 
modulus of the existing private key would match with the modulus of 
the new cert.

Saved Queries