[Tickets #13240] Re: Import, renew public S/MIME Cert

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/13240
------------------------------------------------------------------------------
  Ticket           | 13240
  Aktualisiert Von | lauffer at ph-freiburg.de
  Zusammenfassung  | Import, renew public S/MIME Cert
  Warteschlange    | IMP
  Version          | Git master
  Typ              | Enhancement
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


lauffer at ph-freiburg.de (2014-06-04 09:33) hat geschrieben:

> 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.