Version 1.0 provides3 signature modes:
1) Symbian Developer Certificate
By signing the sis file with the Symbian developer certificate, you can have 13 permissions that developers usually test (LocalServices, NetworksServices, UserEnvironment, WriteUserData, ReadUserData, ProtServ, SwEvent, Location, PowerMgmt, ReadDeviceData, SurroundingsDD, TrustedUI, WriteDeviceData), This function does not require registering a Publish ID account, but only one Sis file can be submitted at a time. An email is required to receive the signed sisx file. It is also subject to IMEI restrictions, so users are required to fill in their own IMEI and valid email when submitting to accept Nokia The signed installer is sent from the official self-service signing system. This process is completely free.
Since Symbian uses SSL's HTTP or HTTPS protocol, we do not provide an automatic submission function. sbsjw.com has decided to provide an automatic form filling function in the next version. For detailed usage, please refer to the subsequent steps of the S60 developer certificate application method.
2) Self-signed. There are only low-privilege general certificates here. The current software integration certificate is created by sbsjw itself and includes LocalServices, NetworksServices, UserEnvironment, WriteUserData, and ReadUserData permissions. The certificate is valid until November 6, 2010. We will In the next version, a longer certificate will be added, or a certificate creation function will be added. The program signed here does not support the use of underlying tools, such as those that need to run automatically at boot.
3) Customize cer and key files
Some netizens may have purchased a high-privilege certificate or their own low-privilege certificate through the certificate production section of major domestic forums. Users only need to select their own cer and key files to sign. In the next version, we will add a password recognition function. (Most certificates do not have passwords).
it works
it works
it works