Operating system kernel authentication system based on RUST language
Through the RUST language-based operating system kernel authentication system, combined with the ISO/IEC standard, the operating system kernel is evaluated and certified, which solves the problems of memory leakage and insufficient security checks in C/C++ language, and achieves efficient and secure kernel authentication.
Patent Information
- Application Number
- CN202510598022.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2025-08-22
AI Technical Summary
The existing operating system kernel uses C/C++ language and lacks the necessary security check mechanism, resulting in memory leaks, dangling pointers, and competition conditions, affecting functional security and information security.
The operating system kernel authentication system based on the RUST language is adopted, and the security characteristics of the Rust language are used to evaluate and authenticate the operating system kernel through the quality evaluation module and the security evaluation module, combined with the ISO/IEC standard, including static code analysis, functional security evaluation and information security evaluation.
It effectively reduces the number of rules for coding specifications, reduces the evaluation workload, improves evaluation efficiency, and ensures the safety and reliability of authentication results through the security characteristics of the Rust language, reducing the possibility of errors in the development stage.
Smart Images

Figure CN120523706A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of system software authentication, and in particular to an operating system kernel authentication system based on RUST language. Background Art
[0002] The operating system is an important piece of basic software and a key component of computer systems. Within an operating system, the kernel plays an indispensable role, managing computer hardware resources, encapsulating them, and providing services to upper-level applications via system calls. This allows applications to ignore hardware details and focus on their own functions. At the same time, by encapsulating the hardware, the operating system can implement functions such as hardware resource protection and application isolation, thereby ensuring the security of the computer system. Currently, commonly used operating systems, such as Windows and Linux, are primarily implemented in the C language. However, due to their overly flexible design, C / C++ lacks the necessary security checking mechanisms, which can lead to problems such as memory leaks, dangling pointers, and race conditions, compromising the functional and information security of the operating system kernel.
[0003] Therefore, an operating system kernel authentication system based on RUST language is provided to solve the above problems. Summary of the Invention
[0004] In order to solve the above problems, the present invention provides an operating system kernel authentication system based on the RUST language, which is designed for the Rust language, fully utilizes the security features contained in the Rust language design, reduces redundant judgments on the program security features guaranteed by the Rust compiler, and thus reduces the workload of the authentication process.
[0005] To achieve the above objectives, the present invention provides an operating system kernel authentication system based on RUST language, including a quality assessment module and a security assessment module. The quality assessment module adopts different assessment methods according to whether the target kernel source code is public;
[0006] For open source operating systems, we use RUST-based coding standards to perform static code analysis on the kernel of the open source operating system, and then evaluate it through the quality assessment solution;
[0007] For operating system kernels whose internal codes are not publicly available, the system kernel is evaluated based on the order of designated evaluation, planned evaluation, and executed evaluation defined in the ISO / IEC 25040 standard.
[0008] The safety assessment module is based on IEC 61508 and ISO / IEC 15408 standards, and evaluates the functional safety and information security of the operating system kernel respectively.
[0009] Preferably, the functional safety assessment includes determining whether it can be verified through empirical use, whether there are existing certifications that can be referenced, and generating a functional safety assessment report;
[0010] Information security assessment includes obtaining or forming a compliant protection profile, obtaining compliant security objectives, verifying the consistency of the protection profile and security objectives, and generating an information security assessment report.
[0011] Preferably, the authentication system performs a quality assessment step and a security assessment step. The quality assessment step evaluates the coding standardization, functional integrity, maintainability, and scalability of the operating system kernel; the security assessment step evaluates the functional safety and information security of the operating system, including the security of its own design and the ability to ensure the confidentiality, integrity, and availability of the system kernel data in the face of potential security threats, specifically expressed as follows:
[0012] S1: Verify whether the kernel of the target operating system is an open source kernel. If it is an open source kernel, perform a quality assessment based on the Rust language coding standards and the open source operating system quality assessment scheme, and generate a quality assessment report.
[0013] For commercial closed-source operating system kernels, develop a quality assessment process based on ISO / IEC 25040, execute a quality assessment plan based on ISO / IEC 25051, and generate a quality assessment report.
[0014] S2: Perform functional safety assessment based on IEC 61508 and information security assessment based on ISO / IEC 15408, and generate security assessment reports for each.
[0015] S3: Combine the safety assessment report and quality assessment report to obtain the certification report.
[0016] Preferably, in the quality assessment step, the target kernel is an open source kernel, and the following steps are specifically performed:
[0017] Step 1: Analyze the kernel code according to the Rust language coding standards. If any code violates the coding standards, modify it before continuing the evaluation.
[0018] Step 2: Analyze the kernel based on the open source operating system quality assessment scheme, define the system kernel according to the assessment indicators, execute the operational process of the assessment scheme, determine whether the assessment results meet the requirements, and finally generate a quality assessment report;
[0019] The target kernel is a commercial closed-source operating system kernel. When performing quality assessment, the following steps are performed:
[0020] (1) Establish quality assessment requirements based on ISO / IEC 25051 standards and generate quality assessment requirements documents;
[0021] (2) Perform quality assessment according to the process guided by ISO / IEC 25040, which includes the following steps: determining assessment needs, planning assessment plans, performing quality assessments, and generating assessment results;
[0022] (3) After performing the quality assessment, if the quality results meet the requirements, a quality assessment report is generated; if the results do not meet the requirements, modifications are made based on the assessment results and the quality assessment process is re-executed until the quality standards are met.
[0023] Preferably, the functional safety assessment performs the following steps:
[0024] Determine whether the kernel has the conditions for long-term stable use. If the kernel is stable, continue to prepare the usage experience certification report based on the IEC 61508 standard; if the kernel is unstable, check whether the kernel has been certified under other standards. If the kernel has been certified under other standards, continue to process the Rust software component documentation; if the kernel has not been certified under other standards, evaluate whether the kernel meets the requirements of IEC 61508. If it meets the requirements, continue with the complete evaluation process in the IEC 61508 plan, and finally complete the functional safety evaluation and generate a functional safety report; if it does not meet the IEC 61508 requirements, evaluate the kernel functional safety based on the existing certification results, generate a functional safety report and complete the certification.
[0025] Preferably, the information security assessment performs the following steps:
[0026] ① Determine whether the protection configuration file of the target operating system kernel exists. If not, create a protection configuration file first. If it exists, directly obtain the protection configuration file based on the Rust language;
[0027] ② Determine whether the security target of the target operating system exists. If not, try to modify the development security document provided by the developer to use as the security target. If it exists, directly obtain the security target;
[0028] ③ After obtaining the corresponding files, it is necessary to verify that the security goals exist and are compliant. At the same time, it is necessary to verify the consistency of the security goals and the protection configuration files, and then verify the consistency of the security function requirements and security protection requirements of the system kernel. If the consistency verification has non-compliant results, it is necessary to re-execute the information security assessment process to finally obtain the assessment results of the information security of the operating system when facing external threats.
[0029] The Rust coding standards include five categories and 11 subcategories, with 30 coding rules. The five categories are naming rules, type safety, expressions, control flow and functions, and other categories; the 11 subcategories involve comments, identifiers, characters and constants, definitions and declarations, basic type models, expressions, side effects, control statements, control flow and match statements, functions, and other categories.
[0030] The Comments subclass in the Naming Rules category defines the writing standards for comments in Rust, using documentation comments and tags to distinguish comments for different purposes;
[0031] Identifier subclasses provide naming methods for variables, functions, constants, structures, enumerations, modules, generic type parameters, and lifetime parameters.
[0032] Preferably, the type safety category includes three subcategories: characters and constants, definitions and declarations, and basic type models;
[0033] Character and constant subclasses require additional annotations for unsigned integers, and string constants are read-only;
[0034] The definition and declaration of subclasses emphasize the use of the pub keyword, and it is recommended that internal variables are not made public;
[0035] The basic type model subclass requires that operands must not be of improper basic types to avoid undefined behavior of shift overflow.
[0036] Preferably, the expression category includes expression and side effect subcategories. The expression subcategory requires clear operator priority to avoid overly deeply nested expressions; the side effect subcategory requires that the value of the expression is consistent with the side effect to avoid modifying the same object multiple times, and requires that the right operand of the logical operation cannot have side effects.
[0037] Preferably, the control flow and function category includes three subcategories: control statement expressions, control flow and match statements, and functions;
[0038] The control statement sub-expression class requires that the basic type of the loop counter avoid using floating-point types, and it is recommended to use the for...in statement instead of the while loop; the control flow and match statement sub-class requires that the function has a single exit, all if...elseif structures should end with else, and the match statement must have at least two branches; the function sub-class avoids recursive calls; if the function returns a non-empty tuple, the return value must be used, otherwise the unused return value should be deleted.
[0039] Therefore, the present invention adopts the above-mentioned RUST language-based operating system kernel authentication system, which includes the following beneficial effects:
[0040] (1) The present invention proposes a Rust language coding specification, which fully utilizes the security properties mandatory for Rust and effectively reduces the number of rules in the coding specification, thereby reducing the workload when applying the coding specification and improving the evaluation efficiency.
[0041] (2) The present invention fully considers the process of using additional information in various standard documents to simplify the authentication process. When the target operating system kernel has other additional auxiliary authentication information, the total amount of authentication work can be effectively reduced.
[0042] (3) The present invention utilizes various features contained in the Rust language to ensure the security and reliability of the authentication results. The Rust language features used include but are not limited to an ownership system, syntax rules, and a type checker. Among them, the ownership system prevents problems such as data competition, memory leaks, and dangling pointers by ensuring that each data has only one owner and automatically releasing resources at the end of its life cycle. By applying the document comments, naming rules, and syntax rules such as control statements that have undergone additional checks provided by Rust, the possibility of errors in the development phase is reduced. Rust's type system performs strict checks at compile time, which can capture problems such as type errors, null pointer dereferences, and mismatched function parameters, reducing runtime errors.
[0043] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] Figure 1 This is an overall flow chart of an operating system kernel authentication system based on RUST language in the present invention;
[0045] Figure 2 This is a flowchart of kernel quality assessment in an embodiment of the present invention;
[0046] Figure 3 This is a flowchart of functional safety assessment in an embodiment of the present invention;
[0047] Figure 4 This is a flowchart of information security assessment in an embodiment of the present invention. DETAILED DESCRIPTION
[0048] The technical solution of the present invention is further described below with reference to the accompanying drawings and embodiments.
[0049] Unless otherwise defined, technical or scientific terms used in the present invention shall have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs.
[0050] The words “include” or “comprising” and similar words used in the present invention mean that the elements before the word include the elements listed after the word, and do not exclude the possibility of also including other elements. The orientation or position relationship indicated by the terms “inside”, “outside”, “upper”, “lower”, etc. is based on the orientation or position relationship shown in the accompanying drawings. It is only for the convenience of describing the present invention and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, it cannot be understood as a limitation of the present invention. When the absolute position of the described object changes, the relative position relationship may also change accordingly. In the present invention, unless otherwise clearly stipulated and limited, the terms such as “attachment” should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral whole; it can be directly connected or indirectly connected through an intermediate medium, and it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to the specific circumstances.
[0051] Example
[0052] like Figure 1 As shown, an operating system kernel certification system based on RUST language includes a quality assessment module and a security assessment module. The quality assessment module adopts different assessment methods according to whether the target kernel source code is public.
[0053] For open source operating systems, we use RUST-based coding standards to perform static code analysis on the kernel of the open source operating system, and then evaluate it through the quality assessment solution;
[0054] For operating system kernels whose internal codes are not publicly available, the system kernel is evaluated based on the order of designated evaluation, planned evaluation, and executed evaluation defined in the ISO / IEC 25040 standard.
[0055] The safety assessment module is based on IEC 61508 and ISO / IEC 15408 standards, and evaluates the functional safety and information security of the operating system kernel respectively.
[0056] Functional safety assessment includes determining whether it can be verified through empirical use, whether there are existing certifications that can be referenced, and generating a functional safety assessment report;
[0057] Information security assessment includes obtaining or forming a compliant protection profile, obtaining compliant security objectives, verifying the consistency of the protection profile and security objectives, and generating an information security assessment report.
[0058] The certification system performs quality assessment and security assessment steps. The quality assessment step evaluates the coding standardization, functional integrity, maintainability, and scalability of the operating system kernel. The security assessment step evaluates the functional safety and information security of the operating system, including the security of its own design and its ability to ensure the confidentiality, integrity, and availability of system kernel data in the face of potential security threats. Specifically, it is expressed as follows:
[0059] S1: Verify whether the kernel of the target operating system is an open source kernel. If it is an open source kernel, perform a quality assessment based on the Rust language coding standards and the open source operating system quality assessment scheme, and generate a quality assessment report.
[0060] The Rust coding standards include five categories and 11 subcategories, with 30 coding rules. The five categories are naming rules, type safety, expressions, control flow and functions, and other categories; the 11 subcategories involve comments, identifiers, characters and constants, definitions and declarations, basic type model, expressions, side effects, control statements, control flow and match statements, functions, and other categories.
[0061] The Comments subclass in the Naming Rules category defines the writing standards for comments in Rust, using documentation comments and tags to distinguish comments for different purposes;
[0062] The identifier subclass provides naming methods for variables, functions, constants, structures, enumerations, modules, generic type parameters, and lifetime parameters, emphasizing that internal and external variable names should avoid duplication.
[0063] The type safety category includes three subcategories: characters and constants, definitions and declarations, and basic type models;
[0064] Character and constant subclasses require additional annotations for unsigned integers, and string constants are read-only;
[0065] The definition and declaration of subclasses emphasize the use of the pub keyword, and it is recommended that internal variables are not made public;
[0066] The basic type model subclass requires that operands must not be of improper basic types to avoid undefined behavior of shift overflow.
[0067] The expression category includes expression and side effect subcategories. The expression subcategory requires clear operator priority to avoid deeply nested expressions and prevent errors caused by constant overflow. The side effect subcategory requires that the value of the expression is consistent with the side effect, avoids modifying the same object multiple times, and requires that the right operand of the logical operation cannot have side effects to prevent side effects from being omitted during the optimization process.
[0068] The control flow and function category includes three subcategories: control statement expressions, control flow and match statements, and functions;
[0069] The control statement sub-expression class requires that the basic type of the loop counter avoid using floating-point types, and it is recommended to use the for...in statement instead of the while loop; the control flow and match statement sub-class requires that the function has a single exit, all if...elseif structures should end with else, and the match statement must have at least two branches; the function sub-class avoids recursive calls; if the function returns a non-empty tuple, the return value must be used, otherwise the unused return value should be deleted.
[0070] For commercial closed-source operating system kernels, develop a quality assessment process based on ISO / IEC 25040, execute a quality assessment plan based on ISO / IEC 25051, and generate a quality assessment report.
[0071] S2: Perform functional safety assessment based on IEC 61508 and information security assessment based on ISO / IEC 15408, and generate security assessment reports for each.
[0072] S3: Combine the safety assessment report and quality assessment report to obtain the certification report.
[0073] When using the Rust coding standards to review operating system kernel code, all codes should be checked one by one to ensure that all coding standards are used in all kernel code.
[0074] The Rust open-source operating system quality assessment scheme is distinguished by evaluating the operating system kernel from multiple perspectives, comprehensively demonstrating its quality. This assessment encompasses coding standards, version control, documentation, resource allocation, domain isolation, synchronization primitives, testing and verification, and community activity. These evaluation criteria provide a comprehensive assessment of the operating system kernel's code quality, maintainability, and support capabilities.
[0075] To ensure the required quality standards, operating systems must demonstrate excellent usability and excel across a wide range of features. Usability requirements include clearly defined operating system behavior, adaptability to application characteristics, and sufficient integrity to ensure system security. Features include execution and scheduling, resource management, internal and external communication, domain isolation, real-time performance, security, user interface, and robustness. Specific evaluation criteria include coding conventions, version control, documentation, resource allocation, scheduling strategies, domain separation, synchronization primitives, verification, system configuration, and community activity.
[0076] When executing the assessment plan, follow these steps: Determine the software quality and community maturity of the target kernel based on the system characteristics and the assessment criteria. Create a specification for the expected system behavior, or if a detailed specification already exists, there is no need to create a new one. Create tests to verify the functionality of the operating system, with the tests traceable to the specification. If existing tests are insufficient, develop additional tests. Execute the test cases to verify functionality and make corrections as necessary. Perform manual code inspections, focusing on high-complexity areas and code that does not conform to the Rust coding standards. Execute the tests and collect test coverage data. Finally, perform a compliance analysis and compare against the functional safety standard.
[0077] like Figure 2 As shown, in the quality assessment step, if the target kernel is an open source kernel, the following steps are specifically performed:
[0078] Step 1: Analyze the kernel code according to the Rust language coding standards. If any code violates the coding standards, modify it before continuing the evaluation.
[0079] The coding standards of the Rust language are modified based on the MISRA C standards and combined with the unique security features of the Rust language to form a set of coding standards suitable for Rust.
[0080] Step 2: Analyze the kernel based on the open source operating system quality assessment scheme, define the system kernel according to the assessment indicators, execute the operational process of the assessment scheme, determine whether the assessment results meet the requirements, and finally generate a quality assessment report;
[0081] If the target kernel is a commercial closed-source operating system kernel, perform the following steps when performing quality assessment:
[0082] (1) Establish quality assessment requirements based on ISO / IEC 25051 standards and generate quality assessment requirements documents;
[0083] (2) Perform quality assessment according to the process guided by ISO / IEC 25040, which includes the following steps: determining assessment needs, planning assessment plans, performing quality assessments, and generating assessment results;
[0084] (3) After performing the quality assessment, if the quality results meet the requirements, a quality assessment report is generated; if the results do not meet the requirements, modifications are made based on the assessment results and the quality assessment process is re-executed until the quality standards are met.
[0085] like Figure 3 As shown, the functional safety assessment performs the following steps:
[0086] Determine whether the kernel is suitable for long-term stable use. If the kernel is stable, proceed with the use experience certification report based on the IEC 61508 standard. If the kernel is unstable, check whether the kernel has been certified under other standards. If the kernel has been certified under other standards, continue processing the Rust software component documentation. If the kernel has not been certified under other standards, evaluate whether the kernel meets the requirements of IEC 61508. If it does, continue with the full assessment process in the IEC 61508 plan, and ultimately complete the functional safety assessment and generate a functional safety report. If it does not meet the requirements of IEC 61508, evaluate the kernel functional safety based on the existing certification results, generate a functional safety report, and complete the certification. The entire process ensures that the functional safety certification of the Rust language operating system kernel is effectively implemented under the premise of compliance with the IEC 61508 standard.
[0087] like Figure 4 As shown, an information security assessment performs the following steps:
[0088] ① Determine whether the protection configuration file of the target operating system kernel exists. If not, create a protection configuration file first. If it exists, directly obtain the protection configuration file based on the Rust language;
[0089] ② Determine whether the security target of the target operating system exists. If not, try to modify the development security document provided by the developer to use as the security target. If it exists, directly obtain the security target;
[0090] ③ After obtaining the corresponding files, it is necessary to verify that the security goals exist and are compliant. At the same time, it is necessary to verify the consistency of the security goals and the protection configuration files, and then verify the consistency of the security function requirements and security protection requirements of the system kernel. If the consistency verification has non-compliant results, it is necessary to re-execute the information security assessment process to finally obtain the assessment results of the information security of the operating system when facing external threats.
[0091] After completing the above steps, the quality assessment report, functional safety report, and information security report are finally integrated to obtain the final Rust language operating system kernel certification report.
[0092] This embodiment is based on a self-developed teaching operating system kernel, which is an open source kernel developed based on the Rust language. It is divided into three layers: hardware driver, Rust-based security kernel, and user program. The hardware driver part includes RISC-V page table, interrupt controller, serial port and disk driver. The Rust-based security kernel includes three parts: memory management module, process management module and file management module. The memory management module is divided into physical memory management and virtual memory management parts; the process management module is divided into process control and synchronization and interrupt handling and process scheduling parts; the file management module is divided into physical file system and virtual file system parts. The modules in the kernel provide services to the user space in the form of system call interface.
[0093] Since the target kernel is an open-source kernel, the kernel code is first analyzed according to the Rust language coding standards. If any violations are found, they are modified before continuing the evaluation. Next, the kernel is analyzed based on the open-source operating system quality assessment protocol. Specifically, the system kernel is first restricted according to the assessment criteria, and then the assessment protocol's operational procedures are executed. After completing this process, the evaluation results are determined to meet the requirements, and a quality assessment report is generated.
[0094] According to the process, a safety assessment is next performed. First, the core is determined to be stable and long-term. In reality, the core is only used for educational purposes and has not been used stably for a long time. The core is then evaluated to determine whether it has been certified under other standards. Since the core has not yet been certified under any standard, a complete assessment process is planned according to IEC 61508. A full functional safety assessment is then performed according to IEC 61508, and a functional safety report is generated based on the assessment results.
[0095] Continue with the information security assessment. First, obtain a protection profile based on ISO / IEC 15408. Since no existing protection profile exists for the target kernel, generate one for that kernel. Then, obtain the security target based on ISO / IEC 15408. Since no existing security target document exists, modify the development security document and use it as the security target. Determine whether the modified version meets the ISO / IEC 15408 security target requirements. If so, verify the consistency of the protection profile with the security target based on ISO / IEC 15408. Then, verify the consistency of the security functional requirements with the security protection requirements. Finally, generate an information security report based on the assessment results.
[0096] Integrate the above three reports to obtain the final certification report and complete the kernel certification.
[0097] Therefore, the present invention adopts the above-mentioned RUST language-based operating system kernel authentication system, fully utilizing the security features contained in the Rust language design, reducing redundant judgments on the program security features guaranteed by the Rust compiler, and thus reducing the workload of the authentication process.
[0098] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit the same. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that they can still modify or replace the technical solutions of the present invention with equivalents, and these modifications or equivalent replacements cannot cause the modified technical solutions to deviate from the spirit and scope of the technical solutions of the present invention.
Claims
1. An operating system kernel authentication system based on RUST language, characterized in that: It includes a quality assessment module and a security assessment module. The quality assessment module uses different assessment methods based on whether the target kernel source code is public. For open source operating systems, we use RUST-based coding standards to perform static code analysis on the kernel of the open source operating system, and then evaluate it through the quality assessment solution; For operating system kernels whose internal codes are not publicly available, the system kernel is evaluated based on the order of designated evaluation, planned evaluation, and executed evaluation defined in the ISO / IEC 25040 standard. The safety assessment module is based on IEC 61508 and ISO / IEC 15408 standards, and evaluates the functional safety and information security of the operating system kernel respectively.
2. The RUST language-based operating system kernel authentication system according to claim 1, characterized in that: Functional safety assessment includes determining whether it can be verified through empirical use, whether there are existing certifications that can be referenced, and generating a functional safety assessment report; Information security assessment includes obtaining or forming a compliant protection profile, obtaining compliant security objectives, verifying the consistency of the protection profile and security objectives, and generating an information security assessment report.
3. The operating system kernel authentication system based on RUST language according to claim 2, characterized in that: The certification system performs quality assessment and security assessment steps. The quality assessment step evaluates the coding standardization, functional integrity, maintainability, and scalability of the operating system kernel. The security assessment step evaluates the functional safety and information security of the operating system, including the security of its own design and its ability to ensure the confidentiality, integrity, and availability of system kernel data in the face of potential security threats. Specifically, it is expressed as follows: S1: Verify whether the kernel of the target operating system is an open source kernel. If it is an open source kernel, perform a quality assessment based on the Rust language coding standards and the open source operating system quality assessment scheme, and generate a quality assessment report. For commercial closed-source operating system kernels, develop a quality assessment process based on ISO / IEC 25040, execute a quality assessment plan based on ISO / IEC 25051, and generate a quality assessment report. S2: Perform functional safety assessment based on IEC 61508 and information security assessment based on ISO / IEC 15408, and generate security assessment reports for each. S3: Combine the safety assessment report and quality assessment report to obtain the certification report.
4. The RUST language-based operating system kernel authentication system according to claim 3, characterized in that: In the quality assessment step, the target kernel is an open source kernel, and the following steps are performed: Step 1: Analyze the kernel code according to the Rust language coding standards. If any code violates the coding standards, modify it before continuing the evaluation. Step 2: Analyze the kernel based on the open source operating system quality assessment scheme, define the system kernel according to the assessment indicators, execute the operational process of the assessment scheme, determine whether the assessment results meet the requirements, and finally generate a quality assessment report; The target kernel is a commercial closed-source operating system kernel. When performing quality assessment, the following steps are performed: (1) Establish quality assessment requirements based on ISO / IEC 25051 standards and generate quality assessment requirements documents; (2) Perform quality assessment according to the process guided by ISO / IEC 25040, which includes the following steps: determining assessment needs, planning assessment plans, performing quality assessments, and generating assessment results; (3) After performing the quality assessment, if the quality results meet the requirements, a quality assessment report is generated; If the results do not meet the requirements, modifications will be made based on the evaluation results and the quality assessment process will be re-executed until the quality standards are met.
5. The RUST language-based operating system kernel authentication system according to claim 3, characterized in that: Functional safety assessment performs the following steps: Determine whether the kernel is suitable for long-term stable use. If the kernel is stable, proceed to the use experience certification report based on the IEC 61508 standard. If the kernel is unstable, check whether the kernel has been certified under other standards. If the kernel has been certified under other standards, continue to process the Rust software component documentation. If the kernel has not been certified under other standards, evaluate whether the kernel meets the requirements of IEC 61508. If it does meet the requirements, continue with the full assessment process in the IEC 61508 plan, and finally complete the functional safety assessment and generate a functional safety report. If the IEC 61508 requirements are not met, the core functional safety is evaluated based on the existing certification results, a functional safety report is generated, and certification is completed.
6. The RUST language-based operating system kernel authentication system according to claim 3, characterized in that: An information security assessment performs the following steps: ① Determine whether the protection configuration file of the target operating system kernel exists. If not, create a protection configuration file first. If it exists, directly obtain the protection configuration file based on the Rust language; ② Determine whether the security target of the target operating system exists. If not, try to modify the development security document provided by the developer to use as the security target. If it exists, directly obtain the security target; ③ After obtaining the corresponding files, it is necessary to verify that the security goals exist and are compliant. At the same time, it is necessary to verify the consistency of the security goals and the protection configuration files, and then verify the consistency of the security function requirements and security protection requirements of the system kernel. If the consistency verification has non-compliant results, it is necessary to re-execute the information security assessment process to finally obtain the assessment results of the information security of the operating system when facing external threats.
7. The RUST language-based operating system kernel authentication system according to claim 3, characterized in that: The Rust coding standards include five categories and 11 subcategories, with 30 coding rules. The five categories are naming rules, type safety, expressions, control flow and functions, and other categories. 11 subcategories involving comments, identifiers, characters and constants, definitions and declarations, basic type models, expressions, side effects, control statements, control flow and match statements, functions and other categories; The Comments subclass in the Naming Rules category defines the writing standards for comments in Rust, using documentation comments and tags to distinguish comments for different purposes; Identifier subclasses provide naming methods for variables, functions, constants, structures, enumerations, modules, generic type parameters, and lifetime parameters.
8. The RUST language-based operating system kernel authentication system according to claim 7, characterized in that: The type safety category includes three subcategories: characters and constants, definitions and declarations, and basic type models; Character and constant subclasses require additional annotations for unsigned integers, and string constants are read-only; The definition and declaration of subclasses emphasize the use of the pub keyword, and it is recommended that internal variables are not made public; The basic type model subclass requires that operands must not be of improper basic types to avoid undefined behavior of shift overflow.
9. The RUST language-based operating system kernel authentication system according to claim 7, characterized in that: The expression category includes expression and side effect subcategories. The expression subcategory requires clear operator priority to avoid overly deeply nested expressions; the side effect subcategory requires that the value of the expression is consistent with the side effect to avoid multiple modifications to the same object, and requires that the right operand of the logical operation cannot have side effects.
10. The RUST language-based operating system kernel authentication system according to claim 7, characterized in that: The control flow and function category includes three subcategories: control statement expressions, control flow and match statements, and functions; The control statement sub-expression class requires that the basic type of the loop counter avoid using floating-point types, and it is recommended to use the for...in statement instead of the while loop; the control flow and match statement sub-class requires that the function has a single exit, all if...else if structures should end with else, and the match statement must have at least two branches; the function sub-class avoids recursive calls; if the function returns a non-empty tuple, the return value must be used, otherwise the unused return value should be deleted.
