Archived:Self-signed certificates expire after one year (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata

---

Code Example

Source file: Media:Makekeys.zip

---

Compatibility

Platform(s): S60 3rd Edition
S60 3rd Edition, Feature Pack 1

---

Article

Created: User:Technical writer 1 (08 Feb 2008)

Last edited: hamishwillee (19 Jun 2012)

Description

The makekeys utility in S60 3rd Edition/FP1 SDKs sets the expiry period of self signed certificates it creates to one year by default. After one year, SIS packages signed with this certificate can no longer be installed.

There is an updated version of the makekeys utility that allows changing the expiry period. However, this version is available after 3rd Edition, Feature Pack 2.

Solution

When creating the private key and certificate used for self-signing, use a version of makekeys that recognizes the expdays command line parameter for setting the expiry period in days.

For example:

 makekeys -cert -expdays 7300 -password secretpassword -len 2048 -dname
          "CN=Test User OU=Development OR=Company CO=FI EM=test@company.com"
          mykey.key mycert.cer

S60 3rd Edition, Feature Pack 2 SDK already has this version of makekeys.

For previous SDK versions, this version can be downloaded from File:Makekeys.zip.