Symbian Express signed null

Dear all,

I tried to sign my new SIS file wich contains a SIS and a JAR/JAD file
I have (I think) a correct certificate se below


[QUOTE]Content
C:\mobisma\dbg.txt
C:\mobisma\mobisma.ini
C:\mobisma\mobisma.jar
C:\mobisma\mobisma.jad
!:\private\10274b9f\import\programToStart.ast
c:\private\101f875a\import\[20027180].rsc
C:\sys\bin\mobismaSRV.exe [ReadDeviceData WriteDeviceData SwEvent NetworkServices ReadUserData WriteUserData]
7 file(s) total
Certificate Chain

Certificate 1:
Signer:
Mobisma AB
SE
Norrtaelje
Stockholm
Mobisma AB
Issuer:
TC TrustCenter Class 2 L1 CA XII
DE
TC TrustCenter GmbH[/QUOTE]


But when I upload the zipped file and want to go next after filling in the values I just get a null as error message, what is that?

[QUOTE]Application submission form: new

Step 1: Upload application

null[/QUOTE]

Can anybody please give me a clue?

Best Jens

What did you include in the zip file ? if I remember right you should have the publicer-signed sis, txt file as well as pkg file in it.

Yes that's right I have a .pkg file the sis file and a readmefile.txt and a readme.pdf
What I was thinking is that the .pkg file contains a JAR/JAD file (Wich of course is included in the SIS file) but should I also supply the JAR and JAD file standalone in the zip file?
It would have been much easier if I got another error message tha null :-)

Symbian signed is for signing symbian installation files, i.e. sis files, thus you can not have standalone java files there. Symbian signed basically should only care that :
1. The file to be signed is valid sis file
2. the sis file is signed only one time, and the certificate used is valid certificate for utilizing Symbian signed
3. The capabilities of dll and exe files inside the sis file are having capabilities allowed for the selected signing
4. UIDs with package are on correct range and reserved for the account used for signing.

Also do have only one sis file in the package, and do not use folders inside the zip file. Also I might submit the pdf separately (as text content, etc.) just to make sure it would not make any problems in there.

Then if it still does not work, then please check the sis file that is signed only one time, and it is indeed your publicer Id tht is used for signing, and then see that your publicer ID is still valid. And if those points appear to be ok, then specify step-by-step on what you have done, and what actually happens when it fails in details.

Symbianyucca,

Thankyou for your info

I have validated all your points, except the PDF file since I have used another sis file with no problem having the PDF inside.

I can see a bit of confusing information when I am signing my file with my converteed Trustcenter certificate though,
[QUOTE]Z:\Installs\mobismaSRV\expresssigned>VerifySymbianSigned_25_05_2007 MobismaME.sis

------------------------------
File format : SISX (V9)
SIS file : MobismaME.sis
------------------------------
Symbian Signed : No
Developer Certificate Signed : No
ACS Publisher Signed : No
Unknown Certifictaes : 1
------------------------------

Z:\Installs\mobismaSRV\expresssigned>pause
Tryck ned valfri tangent för att fortsätta...

Z:\Installs\mobismaSRV\expresssigned>signsis.exe MobismaME.sis -o

Primary:
Issued by TC TrustCenter Class 2 L1 CA XII.
Issued to Development.
Valid from 16/02/2011 to 16/02/2012.

Z:\Installs\mobismaSRV\expresssigned>pause
Tryck ned valfri tangent för att fortsätta...

Z:\Installs\mobismaSRV\expresssigned>C:\Program\7-Zip\7z.exe a -tzip expressigne
dnew.zip readmenew.txt mobisma.pkg MobismaME.sis mobismaMEPSnew.pdf

7-Zip 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Scanning

Creating archive expressignednew.zip

Compressing mobisma.pkg
Compressing MobismaME.sis
Compressing mobismaMEPSnew.pdf
Compressing readmenew.txt

Everything is Ok
[/QUOTE]

With VerifySymbianSigned_25_05_2007 i Get

[QUOTE]ACS Publisher Signed : No
Unknown Certifictaes : 1[/QUOTE]

But with signsis -o I get

[QUOTE]Primary:
Issued by TC TrustCenter Class 2 L1 CA XII.
Issued to Development.
Valid from 16/02/2011 to 16/02/2012.[/QUOTE]

Could this be a problem?

I never used the VerifySymbianSigned_25_05_2007 to be fully honest, thus would not know what it is, also I suppose if the file name indicates a date, then the TC certificates were added to Symbian signed after that specific date. Anyway, what are the steps, and what is the actual outcome ?

I want to make a expresssigned sis from the Symbian signed site. In order to do that you need a TC Publisher certificate from Trustcenter.de
I have received that and then you must use an export-tool (TCP12P8) and divide your certificate in a key-file and a cer-file. wich I have done
as this [QUOTE]tcp12p8 mobismanew.p12 xxxxxx mobismanew.key mobismanew.cer[/QUOTE]
where xxxxxx is my certificate password
Then you sign your sis file with that certificate
[QUOTE]signsis.exe mobisma.sis MobismaME.sis mobismanew.cer mobismanew.key xxxxxx [/QUOTE]
After that I verify the file as I described and pack it all to a zip file wich I try to upload to the Expresssigned Application submission form
located at [url]https://www.symbiansigned.com/app/page[/url]
But when I do that I olny get "null" as error message....

Here is the link to VerifySymbianSigned_25_05_2007
[url]http://wiki.forum.nokia.com/index.php/File:VerifySymbianSigned_v2.4.zip[/url]

I was asking the excat steps on utilizing the symbian signed, i.e. what do you pack in zip file and how you are submitting it ?

I did see this.
[QUOTE]Warning: VerifySymbianSigned tool will not recognise Publisher IDs issued after 1st December 2009. This is because the intermediate certificate used to check the signature of the sis file has been changed. Instead use the latest version of the signsis tool with the -p flag to see that your sis file has been signed with a valid Publisher ID.[/QUOTE]

So I tried this, but it does not really make any sense to me if the certificate is ok or not...

[QUOTE]Z:\Installs\mobismaSRV\expresssigned>signsis MobismaME.sis -p -o

Primary:

Certificate:
Data:
Version: 3 (0x2)
Serial Number:
5e:9a:00:01:00:02:48:fb:21:50:1e:ea:60:58
Signature Algorithm: sha1WithRSAEncryption
Issuer: CN=TC TrustCenter Class 2 L1 CA XII, OU=TC TrustCenter Class 2 L
1 CA, O=TC TrustCenter GmbH, C=DE
Validity
Not Before: Feb 16 11:16:23 2011 GMT
Not After : Feb 16 11:16:23 2012 GMT
Subject: CN=Mobisma AB, OU=Development, O=Mobisma AB, C=SE
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public Key: (2048 bit)
Modulus (2048 bit):
00:c5:b2:f6:7a:6e:4d:a4:df:67:f2:cb:46:a0:74:
74:2b:ee:27:a7:f4:97:54:87:53:93:9b:7f:86:0c:
f2:6b:10:90:28:bc:e4:d6:c1:2e:9d:01:fe:78:60:
cc:02:e1:58:21:2e:42:93:2f:0c:42:83:37:a2:3c:
17:45:c1:d9:1f:06:31:e6:9a:8d:b5:b4:c6:23:99:
c8:5a:e3:5d:ed:3d:91:d7:77:5f:42:3d:84:12:af:
76:43:c0:19:37:96:b2:ad:60:f4:40:b3:58:3d:e1:
22:64:1e:ef:ae:4f:ab:11:d6:a2:ca:70:5e:60:ab:
2f:f5:dd:80:89:02:80:3e:e5:99:e7:c0:b0:1d:6a:
ce:dd:e7:e8:1d:55:68:24:ae:d1:95:57:7e:1e:d8:
b4:73:6b:be:e4:77:44:cf:c5:11:24:90:7b:c6:a4:
c4:f1:9e:99:f4:4a:ae:b6:3c:c1:00:39:12:d4:2b:
a6:a3:71:f6:25:31:3f:83:fd:8b:29:2e:7f:c3:17:
27:1c:65:46:ca:12:4f:12:0f:27:92:da:d9:31:b8:
52:22:02:98:92:2e:f1:fa:a4:5c:23:22:1a:17:8a:
51:ed:1e:4f:2a:ad:fb:28:65:f1:e4:9f:15:d0:8e:
43:33:df:49:be:c6:ad:e5:11:f1:ab:52:95:c7:dd:
f1:a9
Exponent: 65537 (0x10001)
X509v3 extensions:
Authority Information Access:
CA Issuers - URI:[url]http://www.trustcenter.de/certservices/cacerts/tc_c[/url]
lass2_L1_CA_XII.crt
OCSP - URI:[url]http://ocsp.xii.tcclass2-ii.trustcenter.de[/url]

X509v3 Authority Key Identifier:
keyid:09:EF:8C:8B:73:03:81:3C:08:3F:8D:7A:B7:84:55:99:BF:70:BC:14

X509v3 Basic Constraints:
CA:FALSE
X509v3 Certificate Policies:
Policy: 1.2.276.0.44.1.1.6.14.2.1
CPS: [url]http://www.trustcenter.de/cps[/url]

X509v3 Key Usage: critical
Digital Signature
X509v3 CRL Distribution Points:
URI:[url]http://crl.xii.tcclass2-ii.trustcenter.de/crl/v2/tc_class2_L1_CA[/url]
_XII.crl

X509v3 Extended Key Usage:
TLS Web Client Authentication, Code Signing
Signature Algorithm: sha1WithRSAEncryption
45:83:4a:d0:67:6c:a1:91:b2:36:ef:a2:90:e2:12:79:0f:1a:
a1:1d:44:e8:37:f5:3d:5a:77:51:9a:c9:16:86:a4:c4:41:27:
54:e7:3e:01:e1:09:c8:d3:4b:6f:2d:f2:71:03:c1:fc:98:40:
5a:30:52:7f:c8:37:72:fc:5a:4f:80:5a:27:a4:d8:bb:cd:3d:
72:79:11:43:a6:cf:40:52:a1:e1:c9:6f:bc:8e:83:7c:f5:e7:
f8:7a:1e:40:38:12:72:70:0b:0e:39:1e:62:c6:78:37:b5:ad:
25:5b:c1:1e:b0:1c:f2:5d:4c:8c:56:8e:be:69:49:fd:f9:38:
97:09:9c:8e:91:df:d2:69:49:7d:57:04:02:1a:b4:c8:3b:0e:
da:0c:96:9a:f6:d4:bd:73:e8:4a:3d:8b:37:24:8d:97:02:d9:
53:a4:16:2d:25:56:83:0c:2e:ce:10:e7:80:3c:67:64:6c:ca:
fc:aa:87:e2:a9:d1:09:f6:d3:bc:06:6a:f8:e5:19:04:2c:bc:
ba:28:56:a1:dd:0e:66:ca:32:71:e6:14:04:32:29:0f:76:cf:
e0:38:51:94:9f:32:32:08:3b:fe:e9:84:ed:46:a0:13:5c:9b:
16:22:f4:72:c9:91:10:75:bd:ee:2e:90:e5:e4:c0:c5:ab:35:
ef:17:24:7f[/QUOTE]

can you please simply answer the questions asked from you, that usually helps on determining what is going wrong..

In my zip file I have the following files

mobisma.pkg
[QUOTE]; Installation file for Symbian OS 9.x for generic console application
; Installation file for AutoStartExample EXE
;
; This is an auto-generated PKG file by Carbide.
; This file uses variables specific to Carbide builds that will not work
; on command-line builds. If you want to use this generated PKG file from the
; command-line tools you will need to modify the variables with the appropriate
; values: $(EPOCROOT), $(PLATFORM), $(TARGET)
;

;
; UID is the exe's UID
;
#{"mobismaSRV EXE"},(0x20027180),3,1,3
;Supports Series 60 v 3.0
[0x101F7961], 0, 0, 0, {"Series60ProductID"}

;Localised Vendor name
%{"mobisma AB"}

;Unique Vendor name
:"mobisma AB"

"C:\Users\Jens\Desktop\Symbian\mobismaconf\mobisma\dbg.txt" -"C:\mobisma\dbg.txt"
"C:\Users\Jens\Desktop\Symbian\mobismaconf\mobisma\mobisma.ini" -"C:\mobisma\mobisma.ini"
"C:\Symbian\Carbide\workspace\mobismaSRV\J2ME\ClamshellCldcPhone1\MobismaME.jar" -"C:\mobisma\mobisma.jar"
"C:\Symbian\Carbide\workspace\mobismaSRV\J2ME\ClamshellCldcPhone1\MobismaDynamic.jad" -"C:\mobisma\mobisma.jad" , FM, "text/vnd.sun.j2me.app-descriptor"
"..\data\programToStart.ast"-"!:\private\10274b9f\import\programToStart.ast"
"$(EPOCROOT)epoc32\data\z\resource\mSRVAutoStart.rSC"-"c:\private\101f875a\import\[20027180].rsc"
;"$(EPOCROOT)epoc32\data\z\resource\mSRVapp_reg2.rsc"-"c:\private\10003a3f\import\apps\mSRVapp_reg.rsc"
"$(EPOCROOT)Epoc32\release\$(PLATFORM)\$(TARGET)\mobismaSRV.exe" -"C:\sys\bin\mobismaSRV.exe",FR,RI
[/QUOTE]

The SIS file
MobismaME.sis
A PDF
mobismaMEPSnew.pdf
A Readme Textfile
readmenew.txt


Then I go to
[url]https://www.symbiansigned.com/app/page/mysymbiansigned[/url]

And choose Express signed

Fill in the form (As I have done previously with my old app without any problems)

And get this result

[IMG]http://www.mobisma.com/img2/symbiansignederr.PNG[/IMG]

What is the ", FM, "text/vnd.sun.j2me.app-descriptor"" in the jad file line ? I never seen such a line on PKG, could be that the sis file parsin thing symbian signed is using gets confused on that. Can you try with Open signed on-line whether you can sign it with that one, as well as does the sis install to the device without problems .

in my openion.... the way you zip the files are wrong.... what you do is drag the pointer on all the 3 files and then Zip again(instead of making a folder putting all the 3 files in it and Zip).... that will solve your problem....

[QUOTE=symbianyucca;846600]What is the ", FM, "text/vnd.sun.j2me.app-descriptor"" in the jad file line ? I never seen such a line on PKG, could be that the sis file parsin thing symbian signed is using gets confused on that. Can you try with Open signed on-line whether you can sign it with that one, as well as does the sis install to the device without problems .[/QUOTE]Me neither until I read a thread today, [url]http://discussion.forum.nokia.com/forum/showthread.php?225460-how-to-convert-jad-file-to-sis-file[/url], it is about automatic installation of Java stuff via a .sis file.
Gena01, just to make sure: does this Java-install magic work at all?