View file

name	Intelligent Vehicle-Infrastructure Cooperation System(I-VICS) Datasheet.docx
height	250

Release 4 target date is November 30th 2020.

...

High Level Overall Requirements
CI, Blueprint Validation Lab Sub-Committee Requirements
1. Present Pod Topology document.
2. Peering w/LF Jenkins - (Note: peering is an optional requirement)
3. Push logs through Nexus. (Note: This is mandatory for Incubation self-certified and Maturity)
4. Usage of topics for release
  1. Releases >= 1.0 (e.g. 1.xyz, 2.xyz etc) are reserved for BP that have been approved as Core by the TSC (considered ‘GA’ quality).
  2. Releases <1.0 (e.g. 0.xyz etc) are reserved for projects that have not reached the Akraino Core level (i.e. anything that is in Incubation (‘alpha’ quality) and Mature (‘beta’ quality).
5. Enforcement of Static Code Analysis through SonarCloud (SaaS), WIP LF Release Engineering & Security Subcommittee. (Note: This is an optional requirement for Incubation self certified and mandatory for Maturity)
Security Sub-Committee Requirements, please fill in Release 4 Blueprint Scanning Status. Instructions can be found at: Steps To Implement Security Scan Requirements
Blueprint Validation Framework Feature Project Requirements See TSC meeting.
Projects going for Maturity Review please refer to Maturity Criteria defined by Process subcommittee BP Graduation Review Processes and Criteria (Note this is not required for self certification, only required for maturity review)
Documentation Sub-Committee Requirements
User Documents:
The following documentation with the following sections called out should be on the wiki with links to rest of the sections as applicable. We prefer that the entire doc is on the wiki but we do not require it.
Architecture - Blue print Overview and overall architecture
Release Notes – Summary and What is released
Installation Doc – Introduction and deployment architecture
Test Document – Introduction and Overall Test Architecture
Developer Documents:
We are also recommending that Blueprints include via ReadtheDocs, with each Blue Print given their own repo, but we do not require it
API Sub-Committee Requirements (Note: See this link for requirements: Blueprint Projects R4 API Reporting Requirements)
Community Sub-Committee Requirements (Note: no mandatory requirements for Incubation self-certified or Maturity)
Process Sub-Committee Requirements (Note: See the Process Sub Committee page defining the TSC approved Maturity review process and requirements for those requesting inclusion in R3 at Mature level BP Graduation Review Processes and Criteria)
Upstream Sub-Committee Requirements (Note: no mandatory requirements for Incubation self-certified or Maturity). Here is the R4 release Upstream BP review status, Release Upstream Compliance. Also please refer to the page for the R4 requirement as well.

...

01 Dec 2020Vuls Vuls Exception Request

01 Dec 2020

Lynis:

Performing test ID AUTH-9229 (Check password hashing methods)

You are using SHA512 hashing which is good, however, it appears the number of rounds for password hashing is still set to default at 5000. This value must be set higher, 65536. Below is additional information on this topic:

The rounds=N option helps to improve key strengthening. The number of rounds has a larger impact on security than the selection of a hash function. For example, rounds=65536 means that an attacker has to compute 65536 hashes for each password he tests against the hash in your /etc/shadow. Therefore the attacker will be delayed by a factor of 65536. This also means that your computer must compute 65536 hashes every time you log in, but even on slow computers that takes less than 1 second. If you do not use the rounds option, then glibc will default to 5000 rounds for SHA-512. Additionally, the default value for the rounds option can be found in sha512-crypt.c.

Open /etc/pam.d/passwd with a text editor and add the rounds option at the end of of the uncommented line. After applying this change the line should look like this:

password required pam_unix.so sha512 shadow nullok rounds=65536

After you change the number of rounds you will need to expire the existing passwords to encrypt using the new values.

2. Test: Check if one or more compilers can be found on the system

Reason: Our core components of BP are needing more than one compiler and fixing them can break our dependencies.

Since this BP is requesting a maturity review all compilers must be removed prior to using the system in production. Are there components that require compilers in the completed production release code?

Exceptions approved shown at:

Release 4 Vuls Exception scheduled at TSC Y/parserlabs/r4/jobs/iec-type4/

Form uploaded

Scheduled for API subcommittee review 21 Dec 2020

Waiting for re-uploaded API info form with PaaS API info

Reviewed by API subcommittee, PaaS APIs are subset of TARS APIsparserlabsr4jobs/iec-type4/parserlabsr4jobs/iec-type4/01 04 Jan

Performing test ID AUTH-9229 (Check password hashing methods)