Parameter | Description |
| This flag determines whether or not the installation of unsigned packages is allowed. If Notes: · If there is a root certificate marked as · If any of the executables in an unsigned package have system capabilities then the installation is aborted with an error message, even if unsigned packages are allowed. |
| This flag may be used to force end entity certificates to have the X.509 code signing extension (see RFC 3280). If If |
| This flag may be used to force all non-root certificates in chains corresponding to the private keys used to sign the SIS file to contain at least one of the OIDs specified in the policy file. If not, the package will not be installed ( If If For example, if it is a requirement that certificates must contain the OID
|
| A list of OIDs, one of which must be present in each of the certificates if the |
| A boolean flag to indicate whether the installation process should allow the installation of DRM protected SIS files. If It is expected that rights will already be available on the device. Where no rights are available, the installation will fail. If The default is |
| If the If The value can be one of: · · · · · · · · · · The default value is 3. |
| This flag determines whether OCSP checking is performed during software installation. If A SIS file can be signed with multiple certificates. If enabled, OCSP checking verifies the current status of the certificates in all chains built from the SIS file. All chains present are checked and must prove valid. Note that failure of the OCSP check does not necessarily cause installation to fail. Transient errors in verification (for example due to network problems) may be permitted, depending upon the If OCSP indicates that any of the certificates have been revoked, or if the signature on the OCSP response is invalid, a security error will be issued and the software cannot be installed. The OCSP server URI is taken from the corresponding certificate (as long as the chain is trusted). If there is no OCSP server URI specified in a certificate, a default URI is used that is taken from the installation preferences passed to the Software Installer. OCSP responses are considered valid when signed either by a CA that is part of the chain used to validate the SIS file signature or by a root certificate that is installed on the device and explicitly marked as trusted for revocation purposes. |
| If If If |
| This flag determines whether the user can grant user capabilities (as defined by the If If |
| This specifies the list of the capabilities that the user can grant to an executable during the installation of a package if the User capabilities are the set of capabilities whose purpose may be easily understood by a user. The rules governing the installation of a software package containing executables vary depending on whether the executables require user or system capabilities. If a package requires any system capabilities then these capabilities must be endorsed by an appropriate certificate, or installation will fail. In other words, a trust anchor certificate, X, that can grant all capabilities required by the package’s executables must be present in the SWI Certificate Store and the package must be signed with a verifiable EE certificate derived from X. Trust anchor certificates may also endorse user capabilities. Any packages requesting those capabilities and signed with a verifiable EE certificate will also be considered for installation without querying the user. However, if the package requests user capabilities but it is not signed with such a certificate, and if the The standard set of user capabilities is: · Grants access to remote services without any restriction on its physical location i.e. grants access to the phone network. An application that has been given this capability can dial a number, send a text message etc. and thus may incur a cost for the phone user. · Grants access to remote services in the close vicinity of the phone i.e. grants access to the local network. An application with this capability can send or receive information through Bluetooth, USB or IR. In most cases such services will not incur a cost for the phone user. · Grants access to live confidential information about the user and his/her immediate environment. Examples are biometric data (such as blood pressure), audio and video recording. · Grants read access to user data, such as contacts, messaging and calendar data. · Grants write access to user data. · Grants access to the live location of the device. This capability supports the management of the user’s privacy regarding the phone location. Location information protected by this capability can include map co-ordinates and street address, but not regional or national scale information. Note that defining a set of user capabilities in |
| This flag determines whether the user is asked to allow the overwriting of orphaned files in public directories during the installation. A file is considered orphaned if it does not belong to any installed package in the registry. This could be a newly created file or a Symbian OS file not referenced in a ROM stub controller. To allow the overwriting of files in private directories, the Because orphans could potentially be used to block legitimate packages from being installed, the Software Installer allows them to be overwritten if they are 'in the way', but only if the user allows this to happen. If If |
| If The default is |
| When a software package (of type A stub SIS file is one which contains no data units i.e. files or executables. Appending the stub SIS file to a card allows the card to be inserted into another device and the package will be automatically installed. This means that if |
| This specifies the maximum allowed shutdown time in seconds for applications that are required to be shut down during an upgrade or uninstall operation. If the application fails to shut down within this time, the Software Installer shuts it down by killing the process. The default value is 10 seconds. |
| An installation package can specify that a program will run during the installation process (specified using Users of these features should be aware of the following: · If the Software Installer is configured with a positive · With a · Launching a UI application with this mechanism is not recommended because its windows may interact unpredictably with those of the installer UI, or user delay may result in installation/uninstallation continuing regardless. · Using The default value is 3 minutes. |
| This flag determines whether SIS files with no target hardware/UI platform dependencies listed are considered compatible with any target hardware. If If The default is |
| This flag determines whether untrusted applications are allowed to execute via the Note: these directives are not supported for use with The default is |
| This setting allows a device manufacturer to remap the location to which files are installed on the device at install (or restore) time. The syntax is:
Where
For example:
which will cause the following remapping: · · · · · Important Note: ReplacePath only supports the translation of ASCII file-paths. Support for Unicode translation is not currently supported. |
| This specifies a filter that adds HTTP headers to OCSP requests. A filter is an ECOM plugin. This setting is optional. If none is specified then the OCSP request is sent with the default headers. These are The value is the UID of the plugin in hex. For example,
|
| If If Note that configuring this option means that if one user lends an MMC card to another, nothing prevents the second user from inadvertently removing the package from the MMC. |
The early bird catches the worm!
最新推荐文章于 2022-05-07 16:23:22 发布
href="新建%20文本文档.files/filelist.xml" rel="File-List">