Проблема с DevCert

[truf]

Все уже давно ощутили проблемы с symbiansigned.com.
Вчера я с неудовольствием обнаружил что не могу получить DevCert на новый IMEI.
На сайте:

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.

Но я не заню когда GMT office hours и что такое Open Signed Offline. Подозреваю что запрос нужно отправить письмом, но не ясно куда и в какой форме. Кто-нибудь получал его таким образом? Я спрашивал тут и тут.

На самой странице open signed\request все еще более бескомпромиссно:

New Open Signed Developer Certificate request

The Developer Certificate creation outage has been resolved and the service is ready to been re-enabled. The current demand for Developer Certificates is extremely high (tens of thousands of requests) and has the potential to cause significant site slowdown.
Whilst there remains heavy demand, impacting commercial users for paid Services; Express Signed, Certified Signed, Developer Certificates will be available intermittently until the load is balanced.

После бузуспешных попыток нагуглить Open Signed Offline я решил обновить свой DevCertRequest до 2.1.1. Скачал c developer.symbisn.com и что я вижу в release notes?:

Version 2.3 KM
-----------

Release date: 05/12/2007
Target: Windows 2000, Windows XP, Windows Server 2003
Changelist : 147756
Known issues: None.
Changes :

1. Only able to create .CSR with Publisher ID

Version 2.1.1 KM
-----------

Release date: 30/11/2007
Target: Windows 2000, Windows XP, Windows Server 2003
Changelist : 147345
Known issues: None.
Changes :

1. Included the additional 4 Dev Man Caps you get when using a publisher ID into the 2nd tier.

2. Increased the number of IMEIs you can have in a request with a Publisher ID to 1000.

При том что версия программы все еще 2.1.1.
К этому нас готовят?
Самое обидное что у меня 2 PubID - Verisign и TCTrustCentr и я должен участвовать в этом спектакле?

[Den123]

Весело

Понравилось про светлое будущее:

1. Only able to create .CSR with Publisher ID

А если я freeware пишу ? Мне таки прийдется покупать Publisher ID даже для тестирования на реальных девайсах??? Или я должен буду постоянно через этот самый Open Signed подписываться ?

[truf]

О наконец получил ответ:

Hi,
Apologies for the delay in enabling the service. We anticipate it will be available for users with a Publisher ID within the hour.
Rod (Symbian Ltd.)

Ну хоть владельцы PID смогут подписаться.
BTW мне уже пришла личка на developer.symbian.com

Could you help me and my friends to make a certificate, and we can pay you. If you are interested in it, please reply me.

Народ начинает нервничать...

[truf]

Отсюда.

Appreciate the frustration in the developer community relating to not being able to access Developer Certificates. The Symbian Signed site has been suddenly swamped by traffic in the last few weeks. For some indication of the upsurge see http://www.alexa.com/data/details/tr...biansigned.com

The creation of developer certificates requires a connection to a secure server, which has a capped capacity that has suddenly been exceeded. Our capacity planning, used the assumption that that Developer Certificates are

1. Primarily intended for developers use.
2. Valid for 3 years per IMEI, i.e. effectively only required to be created once per device.

The excessive demand we are experiencing is primarily as a result of non sanctioned scraping tools/wizards/bots automating the creation process. These tools do not take into consideration the architectural constraints of creating DevCerts, are outside of our control and are unfortunately the ultimate cause of the degraded service.

To maintain a QoS, we are in process of providing defensive mechanisms to ramp up traffic and will phase these changes in over next few days.

o Priority will be given to Commercial Developers (who have Publisher IDs) to use Open Signed Offline (i.e. Developer Certificates).
o For non commercial developers (without Publisher IDs) we will accelerate Open Signed Online rollout.

Во всем виноваты хакеры. А не_владельцы PID будут дискриминироваться.
Если Open Signed Offline == Developer Certificates, то видимо Open Signed Online rollout - это отправка sis на сервер за подписью. Или я неправильно понял?

[Den123]

Да

And yes, we know, we did not offer a lot for freeware and open source developers yet. But we did not leave them totally unheard either.

There will be a new signing program called Open Sign. This will allow people to sign applications for 1 single IMEI, ie their own phone (or that is the main idea). This should help those open source and freeware developers who previously have relied on dev certs for distribution. While on the surface Open Signed is very much like dev cert signing for a single IMEI, the big change is the ease of use. As a user now can drop on unsigned app onto the Symbian Signed site and have it signed for his/her phone, without any need to setup and install Carbide, SDK or the like. This should provide many new developers the mechanism to distribute certain application categories to much broader audiences.

http://discussion.forum.nokia.com/fo...d.php?t=118597

[truf]

Да самое интересное в этом посте:

There will be a new signing program called Open Sign. This will allow people to sign applications for 1 single IMEI, ie their own phone (or that is the main idea). This should help those open source and freeware developers who previously have relied on dev certs for distribution. While on the surface Open Signed is very much like dev cert signing for a single IMEI, the big change is the ease of use. As a user now can drop on unsigned app onto the Symbian Signed site and have it signed for his/her phone, without any need to setup and install Carbide, SDK or the like. This should provide many new developers the mechanism to distribute certain application categories to much broader audiences.

Интересно, прикрутят ли они фильтр на крякнутый софт? Было бы неплохо

Я встретил пару заявлений на этом и developer.symbian форуме, что люди поставившие PID в браузер, видят:

Your request has failed. Reason:
Your are not enabled to request DevCerts. Please contact the system administrator.

в Open Signed\Result

Это какой-то рудимент, или они планируют заставить нас еще и в браузер ключи вставлять? Становится все интереснее и интереснее. Одно ясно - люди несут существенные убытки.

EDIT: В общем, что то они там делают. Форма появилась Но пока не работает

[truf]

Вот и дождались. Но странице symbiansigned:

OPEN SIGNED ONLINE BETA AVAILABILITY

For developers without a Publisher ID, we will commence roll-out the Beta version of Open Signed Online at the beginning of next week.

As demand is currently higher than the PKI signing capacity, you may experience some restrictions on availability. We are in the process of adding new PKI signing hardware to the signing service to increase signing capacity (but this will take several weeks to configure)

As outlined below there is a maximum number of requests that we can service each hour which limits the number of users that can request at one time.

Open Signed Online Beta will be available next week with the following restrictions:

* The Open Signed Online process is fully described here
* During initial stages of the Open Signed Online beta, the service may only be available from 0900-1500 GMT (UK time) Monday-Friday.
* Until capacity is increased with additional servers, there is a maximum number of requests that can be serviced each hour, if there is excessive demand (which is expected), some users may find Open Signed Online beta is not available.
* As for any beta, there may be issues that impact the performance and/or functionality of the service. Such problems may result in the service being taken off-line at short notice and/or for extended periods.
* Note: Open Signed Online does not allow you to sign a SIS that uses a UID from the "Protected Range", unless the email address you use for Open Signed Online MATCHES the email address of the account which owns/created the UID.
* If you attempt to sign the same SIS file in rapid succession, the service you receive will proportionally slow down. This is to provide fair access to all.
* Installation of the signed SIS file will be restricted to a single IMEI (i.e. mobile phone) that you enter and valid for 36 months.
* SIS files that have been Open Signed will present a notification upon installation that the SIS file is intended for development purposes only.
* SIS files can be signed for all Platform Security Capabilities except CommDD, MultimediaDD, NetworkControl, DiskAdmin, DRM, AllFiles, TCB.

Замечу, что вот это:

* Note: Open Signed Online does not allow you to sign a SIS that uses a UID from the "Protected Range", unless the email address you use for Open Signed Online MATCHES the email address of the account which owns/created the UID.

Решает проблему подписывания cracked приложений. Очень умно. Возможно, конечно менять UID3 в программе, заново собирать sis пакет. Но это будут единичные случаи, и такой аккаунт можно заблокировать по первой жалобе.

Сам OpenSigned Online находится здесь:
https://www.symbiansigned.com/app/pa...ignedOnline.do