Account Verification Problem

[TheOtherUser]

Hi there,

as stated in the titel i have some problems with the verification of my account. We have got a Publisher ID and we have got an application signed with the resulting certificate.

The first problem was the extension of our application, i got a verification error because it was named "*.sisx" instead of ".sis", the failure description was misleading but i found the solution for that here at the forum...

The second problem was that my cer file contained two certificates at the same time, so i got:

Failed to verify Publisher ID due to certificate validation error

So i seperated it into two files an signed the example file from symbian signed (symbian_signed_account_verification.sis) again, tried both certificates and still i get the error:

Failed to verify Publisher ID due to certificate validation error

This is what i get with signsis -o -p

Primary:

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
...
        Signature Algorithm: sha1WithRSAEncryption
        Issuer: C=GB, ST=London, L=Southwark, O=Symbian Software Limited, CN=Symbian Developer Certificate CA 280205A/em
ailAddress=developercertificates@symbian.com
        Validity
            Not Before: Mar 31 14:50:09 2011 GMT
            Not After : Mar 31 14:50:09 2014 GMT
        Subject: C=DE, L=Munich, O=Rohde & Schwarz GmbH & Co.KG, OU=Symbian Signed PublisherID, CN=Rohde & Schwarz GmbH
& Co.KG, ST=Bayern
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
            RSA Public Key: (2048 bit)
                Modulus (2048 bit):
...
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            1.2.826.0.1.1796587.1.1.1.1: critical
...
            1.2.826.0.1.1796587.1.1.1.6: critical
                ...m.......
    Signature Algorithm: sha1WithRSAEncryption
...

Any Ideas?

Thanks

[TheOtherUser]

Okay, i tried once more in serveral ways, like stated in the sticky thread:

With signsis.exe (ships with the native SDK - must be in your PATH or in the same dir as your .sis) on your command prompt:

> signsis symbian_signed_account_verification_sis.sis signed.sis yourPublisherID.cer youPublisherID.key

the problem still remeins the same, maybe there is an issue with older versions of signsis.exe or someting like that?

Regards

[ltomuta]

From what I see your SIS is signed with a developer certificate, not with a Publisher ID. Make sure you use the right certificate.

[TheOtherUser]

Oh wow, thats ist.

Thanks a lot, i used the devcert instead of the cert containing my publisher ID.

Thank u very much...

[charlus]

Hi,
I'm experiencing the same problem, however I'm not signing with a developer certificate but with my PublisherCertificate:
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
50:e5:00:01:00:02:1c:07:b6:e6:12:f7:60:d4
Signature Algorithm: sha1WithRSAEncryption
Issuer: C=DE, O=TC TrustCenter GmbH, OU=TC TrustCenter Class 2 L1 CA, CN=TC TrustCenter Class 2 L1 CA XII
Validity
Not Before: Dec 9 13:07:24 2010 GMT
Not After : Dec 9 13:07:24 2011 GMT
Subject: C=FR, ST=IDF, L=Paris, O=Maeglin Software, OU=Production, OU=Symbian Signed PublisherID, CN=Maeglin Software
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public Key: (2048 bit)
Modulus (2048 bit):
00:bb:40:86:f9:dc:55:cf:b5:22:9a:61:ae:7d:f7:
ac:a3:eb:11:82:6e:71:7a:c1:76:c9:c3:7a:7b:5a:
cb:00:01:0a:a9:c5:43:46:50:31:d7:06:22:51:9f:
46:4a:89:49:2e:04:2b:cd:6d:14:c8:03:05:51:52:
41:ea:50:f6:85:2b:7b:81:3e:67:55:c4:ad:92:d5:
7d:8f:ab:c3:4b:ba:83:bc:98:da:c4:d9:10:c1:71:
3e:af:fb:13:ee:4a:5f:5a:98:2a:44:02:e7:d7:cc:
7c:33:5b:aa:ef:9b:79:ab:e9:3e:47:7b:00:ae:ea:
b3:9b:da:93:84:4b:f5:cd:52:2f:20:3e:fc:7e:cc:
7d:f6:61:db:46:2a:cb:fc:b9:13:54:ba:b4:37:c2:
21:1f:e9:ec:05:4a:cf:12:6f:21:39:46:f7:0a:bf:
af:3b:7b:ea:cd:77:d7:8d:9d:d9:5a:46:79:f3:14:
f8:be:2a:af:c7:90:22:47:f6:75:b2:86:f0:b8:95:
33:38:c9:0f:3a:a9:a7:ad:b4:5b:f2:1d:ea:c6:39:
31:cb:f8:73:cd:a1:2c:6d:fc:c1:ef:b6:cd:f5:94:
48:d6:c7:c2:f4:c7:e0:1c:64:6c:43:0f:6a:58:f5:
d8:88:44:bd:db:79:5f:67:37:11:33:77:cc:2a:5a:
c5:b7
Exponent: 65537 (0x10001)
X509v3 extensions:
Authority Information Access:
CA Issuers - URI:http://www.trustcenter.de/certservic..._L1_CA_XII.crt
OCSP - URI:http://ocsp.xii.tcclass2-ii.trustcenter.de

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: http://www.trustcenter.de/cps

X509v3 Key Usage: critical
Digital Signature
X509v3 CRL Distribution Points:
URI:http://crl.xii.tcclass2-ii.trustcent..._L1_CA_XII.crl

X509v3 Extended Key Usage:
TLS Web Client Authentication, Code Signing
Signature Algorithm: sha1WithRSAEncryption
4d:98:d8:28:b0:cc:6f:77:8e:8a:f4:c0:df:05:97:ee:e2:0e:
a6:e8:58:e5:5e:1c:b0:9e:b6:8f:87:43:a1:84:3f:07:d6:2b:
55:bf:c2:d4:fe:7f:68:f1:2f:7b:99:8d:7d:9d:fa:2d:a4:fc:
03:7f:f4:b6:65:bd:7d:6b:a0:eb:d6:86:96:df:46:7a:8c:45:
6c:56:0b:d8:48:53:cb:1a:80:3c:b9:f8:d9:b2:41:2b:42:aa:
c4:de:c9:0f:44:23:10:05:09:03:2e:6a:52:2b:ef:78:cf:1e:
38:5f:df:88:66:9b:03:ba:52:a1:3a:f2:9d:5d:b0:da:09:e1:
f0:f7:62:a5:8a:0b:b5:38:cb:79:07:82:40:13:32:38:f3:9f:
66:23:f5:2c:a6:51:a8:cd:65:d7:f0:75:9b:ea:c4:57:10:96:
e9:d5:9b:86:73:4b:29:69:e6:50:e8:69:a5:b5:8a:29:bb:d8:
c2:fb:fd:ae:a2:16:93:97:14:a5:c5:4e:00:ce:9e:4e:ff:3e:
76:e7:5f:f3:79:04:64:17:76:9e:e4:e4:eb:b8:96:60:62:71:
dd:27:73:bd:86:c3:6c:ef:59:78:b4:3d:b6:f5:16:34:40:bf:
ac:c3:fa:42:ec:c6:18:9a:17:fb:a7:07:b2:c1:f3:26:58:b5:
ec:40:8b:2d

I've tried severl times signing & sumbitting the test .sis file and I'm always getting the "Failed to verify Publisher ID due to certificate validation error" error.
Any idea on how to sovle this ?
Thanks