hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.11.4.1 MPEG/GEM specific service | The following methods used in the present document shall accept or return instances of Objects which describe GEM services and PSI-only services. Methods which accept a locator for a MPEG/GEM service as an input parameter shall also accept all other GEM locators which include the information to identify a service. If p... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.11.4.2 Generic service | The following methods used in the present document shall accept or return instances of Objects which reference generic services. These methods are also required to accept or return the same locators as in the previous clause. • javax.tv.service.navigation.LocatorFilter - constructor; • javax.tv.service.navigation.Locat... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.11.4.3 Stored services | The following method used in the present document shall accept or return instances of Objects which describe a stored service: • org.dvb.application.storage.StoredApplicationService.getLocator.javax.tv. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.11.4.4 Content referencing for IPTV | All the methods listed in clauses 11.11.4.1, "MPEG/GEM specific service" and 11.11.4.2, "Generic service" of the present document shall accept or return instances of Objects which describe unicast and multicast GEM IP services. • service.Service.getLocator - when the Service is a StoredApplicationService. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.11.4.5 Content referencing for OTT services | All the methods listed in clauses 11.11.4.1, "MPEG/GEM specific service" and 11.11.4.2, "Generic service" of the present document shall accept or return instances of Objects, which describe OTT services addressed by HTTP locators. An HTTPLocator is defined as described in table 60 and detailed in the Annex AU extension... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.12.2.1 Stored application APIs | This is defined in Annex AG, "Stored application APIs" of the present document. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.12.2.2 Modified behaviour of GEM 1.0 APIs | The following APIs defined in GEM 1.0 shall have extended semantics to support listing and launching of stored services as defined in clause 9.6.2, "Stored services". The modifications to these APIs are as follows: • The class javax.tv.service.navigation.ServiceTypeFilter when used with a ServiceType "org.dvb.applicati... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.12.2.3 Permissions | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.12.2.3.1 FilePermission | A read permission shall be granted for the subtree corresponding to the outermost (top level) directory listed in the application description file and recursively all directories below that. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.12.2.4 Stored application management API | This is the org.dvb.application.privileged package defined in Annex AT, "Application Management API". 11.13 Void 11.14 Internet Access 11.14.1 Internet client control APIs These are defined in the org.dvb.internet package (see Annex AH, "Internet client APIs"). Internet clients accessible to GEM applications shall appe... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.14.2.1 HTML tags | Internet applets shall be supported using the "<applet>" and "<object>" tag with the semantics defined in HTML 4 [68]. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.14.2.2 Java Platform | The Java platform for Internet applets shall be PP 1.1 [76]. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.14.2.3 Void | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.14.2.4 Void | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 11.14.2.5 Security | The present document does not require support for signed applets or for the code signing mechanism and APIs as defined in PP 1.1 [76]. If applets can access Java APIs defined as part of clause 11, "DVB-J platform", apart from those listed in clause 11.14.2, "Internet applet support", they shall have the permissions req... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12 Security | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.1 Introduction | This clause covers the following areas of security: • Authentication of applications. • Security policies for applications. • Authentication and privacy of the return channel communications. • Certificate management. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.1.1 Overview of the security framework for applications | The security framework enables a receiver to authenticate the source of application code or other files. In the case of application code files, the authentication advises the receiver what access rights should be granted to an application for sensitive resources, see clause 12.6, "Security policy for applications" for ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.1.2 Overview of return channel security | In this version of the specification general purpose protocols and a standard cryptographic suite derived from internet standards are used. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.1.3 Establishing trusted applications | One mechanism by which an application may be trusted, and thus request additional permissions, is for that application to be signed. Terminal specifications based on GEM may introduce additional mechanisms for establishing that an application is trusted. These mechanisms may involve some form of codesigning. Any securi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.2 Authentication of applications | For profiles and/or targets that do not require compliance with the functional equivalent named "application authentication" as defined in clause 15.6, "Functional equivalents", GEM terminal specifications may define a functional equivalent for authentication of applications. This functional equivalent shall provide a ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.2.1 Overview of authentication messages | Three different message types are used: "Hash codes", "Signatures" and "Certificates". Each message is placed in a file. The placement of the files depends on their function and is specified under the appropriate headings under clause 12.4, "Detail of application authentication messages". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.2.1.1 Hash codes | The present document describes application of hash codes to the following types of information: • Files. • Directories. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 187 The hash computation considers the content and attributes of the objects rather than transport specific information. As a result, the authentication is indepe... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.2.1.2 Signatures | The data authenticated is a hierarchical file system (for example DSM-CC OC). The root of an authenticated "tree" carries one or more signatures. This allows one or more organizations to sign a set of information. The root of the authenticated "tree" can be the root directory of the file system or the "top" directory o... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.2.1.3 Certificates | The certificate provides a public key that can be used to decode a hash code contained in a signature and so enable a tree/subtree to be verified. The certificate itself is signed by a higher certification authority. To correctly authenticate a subtree there must be a valid "chain" of certificates from the signature to... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.2.1.4 Authentication of hierarchical file systems | The solution here is based on authentication of a hierarchical structure of objects. Hashcodes are computed systematically and accumulatively across some or all of the objects in the hierarchy. A signature at the top of the hierarchy identifies the source of the objects. The framework provides a flexible and non-time c... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.3 Message transport | The authentication messages are transported in files. In no cases shall a service transfer be required to access the file content. In the case that the file system is an object carousel this means that the IOR for the authentication message files shall always use a BIOP profile body and never a Lite options profile bod... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4 Detail of application authentication messages | NOTE 1: In the case where the MHP application authentication mechanism is used, the exact file names, locations and syntaxes described in this clause is supported. This includes the requirement in clause 12.4.3.1 that the last certificate in a CertificateFile be the root certificate. NOTE 2: As specified in clause 12.2... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.1 HashFile | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.1.1 Description | The HashFile lists all of the elements of the current directory except itself, and possibly except signature files as described in the following. On transport protocols supporting the listing of files in a directory (e.g. Object Carousel), signature files shall either all be listed with a digest type of non-authenticat... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.1.2 HashFile location and naming conventions | An application comprises files containing data that can be spread across various directories and is contained within a subtree of the file hierarchy. A HashFile will be put in each directory containing objects that need to be authenticated. The name of the HashFile shall be: "dvb.hashfile" There shall only be one insta... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.1.3 Digest value computation rules | The digest value is computed over the objects named in the HashFile in the order listed in the HashFile. The length of the list of objects associated with each digest value may be one or more. Each list of objects may contain an arbitrary mix of different object types (e.g. a mixture of file and directory names). The d... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.1.3.1 Example | Consider two files file1 and file2 and one directory dir1. Using digest type 3, the digest value of file1 + file2 + dir1 is equal to: SHA-1 ( (uimsbf 32) 1 + (uimsbf 32) FileLength ( file1) + contents of file1 + (uimsbf 32) 1 + (uimsbf 32) FileLength(file2) + contents of file2 +(uimsbf 32) 0 +(uimsbf 32) FileLength(Has... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.1.4 Warning concerning grouping of objects under a single digest (informative) | Broadcasters should be made aware that during the construction of the object carousel, grouping objects under one digest can significantly and adversely affect the performance and memory requirements of an application on a terminal. For example, if three objects are grouped under the same digest, implementations must l... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.1.5 Special authentication rules | a) For objects which are directories, if the digest_type is non-zero there shall be a HashFile in the sub-directory listed. If the HashFile is absent then the authentication fails. b) Each HashFile shall provide a complete list of all the objects named in the directory except itself and any possible signature files men... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.2 SignatureFile | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.2.1 Description | The SignatureFile is a File containing one digital signature. It contains the following ASN.1 DER structure: Signature ::= SEQUENCE { certificateIdentifier AuthorityKeyIdentifier, hashSignatureAlgorithm OBJECT IDENTIFIER, signatureValue BIT STRING } certificateIdentifier : As defined in the ITU-T Recommendation X.509 [... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.2.2 SignatureFile location and naming conventions | The SignatureFile is located in the root directory of the subtree that it signs. There can be several SignatureFiles, as there can be several entities that sign the structure. See clause 12.4.4, "Integration". By convention, the name of a SignatureFile is: "dvb.signaturefile."<x> where the <x> is a textual representati... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.2.3 Supported algorithms | Signing data is a two-step process: a) First a hash is computed over the data. b) The resulting hashvalue is then encrypted using an encryption algorithm. As indicated in clause 12.4.1, "HashFile," GEM defines two possible hash algorithms: MD5 and SHA-1. The encryption algorithm used to compute the signature is indicat... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.2.4 Signature computation rules. | The hash is computed over the content of the HashFile contained in this root directory. NOTE: This is the same principle as for the classical hash computation described in clause 12.4.1.3, "Digest value computation rules". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.2.5 Authentication rules | See signatureValue. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 193 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.3 CertificateFile | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.3.1 Description | The CertificateFile contains all of the certificates in the certificate chain up to, and including, the root certificate. The leaf certificate is placed first in the file. The last certificate in the file is the root certificate. The root certificate is included in this file only for consistency. How the GEM terminal d... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.3.2 ASN.1 encoding | The basic specification of the ASN.1 DER encoding used in RFC 2459 [54] is given in ASN.1 [53]. However, RFC 2459 [54] defines some extensions which are required to implement GEM. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.3.3 Supported algorithms | There are various algorithm identifiers in the certificate structure. The OID of the algorithm used in the SubjectPublicKeyInfo structure shall be RSA. The values for AlgorithmIdentifier used both in the certificate structure and in the TBSCertificate structure that are supported in GEM are listed under clause 12.5.1, ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.3.4 Name matching | The only allowed encoding of attributes of distinguished names shall be UTF8String. NOTE: The use of this encoding allows name matching to be a binary comparison. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.3.5 CertificateFile location and naming conventions | As described in clause 12.2.1.3, "Certificates", a key can be authenticated through a "certificate chain". A certificate chain is a hierarchy of certificates that enable the implementation to verify the validity of the key used to check a signature. However, for consistency, the file shall carry all of the certificate ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.3.6 Authentication rules | Certificates are considered to be the same if they have bitwise identical contents. Where a GEM application is authenticated by multiple signature file / certificate file pairs, the GEM terminal shall check all the signature file / certificate file pairs before deciding that a file fails authentication. It is dependent... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.4.4 Integration | Logically a file is authenticated as follows: a) Confirm that the file is listed in the hash file located in the same directory as the file to be authenticated. b) Verify that the file contents and the corresponding digest value are consistent. c) Recursively ascend the directory hierarchy checking that the hash file i... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5 Profile of X.509 certificates for authentication of applications | This clause identifies how ITU-T Recommendation X.509 [51] is profiled when used for authentication of broadcast GEM applications. This profile is a variation (in general a sub-set) of the internet profile defined in RFC 2459 [54]. This clause identifies the differences from the profile in RFC 2459 [54]. Clause 12.11, ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.1 signatureAlgorithm | GEM supports 2 signature algorithms: MD5 with RSA and SHA-1 with RSA. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.1.1 MD5 with RSA | The signature algorithm with MD5 and the RSA encryption algorithm is defined in RFC 2313 [52]. As defined in RFC 2313 [52], the ASN.1 OID used to identify this signature algorithm is: md5WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 4 } |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.1.2 SHA-1 with RSA | The signature algorithm with SHA-1 and the RSA encryption algorithm is implemented using the padding and encoding conventions described in RFC 2313 [52]. The message digest is computed using the SHA-1 hash algorithm. The ASN.1 object identifier used to identify this signature algorithm is: sha-1WithRSAEncryption OBJECT... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.1.3 parameters | For both of the two supported algorithms the parameters component shall be the ASN.1 type NULL. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.2 signatureValue | The RSA signature generation process and the encoding of the result is described in detail in RFC 2313 [52]. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.3 version | The version field of the certificate shall signal v3. All implementations shall support the v3 extensions as required by clause 12.5.9, "Extensions". ETSI ETSI TS 102 728 V1.2.1 (2011-09) 196 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.4 issuer | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.4.1 minimum requirement | For GEM at least a Common Name attribute shall be provided. The text value of the attribute shall be non-empty. It shall be suitable for direct presentation to the user. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.4.2 certificate authority responsibility | The senior certificate authority who signs a certificate shall oversee the attribute information to ensure that the information is suitable. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.5 validity | The only allowed format for encoding time in the validity field is GeneralizedTime. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.6 subject | The subject field is a "distinguished name". The following requirements are specified by GEM: • The only allowed encoding attributes of the subject is UTF8String (see clause 12.4.3.4, "Name matching"). • The minimum set of attributes that shall be present in the subject are: - commonName - countryName • If the certific... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.7 SubjectPublic Key Info | GEM supports a single public key algorithm (RSA) for the subject public key. The key lengths that implementation are required to support are addressed in Annex G, "Minimum platform capabilities". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.7.1 rsaEncryption | The OID rsaEncryption identifies RSA public keys: rsaEncryption OBJECT IDENTIFIER ::= { pkcs-1 1} pkcs-1 OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) 1 } The parameters field shall have ASN.1 type NULL. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.7.2 subjectPublicKey | The RS subjectPublicKey BIT STRING shall be encoded using the ASN.1 type RSAPublicKey: RSAPublicKey ::= SEQUENCE { modulus INTEGER, -- n publicExponent INTEGER -- e -- } The semantics of the modulus (n) and the public exponent (e) are defined in RFC 2313 [52]. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.8 Unique Identifiers | X.509 defines the issuerUniqueID and subjectUniqueID extensions. CAs conforming to this profile shall not generate certificates with unique identifiers. GEM terminals conforming to this profile are not required to be capable of parsing unique identifiers and making comparisons. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.5.9 Extensions | The following restrictions and semantics are placed on the use of certificate extensions when used to authenticate applications. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 198 Table 47: Profile for standard certificate extensions Extension In broadcasts In implementa tions Semantic Authority key identifier Opt. Opt. Shall n... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6 Security policy for applications | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.1 General principles | As described in clause 12.1.3, mechanisms other than MHP codesigning may be used to determine if additional permissions should be granted to applications. As a consequence, in clause 12.4 the term "signed application" is to be interpreted as meaning an application that has been packaged in such a way that it is eligibl... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2 Permission request file | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.0 General | The following rules shall apply for the processing of PRFs by a GEM terminal: 1) If there is only a DVB PRF present, the GEM terminal shall use it. 2) If there is a platform-specific PRF (e.g. an OCAP PRF) present on the corresponding target platform (i.e. an OCAP terminal), then the GEM terminal shall use it exclusive... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.1 File encoding | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.1.1 XML | The Permission Request File is an XML File. Its syntax is defined by the following DTD. The Name used in the document type declaration shall be "permissionrequestfile". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.1.2 MHP/GEM 1.0 | The PublicLiteral to be used for specifying this DTD in document type declarations of the XML files is: "-//DVB//DTD Permission Request File 1.0//EN" and the URL for the SystemLiteral is: "http://www.dvb.org/mhp/dtd/permissionrequestfile-1-0.dtd". The DTD is: <!ELEMENT permissionrequestfile (file?,capermission?,applife... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.1.3 MHP/GEM 1.1 | The PublicLiteral to be used for specifying this DTD in document type declarations of the XML files is: "-//DVB//DTD Permission Request File 1.1//EN" and the URL for the SystemLiteral is: "http://www.dvb.org/mhp/dtd/permissionrequestfile-1-1.dtd". The DTD is: <!ELEMENT permissionrequestfile (file?,capermission?,applife... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.1.4 MHP/GEM 1.2 | The PublicLiteral to be used for specifying this DTD in document type declarations of the XML files is: "-//DVB//DTD Permission Request File 1.2//EN" and the URL for the SystemLiteral is: "http://www.dvb.org/mhp/dtd/permissionrequestfile-1-2.dtd". The DTD is: <!ELEMENT permissionrequestfile (file?,capermission?,applife... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.1.5 Number representation | 12.6.2.1.5.1 Hex Unless stated otherwise (e.g. clause 14.5, "Text encoding of application identifiers") each hexadecimal value has the following form "0x" Nhex where "N" specifies the fixed number of significant digits in the value and hex is specified by the following BNF: hex = digit | "A" | "B" | "C" | "D" | "E" | "... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.2 File integrity | If the permission file is not parsable as defined by the XML parsing rules (see clause 14.3, "XML notation") it shall be ignored and hence no additional permissions are granted (or not granted in the case of SelectPermission). |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.3 Example | <?xml version="1.0"?> <!DOCTYPE permissionrequestfile PUBLIC "-//DVB//DTD Permission Request File 1.0//EN" "http://www.dvb.org/mhp/dtd/permissionrequestfile-1-0.dtd"> <permissionrequestfile orgid="0x000023d2" appid="0x4020"> <file value="true"></file> <capermission> <casystemid id="0x1111" messagepassing="true" entitle... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.4 Permission request file name and location | The format for the permission request file name is: 'dvb.'<application name>'.perm' The prefix "dvb" identifies this as a well known file specified by GEM. The portion "application name" carries the file name of the initial file of the application excluding any file name extension or suffix. The initial file depends on... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.5 Permission Request file | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.5.1 Minimum permissions | If the permission file does not contain a valid permissionrequestfile element it shall be ignored and hence no additional permissions are granted (or not granted in the case of SelectPermission). |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.5.2 Syntax and semantics | <!ATTLIST permissionrequestfile orgid CDATA #REQUIRED appid CDATA #REQUIRED > orgid: This attribute is a hexadecimal string (hex_string) that conveys the organisation id of the associated application. The encoding of this value is specified in clause 14.5, "Text encoding of application identifiers". appid: This attribu... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.5.3 Defaults | NOTE: As defined by XML 1.0 [59], the defaults for attributes defined in the DTD (see clause 12.6.2.1, "File encoding") only apply when the element is present but the attribute concerned is omitted. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.6 Credentials | Support for this mechanism is optional. Since the "signature" and "certchainfileid" element documented in table 50 is dependent on security files used in the MHP application authentication mechanism, stated elements may be modified depending on the application authentication mechanism used. Thus, GEM terminal specifica... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.7 File Access | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.7.1 Unsigned applications | Unsigned applications have no access to the persistent storage. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.7.2 Policy for signed applications | No access to the persistent storage, unless otherwise indicated in the Permission File. Applications may request access to persistent storage either by credentials or the "file" element or both. These two mechanisms are independent. Once an application has access to a file granted by one mechanism, the other mechanism ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.7.3 Permission request syntax | <!ELEMENT file EMPTY> <!ATTLIST file value (true|false) "true" > |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.8 CA API | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.8.0 GEM Introduction | This clause discusses the permissions for conditional access. As discussed in clause 11.10, "Java permissions" of the present document, the class CAPermission is not required to be present for GEM terminal specifications that do not include the functional equivalent named "conditional access" as defined in clause 15.6,... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.8.1 Unsigned applications | An unsigned application cannot access the following methods: • CAModule.buyEntitlements • CAModule.openMessageSession • CAModuleManager.addMMIListener • CAModule.queryEntitltements ETSI ETSI TS 102 728 V1.2.1 (2011-09) 211 • CAModule.listEntitlements |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.8.2 Signed applications | By default, an application has limited access to the CA API functions (same default rights as an unsigned application). In particular, the following method calls are not accessible to an unsigned application: • CAModule.buyEntitlements • CAModule.openMessageSession • CAModuleManager.addMMIListener • CAModule.queryEntit... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.8.3 Conditional Access Permission syntax | The ConditionalAccess Permission is optional. When not present, the application has the default access rights. When present, the permission request file overrides the default rights for this application. <!ELEMENT capermission (casystemid)+> <!ELEMENT casystemid EMPTY> <!ATTLIST casystemid entitlementquery true|false) ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.9 Application lifecycle control policy | Applications shall not launch broadcast applications that are not signalled in the currently selected service for the service context in which the application wishing to do the launching is running. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.9.1 Unsigned applications | An unsigned broadcast application can launch any application visible in the listing API that is signalled in the currently selected service for the service context in which the application wishing to do the launching is running. An unsigned application can control (pause, stop, resume) the lifecycle of an application i... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.9.2 Default policy for signed applications | By default, a signed application has the same rights as an unsigned application as concerns the application lifecycle control policy. These default rights can be overridden by the permission request file as described below. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 212 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.9.3 Syntax | <!ELEMENT applifecyclecontrol EMPTY> <!ATTLIST applifecyclecontrol value (true|false) "true" > value: When the boolean value is set to true, this means that the application can control the lifecycle of all the applications signalled in the currently selected service for the service context in which the application wish... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.10 Return channel access policy | NOTE: The return channel access policy and permission described in this clause are required to be supported. Attention is drawn to the note at the end of clause 12.6.1, "General principles" relating to the return channel permission and return channel connections where it is not necessary to dial a phone, e.g. cable mod... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.10.1 Unsigned applications | An unsigned application may not use the return channel. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.10.2 Signed applications | By default, a signed application may not access the return channel, unless otherwise specified by the permission request file. The syntax of the return channel permission is so that it describes the phone numbers that the application may try to dial. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.