Distributing my own OSS app : which UID range ? Automatic certificate ?

[nono240]

Hi there

I plan to release an OSS port of the GNU HTTP Tunnel for Symbian (in Open C) (coming soon here). Only Network capability is needed. Signing is a new concept for me, despite a lots of reading...
For now, I'm using an UID in Exxxxxxxx range (development range ?), and is self signed with makekeys. Here's the questions :

1- Can I distribute the .sisx with Exxxxxx UID ? If yes, how to be sure it's unique ?
2- Since, I don't have any certificate, makekeys generate one for me, can I distribute my application self-signed using the latter ? If yes, Is there any expiration time (6 month?) or limitation ?

Thanks in advance..

[wizard_hu_]

After registrating on www.symbiansigned.com you can request "unique UID"-s from the A-range. E-range is for development use only (check the FAQ on the same site).
makekeys -view can show you the details of an exisiting certificate. Default validity period of makekeys-generated certificates is 1 year.

[nono240]

Thank you for your precise answer. Since the project is an open source port, I'll distribute sources with E range and the .sisx within the A range. It's a bit messy, no ?

[wizard_hu_]

If you release something - does not matter if it is open/closed free/paid - you should use the release ranges (2 from protected or A from unprotected). In these ranges you can request for UID-s, and they will be unique.
If you release anything (it does not have to be an application, it can be an API too), its UID has to fall in the release range.

[nono240]

Ok, thanks !

I just retrieved an UID in the A range from SymbianSigned.
I updated MMP and PKG to reflect the changes, self-signed with makekeys but the phone say : "Unable to install"

From now, I used UID 0xE12E55B4 (from a Nokia example), which worked. I tried with 0xE12E55B5, but I get the same message as above. Of course, I uninstalled previous version before installing again..

***Build Complete

***Invoking makesis.exe ....
C:\Symbian\9.2\S60_3rd_FP1_2\epoc32\tools\makesis.exe C:\cygwin\home\Nono\gtunnel\httptunnel-3.0.5_S60\_resolvedhttptunnels60.pkg C:\cygwin\home\Nono\gtunnel\httptunnel-3.0.5_S60\httptunnels60.sis -v 
Processing C:\cygwin\home\Nono\gtunnel\httptunnel-3.0.5_S60\_resolvedhttptunnels60.pkg...
Created C:\cygwin\home\Nono\gtunnel\httptunnel-3.0.5_S60\httptunnels60.sis

...No key/cert defined. Generating dummy key/cert for self-signing (key-gen.key/cert-gen.cer)...
No passphrase defined. Using: "DefaultPassword"

***Invoking makekeys....
C:\Symbian\9.2\S60_3rd_FP1_2\epoc32\tools\makekeys.exe -cert -password DefaultPassword -len 2048 -dname "CN=JoeBloggs OR=Acme" key-gen.key cert-gen.cer 
Using existing private key key-gen.key
Created certificate cert-gen.cer

***Invoking signsis.exe....
C:\Symbian\9.2\S60_3rd_FP1_2\epoc32\tools\signsis.exe -v  -s C:\cygwin\home\Nono\gtunnel\httptunnel-3.0.5_S60\httptunnels60.sis C:\cygwin\home\Nono\gtunnel\httptunnel-3.0.5_S60\httptunnels60.sisx C:\cygwin\home\Nono\gtunnel\httptunnel-3.0.5_S60\cert-gen.cer C:\cygwin\home\Nono\gtunnel\httptunnel-3.0.5_S60\key-gen.key DefaultPassword

[kiran10182]

...the phone say : "Unable to install" ...

Then probably you have messed up with UID changes. Anyways here is one blog from Antony: http://blogs.forum.nokia.com/index.p...7&articleId=93

Search for "Unable to install" in entire blog, you would end up with good information, which eventually may help you.

Kiran.

[nono240]

Thanks for this link !

Acocrding to Antony, my problem is :

This message may come up when your installation file (.sis/.sisx) copies files to other application's private folder, i.e. privateuid. Note that Symbian 9 introduces data caging concept, it means you don't have access to other application's private folder.

My mistake were in .pkg file in backup_registration location : I forget to change UID..

; Installation file for GNU Http tunnel application
;
; 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)
;
;Language - standard language definitions
&EN

; standard SIS file header
#{"GNU HTTP Tunnel Client"},(0xA0007795),1,0,0

;Localised Vendor name
%{"Vendor-EN"}

;Unique Vendor name
:"Vendor"

; pips_s60_wp.sis is required
(0x20009A80), 0, 0, 0, {"OpenCRuntime"}
; openc_glib.sis is required
(0x10281F2C), 0, 0, 0, {"GlibRuntime"}

;Supports Series 60 v 3.0
[0x101F7961], 0, 0, 0, {"Series60ProductID"}

;Files to install
;"C:\Symbian\9.2\S60_3rd_FP1_2\Epoc32\release\gcce\urel\htc60.exe" -"!:\sys\bin\htc60.exe"
"$(EPOCROOT)Epoc32\release\$(PLATFORM)\$(TARGET)\htc60.exe" -"!:\sys\bin\htc60.exe"

;text continue
"notice.txt" -"",FT,TC

;required for application to be covered by backup/restore facility 
"backup_registration.xml" -"!:\private\E12E55B4\backup_registration.xml"

THANKS !

[kiran10182]

Thanks for this link !

....
TARGET          htc60.exe
TARGETTYPE      exe
UID             0xA0007795

...
// End of File

...
; standard SIS file header
#{"GNU HTTP Tunnel Client"},(0xA0007795),1,0,0

...
;required for application to be covered by backup/restore facility 
"backup_registration.xml" -"!:\private\E12E55B4\backup_registration.xml"

Some UID problem is there with Backup registration file. Shouldn't it be A0007795 instead of E12E55B4?

Kiran.