Hey everybody, my name is Simon and this is my first post. Just got an N95 and have been reading up all over the internet about what it can do and that. This place looks like a valuable source of knowledge and i probably be hanging around here for a while!!
Well anyway, here is my problem...
First of i would like to start off by appologising for the topic of the post, i have seen there are posts all over the internet about signing applications for personal use and i can understand this can be quite annoying.
Basically i have been trying to get rotateMe.v2.0 signed myself for the past few days. I have followed the guides word by word and i have exactly what i need.
The initial problem i was having was that the self signing part of symbiansigned site was down due to high demand for developer certificates. This didn't bother me at first because i was in no rush for the program and i thought i could wait.
After waiting a few days for the site to be back up i go on it and see its back!! I went on and tried to upload my .csr file and then it gave me back an error message saying that i don't have a publisher id when i created my dev cert request.
So i guess my question is asking anybody on here, firstly if they have a publisher id, and secondly if they wouldn't mind going through the trouble of signing an application for me??
Sorry again for the message about things you have all herd before but i was just wondering if anybody could help me out.
Thanks in advance.
Simon
From the homepage of Symbian Signed ..
MESSAGE FOR DEVELOPERS
- Developer Certificates will be ENABLED for users who have a Publisher ID ONLY. (during GMT office hours)
- ONLY If you used a Publisher ID to create a .csr file with the DevCertCreate tool will you be able to use Open Signed Offline to create a Developer Certificate.
- Developer Certificates are currently DISABLED for users without a Publisher ID. Users who DO NOT have a Publisher ID CANNOT request Developer Certificates or use Open Signed Offline.
In other words .. if you are not a registered developer, with an ID, you cant get a certificate to self sign un-signed apps (like rotate me !) ...
So for the time being it looks like the rest of us will not be able to self sign any of he kewl new apps that people are producing 😞
Basically it appears that open signing has gone tits up. Because of the extremely high volume of people registering with symbiansigned, a publisher id is now required to get apps signed. This means you're going to have to fork out $200 for a publisher id, this is available from https://www.trustcenter.de/cs-bin/PublisherID.cgi/en/155102 the validity is only for 1 year.
I blame the brilliant RotateMe and Nokmote being only available unsigned. Everyone wants it, so everyone bombards symbiansigned who in turn get a bit pissed off with the likes of me wanting a dev cert for only a couple of apps. Sorry but it looks like you've missed the boat.
thanks for the quick reply m8.
yea i understand that, but i was wondering if anybody on this site had a publisher ID so they could sign the app for me.
Thanks
Rattyman wrote:Basically it appears that open signing has gone tits up. Because of the extremely high volume of people registering with symbiansigned, a publisher id is now required to get apps signed. This means you're going to have to fork out $200 for a publisher id, this is available from https://www.trustcenter.de/cs-bin/PublisherID.cgi/en/155102 the validity is only for 1 year.
I blame the brilliant RotateMe and Nokmote being only available unsigned. Everyone wants it, so everyone bombards symbiansigned who in turn get a bit pissed off with the likes of me wanting a dev cert for only a couple of apps. Sorry but it looks like you've missed the boat.
thanks for the input Rattyman. I actually came across that website and wasn't really happy with forking out that much for signing myself a couple of apps, 😮 you know what i mean? 🙄
Sorry I cant help. I too wouldn't fork out $200 for a publisher ID. But I bet some nice developer on this forum would be more than happy to help. Anyone?
bingy_bongy wrote:From the homepage of Symbian Signed ..MESSAGE FOR DEVELOPERS
- Developer Certificates will be ENABLED for users who have a Publisher ID ONLY. (during GMT office hours)
- ONLY If you used a Publisher ID to create a .csr file with the DevCertCreate tool will you be able to use Open Signed Offline to create a Developer Certificate.
- Developer Certificates are currently DISABLED for users without a Publisher ID. Users who DO NOT have a Publisher ID CANNOT request Developer Certificates or use Open Signed Offline.
In other words .. if you are not a registered developer, with an ID, you cant get a certificate to self sign un-signed apps (like rotate me !) ...
So for the time being it looks like the rest of us will not be able to self sign any of he kewl new apps that people are producing 😞
Wonder why this comes . . . !
bingy_bongy wrote:In other words .. if you are not a registered developer, with an ID, you cant get a certificate to self sign un-signed apps (like rotate me !) ...So for the time being it looks like the rest of us will not be able to self sign any of he kewl new apps that people are producing 😞
Actually, as long as you had self signed something before this restriction came into place, the .cer file you created in the process can be used again and again for quite a while (was 6 months initially, but the latest .cer files I made is valid for 3 years), so you will still be able to sign new applications.
The .cer files are tied to the IMEI though, so not very helpful for people who had never signed anything before...
This sucks.... they need to pick rotateme as one of those free signed apps!! everyone wants it! me included.
I agree it sucks.
Their excuse on the upload page is that the 'load is too high' and causes an overall slowdown for the rest of the site, particularly their corporate customers.
I don't buy their argument at all though, any half competent systems administrator wouldn't either. 10,000 signing requests per day wont even put a ripple in the CPU stats for a modern server, bandwidth requirements are insignificant for the likes of a company such as 'Symbian'
This is corporate greed driven by some halfwit swill up at the top that absolutely believes that these 10,000 hits could be converted to cash.
Looks like the swipolicy.ini file is about to get some more attention.
Thanks for all the information every body..
dchky wrote:I agree it sucks.
Looks like the swipolicy.ini file is about to get some more attention.
what is this swipolicy.ini?
This post is for information only, please don't interpret it to mean I condone hacking or any illegal or immoral (depending upon your value of morals) activities, because I don't, and that is not my intention here.
swipolicy.ini is a rather complex file stored in your phone Z:/system/data/swipolicy.ini
Essentially it's a file that the installer checks to determine which applications can be installed on your phone. This is how the sleazy phone companies lock you in to installing only their software.
There are various settings for this file that are well documented on the symbian website. Perhaps the best example of the power available to this file would be a tweak to the option 'AllowUnsigned' - setting this to 'true' would give you the ability to install any compatible program without the need to have it signed, at all!
Additionally you could elevate the capabilities of the programs you can install by making a few alterations to give yourself AllFiles, TCB, and so on. For example, say you wanted your file manager to be able to browse sys and private folders, you would give your browser AllFiles capability, since you've already tweaked your swi file, the installer goes ahead and installs the program without problem. You now have access to every directory on your phone.
It also allows for some pretty handy things like setting your own color operator logos - animated mbm files work here too, so the cool factor is high.
Remove unwanted built in applications that you never could before, simply by removing them from the file system directly (this requires a server app with TCB, but easily done)
In my view it turns the phone in to the computer that Nokia said the phone had become! 😊
very interesting post.. i don't suppose there is any chance that you could delve into this information on how to do it a bit more?
i understand if you cant.
UPDATE FROM SYMBIANSIGNED:
- Open Signed Online and Offline for users without a Publisher ID will NOT be available temporarily, an update will be provided during Week beginning 25th Feb.
so what exactly does this mean to us people without a publisher id?
does it mean that me might possibly see the self signing feature back up soon?
Not much to tell at the moment for the N95 with regard to the swipolicy.ini file. What prevents it from being modified at the moment are a series of CRC's that look to be using non-standard polynomials, the CRC's are a little scattered throughout the firmware file and they are a tad difficult to calculate, but there are a handful of people working on that.
Open Signed Online will be for people wanting to sign their applications free of charge, this would be where the thousands of people who want rotateme and other homebrew applications converted to whatever magic format that will 'just work' on their phones. I suspect that this aspect is driven primarily by corporate backed developers who want to reduce piracy of their applications (understandable), but it also helps to line the pockets of both Symbian and the company handing out developer ID's.
The Offline version is pretty much identical to what people were doing up until a few days ago, make a key, upload it to symbian signed, get a certificate back and use that to sign the application. This will now require a publisher ID though.