×

Discussion Board

Results 1 to 10 of 10
  1. #1
    Registered User
    Join Date
    Nov 2006
    Posts
    568

    Merge SIS problem

    I have a bunch of SIS modules (all unsigned, testrange)
    I tried to mergesis the modules in order to produce a new unsigned, testrange sis, which I can opensign afterwards.

    The modules are:
    1) appswitch103_unsigned_devcertfree.SIS
    2) keypress_1.0.6_unsigned_testrange.sis
    3) appuifw2_1[1].0.1_3rdEd_unsigned_testrange.sis
    4) my module.sis

    I can produce a big SIS, opensign it, keypress and appswitch install fine. Appuifw2 refuses installation.

    The question: How to merge a bunch of SIS to a new SIS?

  2. #2
    Registered User
    Join Date
    Nov 2006
    Posts
    568

    Re: Merge SIS problem

    This is the module package:
    Code:
    Package Name: appuifw2
    Vendor Name: Arkadiusz Wahlig
    Package UID: 0xEDC67CB3
    Capabilities: PowerMgmt, ReadDeviceData, WriteDeviceData, TrustedUI, ProtServ, SwEvent, NetworkServices, LocalServices, ReadUserData, WriteUserData, Location, SurroundingsDD, UserEnvironment 
    Install Type: Standard Application (SA) 
    
    Signing Status: Self-Signed
    "Self-Signed" means that you have signed the SIS file yourself, rather than putting it through the Symbian Signed process. Your SIS file is untrusted, and may only make use of a certain subset of capabilities. You may also not use SIDs, VIDs or Package UIDs from the protected range. 
    ---------------------------------------------------------
    
    Package Name: keypress
    Vendor Name: Ensymble
    Package UID: 0xE6E6D76F
    Capabilities: PowerMgmt, ReadDeviceData, WriteDeviceData, TrustedUI, ProtServ, SwEvent, NetworkServices, LocalServices, ReadUserData, WriteUserData, Location, SurroundingsDD, UserEnvironment 
    Install Type: Standard Application (SA) 
    
    Signing Status: Self-Signed
    "Self-Signed" means that you have signed the SIS file yourself, rather than putting it through the Symbian Signed process. Your SIS file is untrusted, and may only make use of a certain subset of capabilities. You may also not use SIDs, VIDs or Package UIDs from the protected range. 
    ----------------------------------------------------------
    
    
    Package Name: appswitch
    Vendor Name: Vendor
    Package UID: 0xA0001F9C
    Capabilities: PowerMgmt, ReadDeviceData, WriteDeviceData, TrustedUI, ProtServ, SwEvent, NetworkServices, LocalServices, ReadUserData, WriteUserData, Location, SurroundingsDD, UserEnvironment 
    Install Type: Standard Application (SA) 
    
    Signing Status: Signed
    "Signed" means that your SIS file has been through Symbian Signed, or some other equivalent manufacturer signing process (or is signed by a dev cert, which is much the same.) A signed SIS file can make use of capabilities that are not available to a self signed SIS file. 
    ----------------------------------------------------------
    
    
    Package Name: PhoneGuard
    Vendor Name: Ensymble
    Package UID: 0xE13331C5
    Capabilities: PowerMgmt, ReadDeviceData, WriteDeviceData, TrustedUI, ProtServ, SwEvent, NetworkServices, LocalServices, ReadUserData, WriteUserData, Location, SurroundingsDD, UserEnvironment 
    Install Type: Standard Application (SA) 
    
    Signing Status: Self-Signed
    "Self-Signed" means that you have signed the SIS file yourself, rather than putting it through the Symbian Signed process. Your SIS file is untrusted, and may only make use of a certain subset of capabilities. You may also not use SIDs, VIDs or Package UIDs from the protected range.
    These 4 modules are ensymbled "mergesis" to a new sis, the SIS is signed using opensign with all caps, but it refuses to install. Any ideas?

    Regards

  3. #3
    Nokia Developer Moderator
    Join Date
    May 2007
    Location
    21.46 N 72.11 E
    Posts
    3,779

    Re: Merge SIS problem

    Let us know the command you use to merge the files.

    Best Regards,
    Croozeus
    Pankaj Nathani
    www.croozeus.com

  4. #4
    Registered User
    Join Date
    Nov 2006
    Posts
    568

    Re: Merge SIS problem

    Hi Croozeus,

    basically just this:

    1) SIS my Script, full caps, unsigned
    Code:
    python ensymble_python2.2-0.25.py 
    py2sis 
    --version=1.0.4 	
    --caps=LocalServices+
    Location+
    NetworkServices+
    ReadDeviceData+
    ReadUserData+
    WriteUserData+
    SurroundingsDD+
    WriteDeviceData+
    UserEnvironment+
    SwEvent+
    TrustedUI+
    PowerMgmt+
    ProtServ 	
    --autostart 
    PhoneGuard.py
    2) Merge this with modules appswitch, keypress and appuifw2 (all unsigned, testrange)
    Code:
    python ensymble_python2.2-0.25.py 
    mergesis 
    --verbose 
    PhoneGuard_v1_0_4.sis 
    keypress\keypress_1.0.6_unsigned_testrange.sis 
    appswitch\appswitch103_unsigned_devcertfree.SIS 
    appuifw2\appuifw2_1[1].0.1_3rdEd_unsigned_testrange.sis 
    PhoneGuard_v1_0_4_unsigned_testrange.sis
    3) The SIS is created, fits in size, upload to opensign and opensign it with full caps.

    4) Installation PhoneGuard seems to work, but keypress stucks and all other modules are not installed at all.

  5. #5
    Nokia Developer Moderator
    Join Date
    May 2007
    Location
    21.46 N 72.11 E
    Posts
    3,779

    Re: Merge SIS problem

    As I thought, Its a capability problem.

    The files need to be signed before merging. Only the 1st file can be submitted unsigned.

    keypress\keypress_1.0.6_unsigned_testrange.sis
    appswitch\appswitch103_unsigned_devcertfree.SIS
    appuifw2\appuifw2_1[1].0.1_3rdEd_unsigned_testrange.sis
    Hence,

    Code:
    python ensymble_python2.2-0.25.py 
    mergesis 
    --verbose 
    PhoneGuard_v1_0_4.sis 
    keypress\keypress_1.0.6_signed.sisx 
    appswitch\appswitch103_signed.sisx 
    appuifw2\appuifw2_1[1].0.1_3rdEd_signed.sisx
    And I don't understand why you include the PhoneGuard_v1_0_4.sis and PhoneGuard_v1_0_4_unsigned_testrange.sis both ?

    This way your package will have two Phoneguard installations.
    Pankaj Nathani
    www.croozeus.com

  6. #6
    Registered User
    Join Date
    Nov 2006
    Posts
    568

    Re: Merge SIS problem

    The latter is the output, the merged file

  7. #7
    Registered User
    Join Date
    Nov 2006
    Posts
    568

    Re: Merge SIS problem

    The files need to be signed before merging. Only the 1st file can be submitted unsigned.
    Oh that's bad. This prevents the distribution of a singe SIS file to others, who just have to opensign it.

    Symbiansigned is a pain in the ...

  8. #8
    Super Contributor
    Join Date
    May 2004
    Location
    Tampere, Finland
    Posts
    524

    Re: Merge SIS problem

    Quote Originally Posted by neil.young View Post
    I have a bunch of SIS modules (all unsigned, testrange)
    Maybe a simple diagram explains best what kind of SIS files the mergesis command produces. Command

    Code:
      ensymble.py mergesis mysis1.sis mysis2.sis mysis3.sis outsis.sis
    produces the following outsis.sis:

    Code:
      mysis1        Certificate gets replaced by a default one and mysis2, mysis3 embedded inside
        --> mysis2  Included inside mysis1 as-is, certificate and all
        --> mysis3  Included inside mysis1 as-is, certificate and all
    Then, Open Signed turns it into this:

    Code:
      mysis1        Certificate gets replaced again
        --> mysis2  Included inside mysis1 as-is, original certificate still intact
        --> mysis3  Included inside mysis1 as-is, original certificate still intact
    For example, in your scenario, keypress requires the SWEvent capability, which is not available to self-signed SIS files. Using mergesis the way you describe does not change the fact that keypress remains self-signed.

  9. #9
    Super Contributor
    Join Date
    May 2004
    Location
    Tampere, Finland
    Posts
    524

    Re: Merge SIS problem

    Quote Originally Posted by neil.young View Post
    Oh that's bad. This prevents the distribution of a singe SIS file to others, who just have to opensign it.
    Yes. I think the reason for such an internal structure of SIS files is that Nokia could in theory release a helpful SIS file with super-human capabilities (AllFiles, say), normally unattainable for any normal developer. You could still include this super SIS in your own applications.

    Quote Originally Posted by neil.young View Post
    Symbiansigned is a pain in the ...
    Amen.

  10. #10
    Registered User
    Join Date
    Nov 2006
    Posts
    568

    Re: Merge SIS problem

    Jethro, thanks for the explanation.

    So if I don't want to buy a super dooper all around happy certificate from that guys, i have to tell to people interested in getting my sw:

    1) Download appswitch, keypress, appuifw2 from the sources, you are left alone, because even the developers don't know, what is the right version currently
    2) Go to the spider opensing.com, pass a super stupdid "open sign" process (Gees, didn't somone tell them something about webservices by end of the 90th or so??), "sign" all modules found in (1) and of course mine too
    3) Crossing fingers, get the files back and put it onto your phone, piece by piece...???

    I never thought that I had to get that old in order to see such a bullshit again...

    Sick world... the world of symbiansigned...

Similar Threads

  1. Problem with installing SIS via C# (even with example)
    By JustABAStudent in forum PC Suite API and PC Connectivity SDK
    Replies: 2
    Last Post: 2009-03-15, 13:02
  2. problem in creating sis file in helloworldbasic app?
    By SanjayKhuntia in forum Symbian
    Replies: 8
    Last Post: 2008-08-12, 12:56
  3. SIS build problem
    By tinka_83 in forum Symbian
    Replies: 8
    Last Post: 2008-05-23, 04:34
  4. unable to merge two sis file on device .
    By amardeep in forum Symbian
    Replies: 0
    Last Post: 2003-04-25, 08:08
  5. Replies: 0
    Last Post: 2003-03-06, 18:22

Posting Permissions

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