Example: air traffic controller

Specification of Crypto Service Manager - AUTOSAR

Specification of Crypto Service Manager AUTOSAR CP Release 1 of 233 Document ID 402: AUTOSAR_SWS_CryptoServiceManager - AUTOSAR confidential - Document Change History Date Release Changed by Change Description 2017-12-08 AUTOSAR Release Management Added definition for asymmetric key formats Error fixing and consistency improvements Editorial changes 2016-11-30 AUTOSAR Release Management Introduced Crypto job concept Introduced key management concept Removed Cry_XXX functions from the Csm and introduced two new layers in the Crypto stack: Crypto Interface (CryIf) and Crypto Driver ( Crypto ) 2015-07-31 AUTOSAR Release Management Changed return type from Csm_ReturnType to Std_Types in all API functions Added detailed description of RTE interfaces Debugging support marked as obsolete Error fixing and consistency improvements 2014-10-31 AUTOSAR Release Management Obsolete configuration elements removed Error fixing and consistency improvements Editorial changes Document Title Specification of Crypto Service Manager Document Owner AUTOSAR Docu

Specification of Crypto Service Manager AUTOSAR CP Release 4.3.1 7 of 233 Document ID 402: AUTOSAR_SWS_CryptoServiceManager - AUTOSAR confidential -

Tags:

  Services, Specification, Manager, Crypto, Specification of crypto service manager

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Transcription of Specification of Crypto Service Manager - AUTOSAR

1 Specification of Crypto Service Manager AUTOSAR CP Release 1 of 233 Document ID 402: AUTOSAR_SWS_CryptoServiceManager - AUTOSAR confidential - Document Change History Date Release Changed by Change Description 2017-12-08 AUTOSAR Release Management Added definition for asymmetric key formats Error fixing and consistency improvements Editorial changes 2016-11-30 AUTOSAR Release Management Introduced Crypto job concept Introduced key management concept Removed Cry_XXX functions from the Csm and introduced two new layers in the Crypto stack: Crypto Interface (CryIf) and Crypto Driver ( Crypto ) 2015-07-31 AUTOSAR Release Management Changed return type from Csm_ReturnType to Std_Types in all API functions Added detailed description of RTE interfaces Debugging support marked as obsolete Error fixing and consistency improvements 2014-10-31 AUTOSAR Release Management Obsolete configuration elements removed Error fixing and consistency improvements Editorial changes Document Title Specification of Crypto Service Manager Document Owner AUTOSAR Document Responsibility AUTOSAR Document Identification No 402 Document Status Final Part of AUTOSAR Standard Classic Platform Part of Standard Release Specification of Crypto Service Manager AUTOSAR CP Release 2 of 233 Document ID 402.

2 AUTOSAR_SWS_CryptoServiceManager - AUTOSAR confidential - Document Change History Date Release Changed by Change Description 2017-12-08 AUTOSAR Release Management Added definition for asymmetric key formats Error fixing and consistency improvements Editorial changes 2014-03-31 AUTOSAR Release Management Error fixing and consistency improvements Editorial changes 2013-10-31 AUTOSAR Release Management Error fixing and consistency improvements Editorial changes Removed chapter(s) on change documentation 2013-03-15 AUTOSAR Administration services for compression/decompression added services for key update added (Concept CSM extension ) services for symmetric key generation added (Concept CSM extension ) Service state machine changed to cope with terminated users by releasing of locked resources Production errors restructured 2011-12-22 AUTOSAR Administration Fixed issues with AUTOSAR Port Interfaces 2010-09-30 AUTOSAR Administration Complete Configuration parameters Complete API specifications Add support for secure key storage Integration of support for key transport services Introduction of new DET error (checking of the null pointer in getversion info).

3 2010-02-02 AUTOSAR Administration Initial release Specification of Crypto Service Manager AUTOSAR CP Release 3 of 233 Document ID 402: AUTOSAR_SWS_CryptoServiceManager - AUTOSAR confidential - Disclaimer This work ( Specification and/or software implementation) and the material contained in it, as released by AUTOSAR , is for the purpose of information only. AUTOSAR and the companies that have contributed to it shall not be liable for any use of the work. The material contained in this work is protected by copyright and other types of intellectual property rights. The commercial exploitation of the material contained in this work requires a license to such intellectual property rights. This work may be utilized or reproduced without any modification, in any form or by any means, for informational purposes only.

4 For any other purpose, no part of the work may be utilized or reproduced, in any form or by any means, without permission in writing from the publisher. The work has been developed for automotive applications only. It has neither been developed, nor tested for non-automotive applications. The word AUTOSAR and the AUTOSAR logo are registered trademarks. Specification of Crypto Service Manager AUTOSAR CP Release 4 of 233 Document ID 402: AUTOSAR_SWS_CryptoServiceManager - AUTOSAR confidential - Table of Contents 1 Introduction and Functional Overview .. 7 2 Acronyms and 8 Glossary of Terms .. 8 3 Related documentation .. 10 Input Documents .. 10 Related standards and norms .. 11 Related Specification .

5 11 4 Constraints and 12 Limitations .. 12 Applicability to Car Domains .. 12 Security Implications .. 12 5 Dependencies to other Modules .. 13 File Structure .. 13 Code File Structure .. 13 Header File Structure .. 13 6 Requirements 15 7 Functional Specification .. 20 Basic Architecture Guidelines .. 20 General 20 Normal Operation .. 21 Design Notes .. 24 Error Classification .. 31 Development Errors .. 31 Runtime Errors .. 32 Transient Faults .. 32 Production Errors .. 32 Extended Production Errors .. 32 Error detection .. 32 8 API Specification .. 34 Imported types .. 34 Type Definitions .. 34 Crypto_AlgorithmFamilyType .. 34 35 Function Definitions .. 36 General Interface.

6 36 Hash Interface .. 37 MAC interface .. 41 Cipher Interface .. 47 Authenticated Encryption with Associated Data (AEAD) Interface .. 61 Signature Interface .. 63 Secure Counter Interface .. 68 Random Interface .. 69 Key Management Interface .. 70 Specification of Crypto Service Manager AUTOSAR CP Release 5 of 233 Document ID 402: AUTOSAR_SWS_CryptoServiceManager - AUTOSAR confidential - Job Cancellation Interface .. 83 Callback Notifications .. 84 Scheduled functions .. 86 Expected Interfaces .. 86 Interfaces to Standard Software Modules .. 86 Mandatory Interfaces .. 86 Optional Interfaces .. 86 Service 86 Client-Server-Interfaces .. 87 Implementation Data Types .. 136 Ports.

7 161 9 Sequence Diagrams .. 172 Asynchronous Calls .. 172 Synchronous Calls .. 173 10 Configuration .. 174 How to Read this Chapter .. 174 Containers and Configuration Parameters .. 174 Csm .. 180 CsmGeneral .. 180 CsmJobs .. 183 CsmJob .. 183 CsmKeys .. 186 CsmKey .. 186 CsmPrimitives .. 187 CsmQueues .. 188 CsmQueue .. 188 CsmHash .. 189 CsmHashConfig .. 189 CsmMacGenerate .. 193 CsmMacGenerateConfig .. 193 CsmMacVerify .. 197 CsmMacVerifyConfig .. 198 202 CsmEncryptConfig .. 202 CsmDecrypt .. 206 CsmDecryptConfig .. 206 CsmAEADE ncrypt .. 210 CsmAEADE ncryptConfig .. 210 CsmAEADD ecrypt .. 214 CsmAEADD ecryptConfig .. 215 CsmSignatureGenerate .. 219 CsmSignatureGenerateConfig.

8 219 CsmSignatureVerify .. 223 CsmSignatureVerifyConfig .. 223 CsmSecureCounter .. 227 CsmSecureCounterConfig .. 228 CsmRandomGenerate .. 228 CsmRandomGenerateConfig .. 228 CsmCallbacks .. 232 Specification of Crypto Service Manager AUTOSAR CP Release 6 of 233 Document ID 402: AUTOSAR_SWS_CryptoServiceManager - AUTOSAR confidential - CsmCallback .. 232 Published Information .. 233 Specification of Crypto Service Manager AUTOSAR CP Release 7 of 233 Document ID 402: AUTOSAR_SWS_CryptoServiceManager - AUTOSAR confidential - 1 Introduction and Functional Overview This Specification specifies the functionality, API and the configuration of the software module Crypto Service Manager (CSM) to satisfy the top-level requirements represented in the CSM Requirements Specification (SRS) [CSM_SRS].

9 The CSM shall provide synchronous or asynchronous services to enable a unique access to basic cryptographic functionalities for all software modules. The CSM shall provide an abstraction layer, which offers a standardized interface to higher software layers to access these functionalities. The functionality required by a software module can be different to the functionality required by other software modules. For this reason, there shall be the possibility to configure and initialize the services provided by the CSM individually for each software module. This configuration comprises as well the selection of synchronous or asynchronous processing of the CSM services . The construction of the CSM module follows a generic approach.

10 Wherever a detailed Specification of structures and interfaces would limit the scope of the usability of the CSM, interfaces and structures are defined in a generic way. This provides an opportunity for future extensions. Specification of Crypto Service Manager AUTOSAR CP Release 8 of 233 Document ID 402: AUTOSAR_SWS_CryptoServiceManager - AUTOSAR confidential - 2 Acronyms and Abbreviations Acronyms and abbreviations, which have a local scope and therefore are not contained in the AUTOSAR glossary [13], are listed in this chapter. Abbreviation / Acronym: Description: AEAD Authenticated Encryption with Associated Data CDD Complex Device Driver CSM Crypto Service Manager CRYIF Crypto Interface Crypto Crypto Driver DEM Diagnostic Event Manager DET Default Error Tracer HSM Hardware Security Module HW Hardware SHE Security Hardware Extension SW Software Glossary of Terms Terms: Description: Crypto Driver Object A Crypto Driver implements one or more Crypto Driver Objects.


Related search queries