×

Discussion Board

Results 1 to 11 of 11
  1. #1
    Regular Contributor
    Join Date
    Mar 2005
    Posts
    77

    "Developer Certificate Signed : Not Yet Valid" problem

    Hi,

    After many struggles porting my app from Ed2 to Ed3,I am at a loss signing it. Here is a trace of a DOS create/sign session. I had requested and got a .cer file from symbian signed, and tried to apply it. It came up with 'Not Yet Valid' during the signing process, why was that?? After a few minutes, it seemed to change its mind, and came up with developer signed Yes.

    Inwardly rejoicing, I tried to load it on to an E65, but Christmas had not yet come!! The phone said it had a problem. "Certificate may not yet be valid, is expired, or the phone date is set wrongly"

    What is the problem here? Is there something extra about validity periods that I do not understand?

    As a separate issue, why does the SIS creation not work from the Carbide environment? I get:-
    C:\Symbian\9.2\S60_3rd_FP1_4\epoc32\tools\makesis.exe C:\Symbian\Carbide\savecell\SaveCell\sis\_resolvedSaveCell3.pkg C:\Symbian\Carbide\savecell\SaveCell\sis\sis\SaveCell3.sis -v
    Processing C:\Symbian\Carbide\savecell\SaveCell\sis\_resolvedSaveCell3.pkg...
    error: file I/O fault.
    ***Non-Zero Status: makesis.exe returned with exit value = 1

    As it works in DOS, I used it...

    I have checked the times/dates on the phone and PC, and they coincide to within 1 minute with the 123 phone time service.

    If only I understood how signing and checking worked I would have more chance of guessing how to fix it...

    Just in case it helps, I enclose the .MMP and .PKG files.

    Richard






    Code:
    C:\Symbian\Carbide\savecell\SaveCell\sis>makesis -v _resolvedsavecell3.pkg
    Processing _resolvedsavecell3.pkg...
    
    Created _resolvedsavecell3.SIS
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>signsis -v -o -s  _resolvedsavecell3.si
    s savecell3.sis savecell.cer savecell.key
    
    SIGNSIS Version 4, 0, 0, 0
    A utility for signing Software Installation (SIS) files.
    Copyright (c) 2004 Symbian Software Ltd. All rights reserved.
    
    Signing
    
    Primary:
    Issued by Symbian Developer Certificate CA 280205A.
    Issued to Symbian Signed PublisherID.
    Valid from 21/11/2007 to 21/05/2008.
    Issued by VeriSign Identity-Based ACS Root for Symbian OS.
    Issued to Symbian Software Limited.
    Valid from 02/03/2005 to 01/03/2015.
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>verifysymbiansigned_25_05_2007 savecell
    3.sis
    
    ------------------------------
    File format                  : SISX (V9)
    SIS file                     : savecell3.sis
    ------------------------------
    Symbian Signed               : No
    Developer Certificate Signed : Not Yet Valid      <<<<<<<<<<<<<<<<<<<<<<<<<
    ACS Publisher Signed         : No
    Unknown Certifictaes         : 0
    ------------------------------
    C:\Symbian\Carbide\savecell\SaveCell\sis>time
    The current time is: 11:59:47.54
    Enter the new time:
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>ssis
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>makesis -v _resolvedsavecell3.pkg
    Processing _resolvedsavecell3.pkg...
    
    Created _resolvedsavecell3.SIS
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>signsis -v -o -s  _resolvedsavecell3.si
    s savecell3.sis savecell.cer savecell.key
    
    SIGNSIS Version 4, 0, 0, 0
    A utility for signing Software Installation (SIS) files.
    Copyright (c) 2004 Symbian Software Ltd. All rights reserved.
    
    Signing
    
    Primary:
    Issued by Symbian Developer Certificate CA 280205A.
    Issued to Symbian Signed PublisherID.
    Valid from 21/11/2007 to 21/05/2008.
    Issued by VeriSign Identity-Based ACS Root for Symbian OS.
    Issued to Symbian Software Limited.
    Valid from 02/03/2005 to 01/03/2015.
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>verifysymbiansigned_25_05_2007 savecell
    3.sis
    
    ------------------------------
    File format                  : SISX (V9)
    SIS file                     : savecell3.sis
    ------------------------------
    Symbian Signed               : No
    Developer Certificate Signed : Not Yet Valid       <<<<<<<<<<<<<<<<<<<<<<<<<
    ACS Publisher Signed         : No
    Unknown Certifictaes         : 0
    ------------------------------
    
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>time
    The current time is: 12:03:12.57
    Enter the new time:
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>date
    The current date is: 21/11/2007
    Enter the new date: (dd-mm-yy)
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>ssis
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>makesis -v _resolvedsavecell3.pkg
    Processing _resolvedsavecell3.pkg...
    
    Generating SIS installation file...
    Created _resolvedsavecell3.SIS
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>signsis -v -o -s  _resolvedsavecell3.si
    s savecell3.sis savecell.cer savecell.key
    
    SIGNSIS Version 4, 0, 0, 0
    A utility for signing Software Installation (SIS) files.
    Copyright (c) 2004 Symbian Software Ltd. All rights reserved.
    
    Signing
    
    Primary:
    Issued by Symbian Developer Certificate CA 280205A.
    Issued to Symbian Signed PublisherID.
    Valid from 21/11/2007 to 21/05/2008.
    Issued by VeriSign Identity-Based ACS Root for Symbian OS.
    Issued to Symbian Software Limited.
    Valid from 02/03/2005 to 01/03/2015.
    
    C:\Symbian\Carbide\savecell\SaveCell\sis>verifysymbiansigned_25_05_2007 savecell
    3.sis
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    ------------------------------
    File format                  : SISX (V9)
    SIS file                     : savecell3.sis
    ------------------------------
    Symbian Signed               : No
    Developer Certificate Signed : Yes   <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    ACS Publisher Signed         : No
    Unknown Certifictaes         : 0
    ------------------------------
    C:\Symbian\Carbide\savecell\SaveCell\sis>
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    
    ; SaveCell3.pkg
    ;
    ;Language - standard language definitions
    &EN
    
    ; standard SIS file header
    #{"SaveCell"},(0x2000fec2),1,0,0
    
    ;Localised Vendor name
    %{"SMS Systems Ltd"}
    
    ;Unique Vendor name
    :"SMS Systems Ltd"
    
    ;Supports Series 60 v 3.0
    [0x101F7961], 0, 0, 0, {"Series60ProductID"}
    
    ;Files to install
    ;You should change the source paths to match that of your environment
    ;<source> <destination>
    "C:\Symbian\9.2\S60_3rd_FP1_4\Epoc32\release\GCCE\UDEB\SaveCell.exe"		-"!:\sys\bin\uitest.exe"
    "C:\Symbian\9.2\S60_3rd_FP1_4\Epoc32\data\z\resource\apps\SaveCell.r01"		-"!:\resource\apps\uitest.r01"
    "C:\Symbian\9.2\S60_3rd_FP1_4\Epoc32\data\z\private\10003a3f\apps\SaveCell_reg.r01"	-"!:\private\10003a3f\import\apps\uitest_reg.r01"
    "C:\Symbian\9.2\S60_3rd_FP1_4\Epoc32\data\z\resource\apps\SaveCell_aif.mif" -"!:\resource\apps\uitest_aif.mif"
    
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Savecell3.mmp
    
    
    #ifdef EKA2
    #define THIRD_EDITION_MMP
    MACRO THIRD_EDITION
    #endif
    
    
    #ifdef THIRD_EDITION_MMP
    TARGET  SaveCell.exe
    TARGETTYPE  exe
    UID  0x100039CE KSaveCell3Uid
    SECUREID KSaveCell3Uid 
    EPOCSTACKSIZE 0x8000
    
    #else
    
    TARGET SaveCell.app
    TARGETTYPE app
    UID  0x100039CE KSaveCell3Uid
    TARGETPATH \system\apps\SaveCell
     
    #endif
    
    
    SYSTEMINCLUDE \epoc32\include \epoc32\include\variant
    USERINCLUDE	   ..\inc ..\data
    
    
    
    SOURCEPATH		..\data
    
    #ifdef THIRD_EDITION_MMP
    
    START RESOURCE SaveCell.rss
    TARGET savecell.r01
    
    TARGETPATH \resource\apps
    HEADER
    LANG 01
    END //Resource savecell.apps
    
    START RESOURCE savecell_reg.rss
    TARGET savecell_reg.r01
    TARGETPATH \private\10003a3f\apps
    HEADER
    LANG 01
    END //RESOURCE savecell_reg.rss
    
    #else
    
    RESOURCE SaveCell.rss
    RESOURCE savecell_caption.rss
    
    #endif
    
    LANG SC
    
    LIBRARY 	euser.lib apparc.lib cone.lib eikcore.lib
    LIBRARY 	eikcoctl.lib avkon.lib commonengine.lib eikdlg.lib
    LIBRARY 	eikctl.lib bafl.lib fbscli.lib efsrv.lib estor.lib aknnotify.lib
    LIBRARY 	etext.lib gdi.lib egul.lib insock.lib msgs.lib  etel3rdparty.lib smcm.lib gsmu.lib 
    LIBRARY     flogger.lib cntmodel.lib pbkeng.lib pbkview.lib charconv.lib 
    
    SOURCEPATH		..\src
    
    SOURCE SaveCellContainerView.cpp SaveCellContainer.cpp SaveCellApplication.cpp SaveCellAppUi.cpp SaveCellDocument.cpp SaveCellAlienPhoneScreenView.cpp SaveCellAlienPhoneScreen.cpp SaveCellAlienPhoneScreenSettings.cpp SaveCellAlienHelp.cpp SaveCellAlienHelpView.cpp SaveCellContainerHelp.cpp SaveCellContainerHelpView.cpp SaveCellNoExit.cpp SaveCellNoExitView.cpp SaveCellRegisterHelp.cpp SaveCellRegisterHelpView.cpp SaveCellRegisterScreenSettings.cpp SaveCellRegisterScreen.cpp SaveCellRegisterScreenView.cpp SaveCellStatus.cpp SaveCellSMSEngine.cpp SaveCellSettingSettings.cpp SaveCellSettingView.cpp SaveCellSetting.cpp SaveCellStatistics.cpp SaveCellStatisticsView.cpp SaveCellSettingHelpView.cpp SaveCellSettingHelp.cpp SaveCellDisplay.cpp SaveCellDisplayView.cpp SaveCellDummyView.cpp SaveCellDummy.cpp SaveCellMessagesIn.cpp SaveCellMessagesOut.cpp SaveCellQueue.cpp SaveCellpbEngine.cpp SaveCellpbkView.cpp SaveCellpbk.cpp SaveCellAlienConfirm.cpp SaveCellAlienConfirmView.cpp
    
    
    
    #ifdef THIRD_EDITION_MMP
    VENDORID 0
    CAPABILITY ReadDeviceData ReadUserData NetworkServices WriteUserData
    #endif
    
    #ifndef THIRD_EDITION_MMP
    AIF savecell.aif ..\aif savecellaif.rss c8 list_icon_mask.bmp
    #endif
    Last edited by ltomuta; 2007-11-21 at 13:18.

  2. #2
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    28,684

    Re: "Developer Certificate Signed : Not Yet Valid" problem

    Try setting the date on the phone to tomorrow.

  3. #3
    Regular Contributor
    Join Date
    Mar 2005
    Posts
    77

    Re: "Developer Certificate Signed : Not Yet Valid" problem

    Hello again wizard_hu_,

    That worked OK!!!! The application gets much further into the install sequence, before it stalls on'Required access not granted". I have modified the MMP file to only ask for 'LocalServices, NetworkAccess, ReadUserData, and WriteUserData'. This is the set specified in my .cer file.

    What is the problem now, why is it all so difficult?

    Richard

  4. #4
    Nokia Developer Moderator
    Join Date
    Sep 2004
    Location
    Tampere, Finland
    Posts
    11,359

    Re: "Developer Certificate Signed : Not Yet Valid" problem

    It is not difficult at all once you know what you're doing.

    MMP changes may require a project update before the changes are propagated to the output binaries. To check the actual capabilities currently set for the binaries you can use the elfran tool with the "-dump s" switches.
    -- Lucian

    If you are not yet a DVLUP member it is time to correct that mistake :) Click here to join: http://www.dvlup.com/lucian/Invite

  5. #5
    Super Contributor
    Join Date
    Jul 2006
    Location
    Oulu, Finland.
    Posts
    1,174

    Re: "Developer Certificate Signed : Not Yet Valid" problem

    There is one article at NewLC which expose common problems with signing and certification:

    http://www.newlc.com/topic-13580

    Look for :
    Number 10 - stuff about signing and capabilites
    Number 11 - reasons why your SIS file may not install

  6. #6
    Regular Contributor
    Join Date
    Mar 2005
    Posts
    77

    Re: "Developer Certificate Signed : Not Yet Valid" problem

    Hi All,

    It now installs, I did a 'Clean reallyclean', and all sprang into life...

    It does not run, of course, but this is Symbian, it's nothing like the Emulator, so now I will learn abou the Device Debugger... The whole development process is a bit of a B****r.

    Richard

  7. #7
    Regular Contributor
    Join Date
    Mar 2005
    Posts
    77

    Re: "Developer Certificate Signed : Not Yet Valid" problem

    Hi Itomuta,

    Yes, I know that every thing is easy once you can do it, but you must admit that the Symbian environment documentation is not world-class...

    Could you be a little more explicit about what the 'elfran' tool is? A search of this forum, or a Google search return no significant results.

    Thank you

    Richard

  8. #8
    Nokia Developer Moderator
    Join Date
    Sep 2004
    Location
    Tampere, Finland
    Posts
    11,359

    Re: "Developer Certificate Signed : Not Yet Valid" problem

    Quote Originally Posted by 76Richard76 View Post
    Hi Itomuta,

    Yes, I know that every thing is easy once you can do it, but you must admit that the Symbian environment documentation is not world-class...
    Sad but very true. That is why is important to contribute to the Forum Nokia Wiki each time we learn something new [to each of us].

    Quote Originally Posted by 76Richard76 View Post
    Could you be a little more explicit about what the 'elfran' tool is? A search of this forum, or a Google search return no significant results.

    Thank you

    Richard
    Elftran is part of SDK's tool chain, you can call it from the command prompt. It only works on binaries built for the device (armv5 or gcce) and the aspect that is of interest to you is that when called with the "-dump s <path\binary_file>" parameters it will dump the platform security info embedded in that binary, including the capabilities.

    Compare those results with the MMP settings. If they are not the same clean and rebuild the project.

    All this is needed as I suspect your current binaries still have a capability which you are not able to sign for with your capability.
    -- Lucian

    If you are not yet a DVLUP member it is time to correct that mistake :) Click here to join: http://www.dvlup.com/lucian/Invite

  9. #9
    Regular Contributor
    Join Date
    Mar 2005
    Posts
    77

    Re: "Developer Certificate Signed : Not Yet Valid" problem

    Hello again,

    I have listened to the advice offered on two separate threads, heard the video on symbian signing 4 times, and spent sleepless nights thinking about my problems. I am very close to saying that my product will only run on 2nd Edition phones, or the 3rd edition emulator. That seems very defeatist, but I feel that I am being a real pain to the discussions board...

    I managed to cure my certificate generation problems by reloading my ID from trustcenter, and redoing tcp12p8 etc. The files must have got corrupted somehow, but all now works OK.

    My app now installs OK, but does not run on an E65. On the theory put forward by Paul Todd and Itomuta, that it was a capabilities problem, I did the following...

    Recompile on the Phone Debug (GCCE) [S60_3rd_MR] SDK.
    No comp errors, sis file generated with cert as shown below
    Hard reset phone *#7370#
    Set date in phone to tomorrow.
    Set app.manager to accept non symbian signed.
    Installed app by cable.
    installed ErrRd
    Called app
    "System Error -1"

    .MMP file :-
    //#include "..\inc\SaveCellUids.h"

    #define KSaveCell3Uid 0x2000fec2

    #ifdef EKA2
    #define THIRD_EDITION_MMP
    MACRO THIRD_EDITION
    #endif


    #ifdef THIRD_EDITION_MMP
    TARGET SaveCell.exe
    TARGETTYPE exe
    UID 0x100039CE KSaveCell3Uid
    SECUREID KSaveCell3Uid
    EPOCSTACKSIZE 0x8000

    #else

    TARGET SaveCell.app
    TARGETTYPE app
    UID 0x100039CE KSaveCell3Uid
    TARGETPATH \system\apps\SaveCell

    #endif


    SYSTEMINCLUDE \epoc32\include
    USERINCLUDE ..\inc ..\data



    SOURCEPATH ..\data

    #ifdef THIRD_EDITION_MMP

    START RESOURCE SaveCell.rss
    TARGET savecell.r01

    TARGETPATH \resource\apps
    HEADER
    LANG 01
    END //Resource savecell.apps

    START RESOURCE savecell_reg.rss
    TARGET savecell_reg.r01
    TARGETPATH \private\10003a3f\apps
    HEADER
    LANG 01
    END //RESOURCE savecell_reg.rss

    #else

    RESOURCE SaveCell.rss
    RESOURCE savecell_caption.rss

    #endif

    LANG SC

    LIBRARY euser.lib apparc.lib cone.lib eikcore.lib
    LIBRARY eikcoctl.lib avkon.lib commonengine.lib eikdlg.lib
    LIBRARY eikctl.lib bafl.lib fbscli.lib efsrv.lib estor.lib aknnotify.lib
    LIBRARY etext.lib
    LIBRARY gdi.lib
    LIBRARY egul.lib
    LIBRARY msgs.lib
    LIBRARY smcm.lib
    LIBRARY gsmu.lib
    LIBRARY flogger.lib cntmodel.lib pbkeng.lib pbkview.lib charconv.lib

    SOURCEPATH ..\src

    SOURCE SaveCellContainerView.cpp SaveCellContainer.cpp SaveCellApplication.cpp SaveCellAppUi.cpp SaveCellDocument.cpp SaveCellAlienPhoneScreenView.cpp SaveCellAlienPhoneScreen.cpp SaveCellAlienPhoneScreenSettings.cpp SaveCellAlienHelp.cpp SaveCellAlienHelpView.cpp SaveCellContainerHelp.cpp SaveCellContainerHelpView.cpp SaveCellNoExit.cpp SaveCellNoExitView.cpp SaveCellRegisterHelp.cpp SaveCellRegisterHelpView.cpp SaveCellRegisterScreenSettings.cpp SaveCellRegisterScreen.cpp SaveCellRegisterScreenView.cpp SaveCellStatus.cpp SaveCellSMSEngine.cpp SaveCellSettingSettings.cpp SaveCellSettingView.cpp SaveCellSetting.cpp SaveCellStatistics.cpp SaveCellStatisticsView.cpp SaveCellSettingHelpView.cpp SaveCellSettingHelp.cpp SaveCellDisplay.cpp SaveCellDisplayView.cpp SaveCellDummyView.cpp SaveCellDummy.cpp SaveCellMessagesIn.cpp SaveCellMessagesOut.cpp SaveCellQueue.cpp SaveCellpbEngine.cpp SaveCellpbkView.cpp SaveCellpbk.cpp SaveCellAlienConfirm.cpp SaveCellAlienConfirmView.cpp



    #ifdef THIRD_EDITION_MMP
    VENDORID 0
    CAPABILITY LocalServices Location NetworkServices ReadDeviceData ReadUserData SurroundingsDD SwEvent UserEnvironment WriteDeviceData WriteUserData
    #endif

    #ifndef THIRD_EDITION_MMP
    AIF savecell.aif ..\aif savecellaif.rss c8 list_icon_mask.bmp
    #endif


    I attach the output from the dev cert request tool, and from running elftran on the .EXE, they seem to show correspondence between the capabilities, which are just about the maximum one can easily try without manufacturers rights.

    My Cert request:-

    Certificate Request File: C:\certs\savecellall.csr Private Key File: C:\certs\savecell4.key
    Country: UNITED KINGDOM State: Worcestershire City: Redditch
    Company: SMS Systems Ltd Division:
    Symbian Signed PublisherID Common Name: SMS Systems Ltd IMEI(s): 353261013791232,359367004227336
    App Capabilities:
    ReadDeviceData,
    WriteDeviceData,
    SwEvent,
    NetworkServices,
    LocalServices,
    ReadUserData,
    WriteUserData,
    Location,
    SurroundingsDD,
    UserEnvironment


    elftran dump of the exe:-


    C:\certs>elftran -dump s C:\Symbian\9.1\S60_3rd_MR\Epoc32\release\GCCE\UDEB\SaveCell.exe

    ELFTRAN - ELF file preprocessor V02.01 (Build 549)
    Copyright (c) 1996-2005 Symbian Software Ltd.

    E32ImageFile 'C:\Symbian\9.1\S60_3rd_MR\Epoc32\release\GCCE\UDEB\SaveCell.exe'
    Secure ID: 2000fec2
    Vendor ID: 00000000
    Capabilities: 00000000 000ff030
    ReadDeviceData
    WriteDeviceData
    SwEvent
    NetworkServices
    LocalServices
    ReadUserData
    WriteUserData
    Location
    SurroundingsDD
    UserEnvironment

    There must be some basic error in my work, but I don't know what it is. In 40 years in computing I have never felt so frustrated. I have an app which runs OK on 2nd Edition, and on the 3rd edition emulator, but not on a real 3rd ed phone. If I compile for the emulator, and run it, there are no platsec errors.

    If only Symbian were a little more explicit with its error messages...

    Richard

  10. #10
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    28,684

    Re: "Developer Certificate Signed : Not Yet Valid" problem

    -1 is still KErrNotFound. It has nothing to do with capabilities. You might consider completely removing those "TARGET ....r01" lines, and install .rsc-s. Localization support can wait until your application starts working, at least in my opinion.

  11. #11
    Regular Contributor
    Join Date
    Mar 2005
    Posts
    77

    Re: "Developer Certificate Signed : Not Yet Valid" problem

    Hello wizard_hu,

    Thank you for your reply, pointing me at the 'NotFound' thought. I had copied my MMP file syntax from the 'Birthdays' example in the SDK, which complies, installs, and runs on 3rd Edition, so it could not have been causing my problems, I felt.

    But it DID make me look more closely at the file system that my app installed. In my .PKG file, I found that the destination installation file names were incorrect, referring to a prevous project. The source references were correct, so the app generated OK with Makesis.

    I am guilty of wasting everyone's time, and I am very sorry, but my app now loads and runs...Whoopee!

    Thank you all for your interest and help, especially ltomuta, Paul.Todd, mitts, vasant21 and wizard_hu.

    Things I have learnt along the way are:-

    1) If you generate a new certificate, don't expect it to work today unless you tell lies to your phone about the date.

    2) E-series phones don't like Developer apps, unless you set the option in app.manager.

    3) If your app won't delete from the phone, a *#7370# will remove it(and the rest of your data!).

    4) That the support community has some very nice people in it.

    Richard

Similar Threads

  1. Signed Application with different certificate
    By red0devil06 in forum Mobile Java General
    Replies: 15
    Last Post: 2009-10-08, 12:10
  2. Developer Certificate signed for n73
    By pakwaten in forum Symbian Signed Support, Application Packaging and Distribution and Security
    Replies: 2
    Last Post: 2007-07-16, 11:53
  3. verisign certificate signed application and 6265 behaviour
    By mmalam1 in forum Mobile Java General
    Replies: 5
    Last Post: 2006-08-17, 20:39

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×