Open Signed Online (BETA) Service Error

[wirefree101]

I write with reference to the newly launched Open Signed service online at:

https://www.symbiansigned.com/app/pa...ignedOnline.do

On checking all required services and uploading the application, the following error generated:

"The .sis file contains capabilities that are not permitted for Open Signed (Online)"

Would appreciate clarification of the error.


Best Regards,

wirefree101

[ltomuta]

What is it not clear about this message (aside from that it should include the list of "illegal" capabilities)?

What capabilities have you granted to your binaries?

[wirefree101]

What is it not clear about this message (aside from that it should include the list of "illegal" capabilities)?

What capabilities have you granted to your binaries?

The application under consideration is wlantools-PyS60 to be found at:

http://www-rp.lip6.fr/~berger/pys60_exts/

The developer of this application listed NetworkServices, ReadUserData, WriteUserData and ReadDeviceData in personal correspondence to me. Signing attempt with these four services yielded in the error:

"FAILURE: Submitted .sis file uses uses capabilites that were not selected"


Next, I checked the capabilities of the .sis file at:

http://www.whythefuckwontmysisfilein...com/index.html

The above URL listed all services. So I checked all the services which finally yielded the error:

"The .sis file contains capabilities that are not permitted for Open Signed (Online)"


Would appreciate advise on how to proceed.

Best,
wirefree

[ltomuta]

You could proceed by not attempting to Open Sign (online) an application unless you are its developer.

[wirefree101]

You could proceed by not attempting to Open Sign (online) an application unless you are its developer.

How do you propose anyone proceeds if they wish to install & try new apps which are 3rd party & in the public domain?

[ltomuta]

The source code seems to be available, use it under license and integrate it with your project.

A release means that no further development is needed and the released package can be installed on the targeted phone by the end user.

If there is a release in the public domain then use it. And let other people know about it. If not, you will have to wait for a release or release it youself, but do it properly.

[wirefree101]

The source code seems to be available, use it under license and integrate it with your project.

A release means that no further development is needed and the released package can be installed on the targeted phone by the end user.

If there is a release in the public domain then use it. And let other people know about it. If not, you will have to wait for a release or release it youself, but do it properly.

Unfortunately, its clear that ltomuta is not familiar with the procedures of Open Signing. Moreover, his recourse to assumptions renders him an expert to nobodys benefit.

As he is not aware, any application that is to be installed on a Symbian 3rd ed. device has to be signed - by a developer, or self-signed by the owner of device.

All my queries are from the point of view of a user. I simply wish to install an application on my phone. As Symbian has rendered the usage of .csr files useless, millions of Symbian-based phone users world-wide are left wanting.

Would appreciate qualified inputs.

Best,
wirefree

[ltomuta]

This concludes my attempts to make you understand the basics: signing is done by a document's issuer not by a document's receiver.

As for the rest of your comments, well, it's a bad start for my day but I will forget about it quickly.

[wizard_hu_]

any application that is to be installed on a Symbian 3rd ed. device has to be signed - by a developer

This part of the sentence is true, the hyphen is not necessary.

or self-signed by the owner of device.

This part is not. If self-signing is enough, it should be also done by the developer - self-signing does not restrict the package to a limited set of devices.
You apparently confuse self-signing with using developer certificates.

[mitts]

The rules of Open Signed are quite clear:

Note that Open Signed Online currently does not allow you to sign a SIS that is "owned" by someone else and hasn't been enabled for Open Signing; i.e. if a SIS uses a UID from the "Protected Range", the email address you use for Open Signed Online MUST match the email address of the account which owns/created the UID.

If you have gotten a .sis file from someone else, it seems unlikely to contain a UID owned by you.

[mike_brock]

Read http://developer.symbian.com/forum/t...rt=21&tstart=0 for what was said yesterday by the person in charge of the recent Symbian Signed changes.

Symbian have said that people developing freeware applications can use a UID from the development/test range and that the end user can then use Open Signing to sign them.

[ltomuta]

Do not believe what you read on a discussion board, this or another one, over what you can read in the legal documents that govern the process.

When submitting a file for signing you must accept a legal agreement that says:

You will only use Developer Certificates for development and testing purposes.

The freeware signing channel is still in place, as nonfunctional as it might be. Use that one for your freeware, like others have done successfully already and please stop abusing the system as this can only have negative effects for all the developers.

[patrickfrei]

Freeware applications can be signed via Open Signed Online. The only thing you have to do as developer is to change the UID to one in the range 0xExxxxxxx (Development use only). If you have the source code you can change it by yourself.

There are already numerous freeware applications available that can be signed now via Open Signed Online, e.g. PhoNetInfo version 1.8.1.

[wirefree101]

Appreciate your patience, Itomuta.

The interests of an honest developer must be protected.

As for the error under consideration, per mitts suggestion, it is related to the usage of UID from protected range. The appropriate error message associated with the same is:

"FAILURE: Submitted .sis file uses a UID that is not allocated to the account holder matching this email address (0xa000#### )"

Hence, the error genetated while attempting to sign wlantools...

"The .sis file contains capabilities that are not permitted for Open Signed (Online)"

...remains nebulous in its intented message.

Best,
wirefree

[Paul.Todd]

Well its probably that Symbian made another change to open signed.
They regressed their previous openeness and the following capabilties are avaliable with a devcert only, but NOT with open signed
CommDD,
MultimediaDD,
NetworkControl,
DiskAdmin

My guess is you are using Network Control or CommDD which will generate this message.

Can you post which of the files you attempted to sign?