hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.10.3 Return channel permission syntax | <!ELEMENT returnchannel (defaultisp?,phonenumber*)> <!ELEMENT phonenumber (#PCDATA)> <!ELEMENT defaultisp EMPTY> The syntax of the phone number string is as defined below. phonenumber = "+" digit digits | digits digits = "" | digit digits digit = "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" The presence of... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.11 Tuning access policy | This clause discusses the permissions for tuning access. As discussed in 11.10, "Java permissions" of the present document, the class TunerPermission is not required to be present for GEM terminal specifications that do not support the "Tuning API" (clause 11.6.3) listed in table 61 of the present document; for such GE... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.11.1 Unsigned applications | An unsigned application may not tune using the Tuning API. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.11.2 Signed applications | By default, a signed application may not tune using the Tuning API. However, the right to tune can be requested with the Tuning permission that can be put in the permission request file. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.11.3 Tuner Permission syntax | The syntax of this permission is as follows: <!ELEMENT tuning EMPTY>< <!ATTLIST tuning value (true|false) "true" > The value true requests the permission to tune using the Tuning API. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.12 Service selection policy | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.12.1 Unsigned applications | Unsigned applications may not select a new service. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.12.2 Signed applications | By default, signed applications can select any new service, unless otherwise specified in the permission request file. Service selection might require return channel access. If an application attempts to do a service selection using a locator that refers to an AIT File delivered over the return channel, and a return ch... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.12.3 Service Selection Permission | The syntax of the service selection permission is as follows: <!ELEMENT servicesel EMPTY> <!ATTLIST servicesel value (true|false) "true" > If no service selection permission is present in the permission request file, the application has the default right, i.e. it can select any service. The value "false" in this item i... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.13 Media API access policy | The media API is inside the sandbox. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 214 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.14 Inter-application communication policy | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.14.1 Unsigned applications | Unsigned applications are allowed to communicate with each other through the inter-application communication API. However, unsigned and signed applications shall only be able to communicate with each-other using the inter- application communication API in the "dvb:/ixc/" namespace. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.14.2 Signed applications | Signed applications signalled in the same service are allowed to communicate with each other through the interapplication communication API. Signed applications shall only be able to communicate with unsigned applications using the inter-application API in the "dvb:/ixc/" namespace. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.15 User Setting and Preferences access policy | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.15.1 Unsigned applications | Read access to: • User Language. • Parental Rating. • DefaultFontSize. • Country Code. An unsigned application cannot access (neither read nor write) other preferences. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.15.2 Signed applications | By default, same as unsigned applications. The permission request file may include items that request read access to all user preferences and/or write access to all user preferences. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.15.3 Permission syntax | <!ELEMENT userpreferences EMPTY> <!ATTLIST userpreferences write (true|false) "false" read (true|false) "true" > True value in the write and read attribute means that the permission for writing and reading, respectively, is requested. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.16 Network permissions | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.16.1 Unsigned applications | Unsigned applications can not have access to the return channel and therefore can not access remote network hosts. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.16.2 Signed applications | For signed applications, the permission request file can contain a set of permissions that specify the hosts and actions for which permissions are requested. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 215 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.16.3 Permission syntax | <!ELEMENT network (host)+> <!ELEMENT host (#PCDATA)> <!ATTLIST host action CDATA #REQUIRED > The two strings that specific the host and the action shall be formatted as specified in the java.net.SocketPermission class as defined in clause 11.8, "Security". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.17 Dripfeed permissions | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.17.1 Unsigned applications | Has no access to drip feed mode. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.17.2 Default policy for signed applications | No access to drip feed mode unless otherwise indicated in the Permission file. When an application is granted access to the drip feed mode, it is able to instantiate a DripFeedDataSource. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.17.3 Permission request syntax | <!ELEMENT dripfeed EMPTY> <!ATTLIST dripfeed value (true|false) "true" > |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.18 Privileged Runtime Code Extension Permission | NOTE: DVB-J prohibits runtime code extension from data sources less secure than the original program code by virtue of the fact that interoperable DVB-J applications cannot directly create a ClassLoader, so this permission does not apply to DVB-J. See clause 11.10.1.4, "java.lang.RuntimePermission" and DVBClassLoader i... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.18.1 Unsigned Applications | Unsigned applications shall be permitted to do runtime code extension with string data from any source. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.18.2 Signed applications with no permission request file | Signed applications with no permission request file shall be permitted to do runtime code extension with string data from any source. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.18.3 Signed applications with a permission request file | By default, a signed application with a permission request file is prohibited from doing any runtime code extension from a string. The permission request file may include items that request the ability to do runtime code extension with internal strings only, or with both internal an external strings. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.18.4 Permission request syntax | <!ELEMENT priviligedrce EMPTY> <!ATTLIST privilegedrce value (internal|external) "internal" > ETSI ETSI TS 102 728 V1.2.1 (2011-09) 216 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.19 Application storage | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.19.1 Unsigned applications | Have no permission to store applications. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.19.2 Default policy for signed applications | By default signed applications do not have permission to store any applications. Permission to store applications can be requested using the permission request file. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.19.3 Permission request syntax | <!ELEMENT applicationstorage (applicationstorageorg)*> <!ATTLIST applicationstorage manageservice: (true|false) "false" createservice: (true|false) "false" deleteservice: (true|false) "false" managecache: (true|false) "false" > manageservice: When set to "true", requests a permission to manage a stored application serv... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.20 Non-CA smart card access | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.20.1 Unsigned applications | Have no permission to access smart cards. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 217 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.20.2 Default policy for signed applications | By default signed applications do not have permission to access smart cards. Permission to access smart cards can be requested using the permission request file. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.20.3 Permission request syntax | <!ELEMENT smartcardaccess EMPTY> When the smartcardaccess element is included in the permission request file, the permission to access smart cards is requested. If the element is not included in the permission request file, this permission is not requested. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.21 Provider Management | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.21.1 Unsigned applications | Have no permission to install or remove providers. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.21.2 Signed applications | By default, signed applications have no permissions to add or remove providers. Permission to insert or to remove a provider can be requested by requested using the permission request file. An application shall only be granted permissions to insert or to remove providers that have the same organisation identifier as th... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.21.3 Permission request syntax | <!ELEMENT provider (name)+ > <!ELEMENT name (#PCDATA)> <!ATTLIST name scope (application|system) "application" > The provider name shall be prefixed with the GEM organisation identifier of the organisation which is in charge of it. The syntax for the GEM orgId shall be compliant with clause 12.6.2.1.5.1, "Hex". The pro... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.22 Service type selection policy | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.22.1 Unsigned applications | Service type selection policy is irrelevant for unsigned applications since they are denied the ability to select a new service by clause 12.6.2.12.1, "Unsigned applications". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.22.2 Signed applications | By default a signed application running in an AbstractService shall be granted a this permission of type "abstract.mso" and other signed applications shall be granted this permission with type of "broadcast". NOTE: The type "broadcast" includes stand-alone stored services 9.6.2, "Stored services" and return channel sig... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.22.3 Permission request file syntax | <!ELEMENT servicetypepermission EMPTY> <!ATTLIST servicetypepermission type (broadcast | abstract.mso) "broadcast" action (own | all) "all" value (true | false) "false" > |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.23 Privileged application access | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.23.1 Unsigned applications | Unsigned applications shall not be able to access any privileged APIs. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.23.2 Signed applications | Only applications successfully authenticated as defined in clause 12.18, "Authentication of privileged applications" shall be able to access privileged APIs. Multiple instances of the "monitorapplication" element may appear, one for each type of access that is requested. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.6.2.23.3 Permission request file syntax | <!ELEMENT monitorapplication EMPTY> <!ATTLIST monitorapplication value (true | false) "false" name (registrar | service | servicemanager | security | reboot | handler.appFilter | systemevent) #IMPLIED > 12.7 Example of creating an application that can be authenticated |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.7.1 Scenario Example | This clause is informative and gives an example of how a file system carrying an application can be organized. In this example, the file system carries single signed application Xlet1. The main class of the application is the file root/Xlet1/classes/Xlet1.class, other files comprising the application are the following ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.7.2 Hashes and signature computations: | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.7.2.1 Computation of the hashes of the root/Xlet1/classes/subclasses directory | a) Initialize the MD5 algorithm. b) Apply the contents of the file "root/Xlet1/classes/subclasses/sub1.class" to the MD5 algorithm then apply the contents of the file "root/Xlet1/classes/subclasses/sub2.class" to the MD5 algorithm. The cumulative result from these two files is the result H0. c) Construct the contents o... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.7.2.2 Computation of the hashes of the of root/Xlet1/classes directory | e) Initialize the MD5 algorithm, compute the MD5 hash H2 using the contents of the file "root/Xlet1/classes/subclasses/dvb.hashfile". f) Initialize the MD5 algorithm, compute the MD5 hash H3 using the contents of the file "root/Xlet1/classes/Xlet1.class". ETSI ETSI TS 102 728 V1.2.1 (2011-09) 220 g) Initialize the MD5 ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.7.2.3 Computation of the hashes of the of root/Xlet1 directory | k) Initialize the MD5 algorithm, compute the MD5 hash H5 using the contents of the file "root/Xlet1/classes/dvb.hashfile". l) Construct the contents of the hash file for the directory root/Xlet1/classes/ as follows: Table 54: root/Xlet1/dvb.hashfile Field Comment 3 Three digests 1 Type of digest algorithm = MD5 1 Numbe... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.7.2.4 Computation of the signature | n) Initialize the MD5 algorithm, compute the MD5 hash H6 using the contents of the file root/Xlet1/dvb.hashfile. o) RSA-encrypt H6 with the private key corresponding to the public key that can be found in the leaf certificate in the file "root/Xlet1/dvb.certificates.1". In this example this has serial number 0123456. p... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.8 Void | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9 Certificate management | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1 Certificate Revocation Lists | 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 are not required to implement certificate revocation lists; such GEM terminal specifications are therefore not requ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.1 Introduction (informative) | Certificates may be revoked prior to their expiration time, e.g. if the broadcaster's private key is assumed to be compromised, or the broadcaster is no longer to be certified by the CA. Each CA publishes a list of revoked certificates, called a CRL (Certificate Revocation List). This contains the list of the serial nu... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.2 Distribution of CRLs (informative) | Two routes from the broadcaster to the GEM terminal can be envisaged: • Via the return channel. • In the broadcast MPEG stream. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 222 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.2.1 Distribution via return channel | In the certificate extension fields, there is an optional field called "CRL Distribution points". This field can hold a URL pointing to a crlFile which can be downloaded. This approach is suitable for obtaining CRLs relating to TLS authentication of return channel exchanges. It is not suitable for delivering CRLs for b... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.2.2 Distribution via MPEG stream | For a GEM terminal without a working return channel, the only way to deliver CRLs is via the broadcast MPEG Transport Stream. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.3 CRL retention | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.3.1 Requirement | GEM terminals shall retain CRLs or the information they contain (including serial numbers) in persistent storage because: • This enhances security as it defends against attacks with signals that filter out the CRL and use a revoked certificate. • It is more efficient to cache CRLs rather than downloading the CRLs for a... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.3.2 Storage requirement | The minimum amount of persistent storage required to store CRLs is addressed in clause 12.12, "Platform minima". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.3.3 Storage management | The broadcast CRL and RCMM signalling (see clause 12.9.2, "Root certificate management") manages the use of the persistent storage. If the CRL of a non-root certificate CA becomes too large the CA's certificate itself can be revoked by its parent CA who adds it to their CRL. For root certificates, the RCMM mechanism ca... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.4 CRL file location and naming convention | For CRLs that are authenticated by a non-root certificate the format of the name of files carrying CRLs shall be: "dvb.crl.x" In this case the "x" portion of the filename corresponds to the "x" portion of a certificate filename for the certificate file that authenticates the CRL. For CRLs that are authenticated by a ro... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.5 Operational model | Receivers are expected to inspect the set of CRL files periodically and cache the revocation information for future use. This inspection process can assume that a file system will not normally carry certificates revoked by CRL files carried in the same file system. So, inspection of the CRL set in a file system is not ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.6 Examples | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.6.1 Revocation of a broadcaster's certificate | If the broadcaster B's certificate is compromised: a) The certification authority CA01 adds the serial number of broadcaster B's certificate to its CRL. b) CA01 then sends the new CRL file to the broadcasters that use CA01. c) These broadcasters (broadcaster A for instance) broadcast the new CRL file. As soon as a GEM ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.6.2 Revocation of a CA's certificate. | If the CRL of CA01 becomes too big, CA01's certificate could be revoked: a) The root certification authority RCA0 adds the serial number of CA01's certificate to its CRL. b) RCA0 sends the new CRL file to the broadcasters that use RCA0. c) These broadcasters broadcast the new CRL file. As soon as a GEM terminal has dow... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.7 CRL format | Each CRL file contains the CRL of one certification authority. The encoding of the CRL is defined in the ITU-T Recommendation X.509 [51] is reproduced below for information. The fields Version, Time, CertificateSerialNumber correspond to fields with the same names in the certificate see clause 12.11, "The internet prof... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.8 Profile of CRL | The profile of fields that correspond to fields in the certificate follow the profile in clause 12.5, "Profile of X.509 certificates for authentication of applications". This applies to the following fields: signatureAlgorithm : follows clause 12.5.1, "signatureAlgorithm". signatureValue: follows clause 12.5.2, "signat... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.1.9 CRL Processing | CRLs, or the information they contain (including serial numbers), shall be kept in persistent storage in the GEM terminal. When a GEM terminal finds a file with the file name format given in clause 12.9.1.4, "CRL file location and naming convention", it shall do the following sequence: a) Get the field thisUpdate and c... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.2 Root certificate management | 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 are not required to implement root certificate management; such GEM terminal specifications are therefore not requ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.2.1 Introduction | Clause 12.9.2 specifies an MHP root certificate management protocol that fulfils the requirements of GEM, but another protocol syntax and another distribution means are possible. Broadly speaking, GEM places requirements on both the semantics of a root certificate management message and requirements underlying its proc... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.2.2 Security of RCMM | The reference to the nextNbOfSignature field is to be interpreted as referring to the version of nextNbOfSignature from the present document, as specified in clause 12.9.2.3. RCMM are authenticated by multiple signatures. An RCMM message will be accepted by an MHP terminal if and only if it has at least N signatures. E... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.2.3 Format of RCMM | RCMM encoding format as specified in MHP [1], clause 12.9.2.3 is not required for GEM terminal specifications. MHP [1], clause 12.9.2.3 shall apply to GEM terminal specifications that include the functional equivalent named "RCMM" as defined in clause 15.6, "Functional equivalents." GEM terminal specifications that do ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.2.4 Distribution of RCMM | This clause is not required for GEM terminal specifications. It shall apply to GEM terminal specifications that include the functional equivalent named "RCMM" as defined in clause 15.6, "Functional equivalents." GEM terminal specifications that do not include this MHP definition shall specify a functional equivalent th... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.2.5 RCMM Processing | References to RCMM messages named "dvb.rcmm.<x>" shall be interpreted as the set of historic RCMM messages as mentioned in clause 12.9.2.4 of the present document. References to RCMM message named "dvb.rcmm" shall be interpreted as the most recent RCMM message. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 227 When an MHP term... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.2.6 Example: Renewal of a root certificate | Let us assume the root certification authority RCA has two certificates in each MHP termninal:RC0 and RC1. If RC0 is compromised, RCA may wish to renew this certificate using the following steps: a) RCA generates a new key pair and a new self signed certificate RC2. b) RCA provides new certificates signed by RC1 to all... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.9.3 Test certificates | There shall be a means to make test root certificates (as required by clause 12.12, "Platform minima") available while the terminal is being tested. The method for doing so shall be implementation dependent; it may involve either replacing non-test root certificates, or storing test root certificates in addition to non... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.10.3.1 Introduction | Before the TLS connection can be established, a GEM application has to ensure that the certificate list sent by a server contains at least one trusted certificate. In computer environment, this is simply done by checking the list of certificates against one certificate that is resident in the computer. In the GEM envir... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.10.3.2 Usage of certificate in TLS | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.10.3.2.1 When certificates are delivered with the application | One or several TLS root certificates can be optionally broadcast along with the application. When the certificate chain sent by the TLS server is not compatible with any of the TLS root certificates sent with the application an IOException will be thrown. 12.10.3.2.1.1 Certificate file naming and location To facilitate... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.10.3.2.2 When no certificates are provided | When there are no TLS certificates sent with the application then the implementation will allow connection to be established to any server. The application can then use the JSSE API (see clause 11.8.2, "APIs for return channel security") to retrieve the certificate chain and check that it contains what the application ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.10.3.2.3 CRL distribution points | GEM implementations are free to ignore this field during TLS server authentication over the return channel. 12.11 The internet profile of X.509 (informative) The text that follows summarizes the technical features of RFC 2459 [54] and references the different profile decisions made for the different GEM application are... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.1 Certificate | Certificate ::= SEQUENCE { tbsCertificate TBSCertificate, signatureAlgorithm AlgorithmIdentifier, signatureValue BIT STRING } |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.2 signatureAlgorithm | The signatureAlgorithm field contains the identifier for the cryptographic algorithm used by the CA to sign this certificate. An algorithm identifier is defined by the following ASN.1 structure: AlgorithmIdentifier ::= SEQUENCE { algorithm OBJECT IDENTIFIER, parameters ANY DEFINED BY algorithm OPTIONAL } ETSI ETSI TS 1... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.3 signatureValue | The signatureValue field contains a digital signature computed upon the ASN.1 DER encoded tbsCertificate. The ASN.1 DER encoded tbsCertificate is used as the input to the signature function. This signature value is then ASN.1 encoded as a BIT STRING and included in the Certificate's signature field. NOTE: RFC 2459 [54]... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.4 tbsCertificate | The field contains the names of the subject and issuer, a public key associated with the subject, a validity period, and other associated information. The tbscertificate may also include extensions. The pair issuer / serialNumber uniquely identifies the certificate. TBSCertificate ::= SEQUENCE { version [0] EXPLICIT Ve... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.5 version | This field describes the version of the encoded certificate. When extensions are used, as expected in this profile, use X.509 version 3 (value is 2). If no extensions are present, but a UniqueIdentifier is present, use version 2 (value is 1). If only basic fields are present, use version 1 (the value is omitted from th... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.6 serialNumber | The serial number is an integer assigned by the CA to each certificate. It must be unique for each certificate issued by a given CA (i.e. the issuer name and serial number identify a unique certificate). CertificateSerialNumber ::= INTEGER |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.7 signature | This field contains the algorithm identifier for the algorithm used by the CA to sign the certificate. This field must contain the same algorithm identifier as the signatureAlgorithm field in the sequence Certificate. The contents of the optional parameters field will vary according to the algorithm identified. If the ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.8 issuer | The issuer field identifies the entity who has signed and issued the certificate. The issuer field must contain a non-empty distinguished name (DN). The issuer field is defined as the X.501 type Name. ITU-T Recommendation X.501 [50] Name is defined by the following ASN.1 structures: Name ::= CHOICE { RDNSequence } RDNS... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.9 validity | The certificate validity period is the time interval during which the CA warrants that it will maintain information about the status of the certificate. The field is represented as a SEQUENCE of two dates: the date on which the certificate validity period begins notBefore) and the date on which the certificate validity... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.9.1 UTCTime | The universal time type, UTCTime, is a standard ASN.1 type intended for representation of dates and time. UTCTime specifies the year through the two low order digits and time is specified to the precision of one minute or one second. UTCTime includes either Z (for Zulu, or Greenwich Mean Time) or a time differential. F... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.9.2 GeneralizedTime | The generalized time type, GeneralizedTime, is a standard ASN.1 type for variable precision representation of time. Optionally, the GeneralizedTime field can include a representation of the time differential between local and Greenwich Mean Time. For the purposes of this profile, GeneralizedTime values must be expresse... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.10 subject | The subject field identifies the entity associated with the public key stored in the SubjectPublicKeyInfo field. It thus represents the entity whose public key is certified. It is encoded as a Distinguished Name (see clause 12.11.1.8, "issuer"). This name must be unique for each subject entity certified by one CA as de... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.