Specification of Crypto Service Manager, No.402, 2021-11
AUTOSAR R21-11記事一覧はこちら。
AUTOSAR 21-11,160文書読んだ。2022年5月中に全部読み。
AUTOSAR 21-11, 62文書読んだ。2022年5月中に半分到達予定。
AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成
用語(terms)
| Term | Description |
|---|---|
| AEAD | Authenticated Encryption with Associated Data |
| CDD | Complex Device Driver |
| CSM | Crypto Service Manager |
| CRYIF | Crypto Interface |
| CRYPTO | Crypto Driver |
| DET | Default Error Tracer |
| HSM | Hardware Security Module |
| HW | Hardware |
| SHE | Security Hardware Extension |
| SW | Software |
| Crypto Driver Object | A Crypto Driver implements one or more Crypto Driver Objects. The Crypto Driver Object can offer different crypto primitives in hardware or software. The Crypto Driver Objects of one Crypto Driver are independent of each other. There is only one workspace for each Crypto Driver Object (i.e. only one crypto primitive can be performed at the same time) |
| Key | A Key can be referenced by a job in the Csm. In the Crypto Driver, the key refers a specific key type. |
| Key Type | A key type consists of refers to key elements. The key types are typically pre-configured by the vendor of the Crypto Driver. |
| Key Element | Key elements are used to store data. This data can be e.g. key material or the IV needed for AES encryption. It can also be used to configure the behaviour oft he key management functions. |
| Job | A Job is a configured 'CsmJob'. Among others, it refers to a key, a cryptographic primitive and a reference channel. |
| Channel | A channel is the path from a Crypto Service Manager queue via the Crypto Interface to a specific Crypto Driver Object. |
| Primitive | A primitive is an instance of a configured cryptographic algorithm realized in a Crypto Driver Object. Among others it refers to a functionality provided by the CSM to the application, the concrete underlining 'algorithmfamily' (e.g. AES, MD5, RSA, etc.), and a 'algorithmmode' (e.g. ECB, CBC, etc). |
| Operation | An operation of a crypto primitive declares what part of the crypto primitive shall be performed. There are three different operations: It is also possible to perform more than one operation at once by concatenating the corresponding bits of the operation_mode argument. |
| START | Operation indicates a new request of a crypto primitive, it shall cancel all previous requests perform necessary initializations and checks if the crypto primitive can be processed. |
| UPDATE | Operation indicates, that the crypto primitive expect input data. An update operation may provide intermediate results. |
| FINISH | Operation indicates, that after this part all data are fed completely and the crypto primitive can finalize the calculations. A finish operation may provide final results. |
| Priority | The priority of a job defines the importance of it. The higher the priority (as well in value), the more immediate the job will be executed. The priority of a cryptographic job is part of the configuration. |
| Processing | Indicates the kind of job processing. |
| Asynchronous | The job is not processed immediately when calling a corresponding function. Usually, the caller is informed via a callback function when the job has been finished. |
| Synchronous | The job is processed immediately when calling a corresponding function. When the function returns, a result will be available. |
| Service | A service shall be understand as defined in the TR_Glossary document: A service is a type of operation that has a published specification of interface and behavior, involving a contract between the provider of the capability and the potential clients. |
英日
日本語は仮訳
T.B.D.
参考(reference)
[1] List of Basic Software Modules
AUTOSAR_TR_BSWModuleList.pdf
[2] Layered Software Architecture
AUTOSAR_EXP_LayeredSoftwareArchitecture.pdf
[3] General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral.pdf
[4] Specification of RTE Software
AUTOSAR_SWS_RTE.pdf
[5] Specification of BSW Scheduler
AUTOSAR_SWS_Scheduler.pdf
[6] Specification of ECU Configuration
AUTOSAR_TPS_ECUConfiguration.pdf
[7] Specification of Memory Mapping
AUTOSAR_SWS_MemoryMapping.pdf
[8] Specification of Default Error Tracer
AUTOSAR_SWS_DefaultErrorTracer.doc.pdf
[9] Specification of Diagnostic Event Manager
AUTOSAR_SWS_DiagnosticEventManager.pdf
[10] Specification of ECU State Manager
AUTOSAR_SWS_ECUStateManager.pdf
[11] Specification of C Implementation Rules
AUTOSAR_TR_CImplementationRules.pdf
[12] Specification of Standard Types
AUTOSAR_SWS_StandardTypes.pdf
[13] AUTOSAR Glossary, AUTOSAR_TR_Glossary.pdf
https://www.autosar.org/fileadmin/standards/foundation/21-11/AUTOSAR_TR_Glossary.pdf
[14] Requirements on the Crypto Stack
AUTOSAR_SRS_CryptoStack.pdf
[15] Specification of the Crypto Interface
AUTOSAR_SWS_CryptoInterface.pdf
[16] Specification of the Crypto Driver
AUTOSAR_SWS_CryptoDriver.pdf
[17] General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral.pdf
[18] IEC 7498-1 The Basic Model, IEC Norm, 1994
[19] IETF RFC5639 Elliptic Curve Cryptography (ECC) Brainpool Standard
Curves and Curve Generation, 2010
[20] IETF RFC6637 Elliptic Curve Cryptography (ECC) in OpenPGP, 2012
＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
文書履歴(document history)
ver. 0.01 初稿 20221201
ver. 0.02 URL追記 20230121