Discussion Board

Results 1 to 4 of 4
  1. #1
    Regular Contributor RomanAge's Avatar
    Join Date
    Nov 2009
    Posts
    112
    Hello,

    I'm confused . I know that an application has to be self-signed (if not Symbian Signed).
    I use Carbide C++, to create a SIS file and SISX file.
    The SIS file cannot work, as it is unsigned (I'm fine with that ).

    But until now, I thought that the SISX file was not yet self-signed. However it looks like it is, as it is created by ticking the option self-signed (and the fact that it is a SISX file means just that: self-signed, also it does install properly, with a warning message, as expected).

    The only thing is: my application did not have a proper UID from Symbian (it was randomly generated by Carbide). So I got one from Symbian, from the unprotected range, as I understand it is meant to be used for self-signing (OS 9.0), and that one from the protected range would not work for self-signing (tell me if I'm wrong).
    So I create my self-signed SISX file with the right UID now, it works.

    Why is it possible to create in Carbide a SISX file (supposed to be self-signed) without a proper UID? The one generated by Carbide is supposed to be for testing only. Or is it because it is no different to those generated by Symbian? (in the unprotected range, I mean).

    In any case I can see the point of getting a UID from Symbian as you fill a few information about the product, which is the only way to identify its origin, for instance.
    Tell me, how much do I understand? Am I missing something?

    Thanks.

  2. #2
    Nokia Developer Expert symbianyucca's Avatar
    Join Date
    Mar 2003
    Location
    Lempäälä/Finland
    Posts
    28,664
    Basically I suppose Carbide uses test-range UIDs by default (0xExxxxx ones), those UIDs should not be used for normal distribution versions and should only be used for examples & test&developerment state applications. I actually never tried self-signing with test range UID, but I assume it works.

    Where as protected range UIDs would not work with self-signing, so you are correct on that one.

    Basically by using the real UID allocated for your own account in Symbian signed, you can be certain that your application has unique UID, when using test-range UIDs, somebody else could as well be using the same UIDs which could lead to some unexpected problems..

  3. #3
    Registered User Nequita's Avatar
    Join Date
    Jun 2012
    Posts
    6
    Hello
    How do you self sign with carbide??

  4. #4
    Nokia Developer Moderator wizard_hu_'s Avatar
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    27,682
    That is the default when you create a new project. Otherwise you can configure the SIS Builder in the project Properties (and check the Carbide.c++ group there)

Similar Threads

  1. Каковы карательные меры за непрохождение Symbian Signed Test
    By BETEP.OK in forum Russian Developer Forum - Форум Российских разработчиков
    Replies: 7
    Last Post: 2009-08-08, 11:20
  2. Symbian Signed recognizer with self signed exe?
    By vonolsson in forum Symbian C++
    Replies: 2
    Last Post: 2007-02-23, 10:10
  3. Symbian Signed Catalog
    By dangeross in forum Symbian Signed Support, Application Packaging and Distribution and Security
    Replies: 0
    Last Post: 2006-11-30, 11:14
  4. Distributing for Symbian 9 without Symbian Signed
    By tal.shahar@mobile-mx.com in forum Symbian C++
    Replies: 2
    Last Post: 2006-09-06, 05:15
  5. Symbian Signed - Low Mem test
    By rave_symbian in forum Symbian C++
    Replies: 9
    Last Post: 2006-02-02, 14:17

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Nokia Developer aims to help you create apps and publish them so you can connect with users around the world.

京ICP备05048969号  © Copyright Nokia 2013 All rights reserved