This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Crypto Driver

Crypto Driver

Component Documentation

1 - Crypto Peer Review Checklists

Overview

Summary Sheet
Synergy Project
3rd Party Files

Sheet 1: Summary Sheet























Rev 1.019-Apr-17
Peer Review Summary Sheet


























Synergy Project Name:



Windows User: Intended Use: Identify which component is being reviewed. This should match the component short name and the middle part of the Synergy project name Crypto
Revision / Baseline:


Windows User: Intended Use: Identify the implementation baseline name intended to be used for the changed component when changes are approved. Crypto_Bac_Ar4.3.0_05.02.00_Bmw_0


























Change Owner:



Windows User: Intended Use: Identify the developer who made the change(s) being reviewed Akilan Rathakrishnan
Work CR ID:


Windows User: Intended Use: Identify the Implementation Work CR whose work is being reviewed (may be more than one) EA4#21725


























3rd party delivery package identifier:







Intended Use: This is a reference to the identifier of the 3rd party delivery package(s) that the component was extracted/created from. Rationale: This will allow easier tracing back to 3rd party deliveries. CBD1700369_D04_Rh850


























Windows User: Identifiy which type of 3rd party component this is so as to provide appropriate review checklist sheets Component Type:





























































































































Windows User: General section for summarizing review comments or review notes. Review Checklist Summary:


















































Comments:































































Sheet 2: Synergy Project

Peer Review Meeting Log (Component Synergy Project Review)



















































Quality Check Items:




































Rationale is required for all answers of No










New baseline version name from Summary Sheet follows








Yes
Comments:




naming convention for 3rd Party Software Components







































Project contains necessary subprojects








N/A
Comments:













































Project contains the correct version of subprojects








N/A
Comments:













































General Notes / Comments:



























































LN: Intended Use: Identify who were the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. KMC: Group Review Level removed in Rev 4.0 since the design review is not checked in until approved, so it would always be DR4. Review Board:


























Change Owner:

Akilan Rathakrishnan


Review Date :

03/15/18
































Lead Peer Reviewer:


Kevin Smith


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Rijvi Ahmed





































































Sheet 3: 3rd Party Files

Peer Review Meeting Log (3rd Party File Review)





















































Quality Check Items:






































Rationale is required for all answers of No










(e.g. component_bswmd.arxml) Component "autosar" folder contains autosar module description file from 3rd party delivery packageYes
Comments:




































(e.g. component_preo.arxml) Component "autosar" folder contains any relevant preconfiguration files from 3rd party delivery package(s)Yes
Comments:




































If needed as in the case with Renesas MCAL (e.g. MCALcomponent_bswmd_rec.arxml taken from Vector delivery) Component "autosar" folder contains any needed supplemental autosar module description file(s)N/A
Comments:




































Component "doc" folder contains all documentation related to this component from 3rd party delivery packageYes
Comments:




































Modifications from delivery to be reviewed (e.g. path changes) Component "generate" folder contains all external generation files from 3rd party delivery packageYes
Comments:




































Component "include" and "src" folder contains exact component files from 3rd party delivery packageYes
Comments:




































Component "make" folder contains any makefiles included from 3rd party delivery packageYes
Comments:




































1) All source and headers of component should be referenced in .gpj 2) Compiler settings may need to be tailored to source component (e.g. Renesas MCAL vs Vector BSWs) Component "tools" folder contains GHS project file with appropriate files referenced with appropriate compiler settingsYes
Comments:




































Should delete old existing files/directories from integration project and copy new ones into integration project May also contain logic for integrator user interaction if required. (e.g. selection of micro variant on MCAL) Component "tools" folder contains Integrate.bat with appropriate logic in it for integration into projectYes
Comments:




































For external generation and internal behavior definition for use with Vector Davinci tools. Typically only desired/needed for non-Vector developed components. This file should be copied as part of Integrate.bat. Components optionally contains settings xml file with appropriate contentsYes
Comments:




































General Notes / Comments:





























































LN: Intended Use: Identify who were the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. KMC: Group Review Level removed in Rev 4.0 since the design review is not checked in until approved, so it would always be DR4. Review Board:



























Change Owner:

Akilan Rathakrishnan


Review Date :

03/15/18

































Lead Peer Reviewer:


Kevin Smith


Approved by Reviewer(s):



Yes
































Other Reviewer(s):


Rijvi Ahmed







































































2 - CryptoClassic_IntegrationManual

3 - CryptoClassic_IntegrationManual_ind

Outline
Page 1
Page 2
Page 3
Page 4
Page 5
Page 6
Page 7

4 - CryptoClassic_IntegrationManuals


Crypto Classic Integration Manual
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.2.0
Status
Release
Hotline
+49 89 382 - 32233
Contact
bac@bmw.de
https://asc.bmw.com/jira/browse/BSUP (extern)
https://asc.bmwgroup.net/jira/browse/BSUP (intern)
Revision History
Version
Date
Description
5.2.0
2017-12-14
Version Update
5.1.0
2017-11-09
Version Update
5.0.0
2017-10-12
Initial version for SP2021
Company
Bayerische
Motoren Werke
Aktiengesellschaft
Postal address
BMW AG
80788 München
Office address
Forschungs- und
Innovationszentrum
(FIZ)
Hufelandstr. 1
80937 München
Telephone
Switchboard
+49 89 382-0
Internet
www.bmwgroup.com
CryptoClassic_IntegrationManual.pdf, Version 5.2.0, Software Platforms
Page 1 of 7

Table of Contents
1 Introduction
3
1.1
Functional overview
3
2 Related documentation
4
3 Limitations
5
4 Software Architecture
6
4.1
Dependencies on AUTOSAR modules
6
4.2
Dependencies to other modules
6
5 Integration
7
5.1
Configuration of other Modules
7
5.2
Configuration
7
5.3
Configuration of the RTE
7
5.4
Key File
7
CryptoClassic_IntegrationManual.pdf, Version 5.2.0, Software Platforms
Page 2 of 7

1
Introduction
This Integration Manual describes the basis functionality and the configuration and integration of the
Crypto module.
Functional overview
The main objective of the Crypto functionality is to provide a hardware independant cryptography library
which shall be usable by all BMW ECUs.
The Crypto Module provides the following Crypto primitives :
SHA-256
SHA-384
SHA-512
ECDSA Signature verification (P-256/P-384/P-521)
Certificate parsing and signature verification.
CryptoClassic_IntegrationManual.pdf, Version 5.2.0, Software Platforms
Page 3 of 7

2
Related documentation
References
CryptoClassic_IntegrationManual.pdf, Version 5.2.0, Software Platforms
Page 4 of 7

3
Limitations
No limitations are known.
CryptoClassic_IntegrationManual.pdf, Version 5.2.0, Software Platforms
Page 5 of 7

4
Software Architecture
Dependencies on AUTOSAR modules
The current version of the Module Crypto does not depend on any BSW module.
Dependencies to other modules
Crypto includes headers from the BMW BUtil module.
CryptoClassic_IntegrationManual.pdf, Version 5.2.0, Software Platforms
Page 6 of 7

5
Integration
Configuration of other Modules
No other module needs to be configured to perform integration of the Crypto library.
Configuration
For a detailed description of the configuration parameters, please consult the description in the Crypto
parameter definition file.
Configuration of the RTE
There are no special requirement for RTE configuration.
Key File
The security key file is generated with BMW backend system SWL-SEC for every ECU. This key file
named Crypto_Keys.h needs to be included directly.
CryptoClassic_IntegrationManual.pdf, Version 5.2.0, Software Platforms
Page 7 of 7

Document Outline

5 - CryptoClassic_ReleaseNotes

6 - CryptoClassic_ReleaseNotes_ind

Outline
Page 1
Page 2
Page 3

7 - CryptoClassic_ReleaseNotess


Release Notes CryptoClassic
Project
BMW AUTOSAR 4 Core Rel. 3
Author
BMW AG
Release Date
2017-12-14
Version
5.2.0
Status
Release
Hotline
+49 89 382 - 32233
Contact
bac@bmw.de
https://asc.bmw.com/jira/browse/BSUP (extern)
https://asc.bmwgroup.net/jira/browse/BSUP (intern)
Revision History
Version
Date
Issues
5.2.0
2017-12-14
BAC-6668, BAC-6671
5.1.0
2017-11-09
BAC-6508, BAC-6451
5.0.0
2017-10-12
Company
Bayerische
Motoren Werke
Aktiengesellschaft
Postal address
BMW AG
80788 München
Office address
Forschungs- und
Innovationszentrum
(FIZ)
Hufelandstr. 1
80937 München
Telephone
Switchboard
+49 89 382-0
Internet
www.bmwgroup.com
ReleaseNotes_CryptoClassic, Version 5.2.0, Software Platforms
Page 1 of 3

1
Module Description
The Crypto module provides access to a Cryptographic library and can be used as an AUTOSAR Crypto
driver.
2
Revisions and Modifications
Revision 5.2.0 [Released]
Item
Description
CR ID:
BAC-6668
CR Headline:
Incorrect name of Integration Manual
Description of Issues:
Integration Manual is incorrectly named.
Description of Changes:
Integration Manual habeen correctly named.
Changed Files:
doc/CryptoClassic_IntegrationManual.pdf
Compatibility:
Item
Description
CR ID:
BAC-6671
CR Headline:
Add functionalities for RSA Verifiy (PKCS1 V2)
Description of Issues:
RSA verification feature (PKCS1 V2) needs to be implemented
Description of Changes:
RSA verification feature is implemented. The corresponding
interface has been added to the jumptable and the corresponding
parameters are now present in the paramconf
Changed Files:
cfgdesc/CryptoClassic_paramdef.arxml
generate/src/Crypto_JumpTable.c.pgen
generate/include/Crypto_JumpTable.h.pgen
Compatibility:
Revision 5.1.0 [Released]
Item
Description
CR ID:
BAC-6508
CR Headline:
Update jumptable generation to new Page version
Description of Issues:
Pgen files used to generate Crypto jumptable don't work with the
new version of page.
Description of Changes:
Updated the files so the jumptable can be generated again.
Changed Files:
src/Crypto_CertificateManagement.c
generate/include/Crypto_CertificateManagement.h.pgen
generate/src/Crypto_CertificateManagement.c.pgen
CMakeLists.txt
generate/src/Crypto_JumpTable.c.pgen
generate/include/Crypto_JumpTable.h.pgen
Compatibility:
ReleaseNotes_CryptoClassic, Version 5.2.0, Software Platforms
Page 2 of 3

Item
Description
CR ID:
BAC-6451
CR Headline:
Add functionalities Hashes SHA 384 and SHA512
Description of Issues:
The hashes SHA 384 and SHA 512 are missing from the BMW
Crypto library.
Description of Changes:
Functionalities have been added to the generic part. Jumptables
have been adapted with new functions to allow access to said
functionalities.
Changed Files:
cfgdesc/CryptoClassic_paramdef.arxml
template/include/Crypto_MemMap.h.sample
generate/include/Crypto_JumpTable.h.pgen
generate/src/Crypto_JumpTable.c.pgen
Compatibility:
Revision 5.0.0 [Released]
Item
Description
CR ID:
CR Headline:
Initial Release for SP2021
Description of Issues:
Initial Release for SP2021
Description of Changes:
Initial Release for SP2021
Changed Files:
Compatibility:
ReleaseNotes_CryptoClassic, Version 5.2.0, Software Platforms
Page 3 of 3

Document Outline

8 - CryptoGeneric_ReleaseNotes

9 - CryptoGeneric_ReleaseNotes_ind

Outline
Page 1
Page 2
Page 3
Page 4
Page 5
Page 6

10 - CryptoGeneric_ReleaseNotess


Release Notes CryptoGeneric
Project
BMW AUTOSAR Core 4 Rel. 3 and adaptive BMW AUTOSAR Core Rel. 1
Author
BMW AG
Release Date
2017-12-14
Version
5.2.0
Status
Release
Hotline
+49 89 382 - 32233 (classic) / +49 89 382 - 22522 (adaptive)
Contact
bac@bmw.de (classic) / abac@bmw.de (adaptive)
https://asc.bmw.com/jira/browse/BSUP (extern)
https://asc.bmwgroup.net/jira/browse/BSUP (intern)
Revision History
Version
Date
Issues
5.2.0
2017-12-14
BAC-6720, BAC-6588, BAC-6681, BAC-6671
5.1.0
2017-11-09
BAC-6548, BAC-6508, BAC-6451
5.0.0
2017-10-12
Company
Bayerische
Motoren Werke
Aktiengesellschaft
Postal address
BMW AG
80788 München
Office address
Forschungs- und
Innovationszentrum
(FIZ)
Hufelandstr. 1
80937 München
Telephone
Switchboard
+49 89 382-0
Internet
www.bmwgroup.com
ReleaseNotes_CryptoGeneric, Version 5.2.0, Software Platforms
Page 1 of 6

1
Module Description
TODO
2
Revisions and Modifications
Revision 5.2.0 [Released]
Item
Description
CR ID:
BAC-6720
CR Headline:
Clean up Crypto
Description of Issues:
Clean up : - Removed pieces of unused code. - Fix warnings.
Description of Changes:
Removed unused code and comments. Fixed some warnings.
Changed Files:
src/Crypto_Keys.c
src/Crypto_SHA256.c
src/fp_mul.c
src/fp_sqr.c
Compatibility:
Item
Description
CR ID:
BAC-6588
CR Headline:
Use tomfastmath for Crypto Math functions
Description of Issues:
Changed Big Number Math functions to gain speed.
Description of Changes:
Switched to Tomfastmath based functions. (Internal functions
change only).
Changed Files:
src/fp_cmp_d.c
generate/include/Crypto_Cfg.h.pgen
src/fp_add.c
cfgdesc/Crypto_paramdef.arxml
src/fp_sqr_comba_20.c
src/Crypto_Math.c
src/fp_mod_2d.c
src/fp_cmp.c
CMakeLists.txt
src/fp_lshd.c
src/fp_mulmod.c
src/fp_rshd.c
src/s_fp_sub.c
src/fp_montgomery_calc_normalization.c
src/fp_mul_comba.c
src/fp_mul_2d.c
src/fp_mul_comba.h
src/fp_2expt.c
src/fp_mul_comba_small_set.c
ReleaseNotes_CryptoGeneric, Version 5.2.0, Software Platforms
Page 2 of 6

src/fp_sqr.c
src/s_fp_add.c
src/fp_div.c
src/Crypto_Math_Intern.h
src/Crypto_EccOperations.c
src/fp_montgomery_setup.c
src/fp_montgomery_reduce.c
src/fp_reverse.c
src/fp_invmod.c
src/fp_mul_comba_20.c
src/fp_sqr_comba_small_set.c
src/Crypto_Common_Intern.h
src/fp_sqr_comba_generic.c
src/fp_div_2d.c
src/fp_mod.c
src/fp_mul_2.c
src/fp_sqr_comba.h
src/fp_set.c
src/fp_count_bits.c
src/mp_read_unsigned_bin.c
src/fp_sqr_comba.c
src/fp_mul.c
src/fp_div_2.c
src/Crypto_ECDSA.c
src/Crypto_ECDSA_Intern.h
src/fp_mul_d.c
src/fp_cmp_mag.c
src/fp_sub.c
src/fp_to_unsigned_bin.c
Compatibility:
Item
Description
CR ID:
BAC-6681
CR Headline:
Fix or justify Misra warnings/errors
Description of Issues:
Some Misra warnings have to be corrected
Description of Changes:
Correct some MISRA warnings when possible.
Changed Files:
Corrected code to reduce number of MISRA warnings.
Compatibility:
Item
Description
CR ID:
BAC-6671
CR Headline:
Add functionalities for RSA Verifiy (PKCS1 V2)
Description of Issues:
RSA verification feature (PKCS1 V2) needs to be implemented
Description of Changes:
RSA verification feature is implemented. The corresponding
interface has been added to the jumptable and the corresponding
parameters are now present in the paramconf
ReleaseNotes_CryptoGeneric, Version 5.2.0, Software Platforms
Page 3 of 6

Changed Files:
generate/include/Crypto_Cfg.h.pgen
src/Crypto_HashDescriptor.c
include/Crypto_KeyManagement.h
CMakeLists.txt
src/zeromem.c
include/Crypto_RSA.h
src/Crypto_EccOperations.c
cfgdesc/Crypto_paramdef.arxml
src/Crypto_RSA.c
src/Crypto_Math_Intern.h
src/Crypto_KeyManagement_Intern.h
include/Crypto_Hash.h
src/Crypto_Keys.c
include/Crypto_Common.h
src/Crypto_Common_Intern.h
include/Crypto.h
src/fp_unsigned_bin_size.c
src/Crypto_RSA_Intern.h
src/mem_neq.c
include/Crypto_ECDSA.h
src/Crypto_ECDSA.c
src/Crypto_ECDSA_Intern.h
src/fp_exptmod.c
Compatibility:
Revision 5.1.0 [Released]
Item
Description
CR ID:
BAC-6548
CR Headline:
Improve math functions performance by allowing inlining
Description of Issues:
BMW Math functions allow inlining (as defined in AUTOSAR) in
order to improve performance.
Description of Changes:
Grouped Math functions in a file and declared the relevant as
LOCAL_INLINE to allow optimization from the integrator.
Changed Files:
src/bn_mp_copy.c
src/bn_mp_mul_d.c
src/bn_mp_div_2.c
src/bn_s_mp_add.c
src/bn_mp_count_bits.c
src/Crypto_Math.c
src/bn_mp_2expt.c
src/bn_mp_init_copy.c
src/bn_mp_read_unsigned_bin.c.c
src/bn_fast_mp_montgomery_reduce.c
src/bn_mp_cmp_mag.c
src/bn_mp_div.c
ReleaseNotes_CryptoGeneric, Version 5.2.0, Software Platforms
Page 4 of 6

src/bn_mp_montgomery_reduce.c
src/bn_mp_montgomery_setup.c
src/bn_mp_zero.c
src/bn_mp_mod_2d.c
src/bn_s_mp_sub.c
src/bn_fast_s_mp_mul_digs.c
src/bn_mp_invmod.c
src/bn_mp_mod.c
src/bn_fast_mp_invmod.c
src/bn_s_mp_sqr.c
src/bn_mp_cmp_d.c
src/bn_mp_sqr.c
src/bn_mp_set.c
src/bn_mp_invmod_slow.c
src/bn_mp_mul.c
src/bn_mp_montgomery_calc_normalization.c
src/bn_mp_mul_2.c
src/bn_mp_exch.c
src/bn_mp_sub.c
src/bn_mp_rshd.c
src/bn_mp_clamp.c
src/bn_mp_lshd.c
src/bn_mp_add.c
src/bn_mp_mul_2d.c
src/bn_mp_div_2d.c
src/Crypto_Math_Intern.h
src/bn_mp_mulmod.c
src/bn_s_mp_mul_digs.c
src/bn_mp_cmp.c
CMakeLists.txt
src/bn_mp_init_size.c
Compatibility:
Item
Description
CR ID:
BAC-6508
CR Headline:
Update jumptable generation to new Page version
Description of Issues:
Pgen files used to generate Crypto jumptable don't work with the
new version of page.
Description of Changes:
Updated the files so the jumptable can be generated again.
Changed Files:
include/Crypto_Certificate.h
src/Crypto_CertificateHandling.c
Compatibility:
Item
Description
CR ID:
BAC-6451
CR Headline:
Add functionalities Hashes SHA 384 and SHA512
ReleaseNotes_CryptoGeneric, Version 5.2.0, Software Platforms
Page 5 of 6

Description of Issues:
The hashes SHA 384 and SHA 512 are missing from the BMW
Crypto library.
Description of Changes:
Functionalities have been added to the generic part. Jumptables
have been adapted with new functions to allow access to said
functionalities.
Changed Files:
template/include/Crypto_MemMap.h.sample
include/Crypto_Hash.h
src/Crypto_SHA256.c
src/Crypto_BitOperations.h
CMakeLists.txt
src/Crypto_SHA512.c
src/Crypto_SHA384.c
Compatibility:
Revision 5.0.0 [Released]
ReleaseNotes_CryptoGeneric, Version 5.2.0, Software Platforms
Page 6 of 6

Document Outline

11 - CryptoGeneric_RequirementsTable

12 - CryptoGeneric_RequirementsTable_ind

Outline
Page 1
Page 2
Page 3
Page 4

13 - CryptoGeneric_RequirementsTables


Crypto Generic Requirements Table
Project
BMW AUTOSAR Core 4 Rel. 3 and adaptive BMW AUTOSAR Core Rel. 1
Author
BMW AG
Release Date
2017-12-14
Version
5.2.0
Status
Release
Hotline
+49 89 382 - 32233 (classic) / +49 89 382 - 22522 (adaptive)
Contact
bac@bmw.de (classic) / abac@bmw.de (adaptive)
https://asc.bmw.com/jira/browse/BSUP (extern)
https://asc.bmwgroup.net/jira/browse/BSUP (intern)
Revision History
Version
Date
Changed by
Description
5.2.0
2017-12-14
JC-42
Version Update
5.1.0
2017-11-09
JC-42
Version Update
5.0.0
2017-10-12
JC-42
Initial version for SP2021.
Company
Bayerische
Motoren Werke
Aktiengesellschaft
Postal address
BMW AG
80788 München
Office address
Forschungs- und
Innovationszentrum
(FIZ)
Hufelandstr. 1
80937 München
Telephone
Switchboard
+49 89 382-0
Internet
www.bmwgroup.com
CryptoGeneric_RequirementsTable.pdf, Version 5.2.0, Software Platforms
Page 1 of 4

Table of Contents
1 Related documentation
3
2 Requirements Table
4
CryptoGeneric_RequirementsTable.pdf, Version 5.2.0, Software Platforms
Page 2 of 4

1
Related documentation
References
[1] LH Basic Security Requirements
SAP: 10634396 000 03
CryptoGeneric_RequirementsTable.pdf, Version 5.2.0, Software Platforms
Page 3 of 4

2
Requirements Table
The Requirements are taken from [1].
Requirement
Description
Satisfied by
[CERT_1011]
No description
[CERT_1012]
No description
[CERT_1015]
No description
[CERT_1173]
No description
[CERT_20]
No description
[CERT_603]
No description
CryptoGeneric_RequirementsTable.pdf, Version 5.2.0, Software Platforms
Page 4 of 4

Document Outline