是面向计算产业的机密计算安全应用开发套件，屏蔽不同的 TEE（Trusted Execution Environment）SDK 差 异提供统一的开发框架，同时提供开发工具、通用安全组件等，帮助安全应用开发者聚焦业务，提升开发效率。 secGear 的整体架构如图所示，主要提供三大能力： • 架构兼容：屏蔽不同 SDK 接口差异，提供统一开发接口，实现不同架构共源码。 • 易开发：提供开发工具、通用安全组件等，帮助用户聚焦业务，开发效率显著提升。 置根密钥签名，防止证明报告被篡改或伪造。 secGear 远程证明基于各厂商 SDK 远程证明能力，封装统一远程证明接口，当前仅支持鲲鹏平台，其中 secGear 依赖 kunpengsecl 的 TEE 验证库来验证证明报告。 secGear 远程证明与 kunpengselc TEE 远程证明区别在于：secGear 是统一开发框架，提供统一远程证明 SDK 接口（获 取远程证明报告、校验报告接口），供客户基于 提供鲲鹏平台的远程证明服务、证明报告校验，可供用户直接部署使用。 场景 开发 框架 SDK 硬件 secGear Unified Framework Component & Service SDK Unified API SGX SDK Intel SGX 鲲鹏Trustzone 华为云 擎天Enclave TEEOS SDK Qingtian SDK 金融风控 安全通道 开发工具 零切换 远程证明 新增特性

CANN、CUDA 等硬件 SDK，以及 TensorFlow、PyTorch 等相应的 AI 框架软件，支持 AI 应用在 openEuler 上高效开发与运行。 2. openEuler AI 软件栈容器化封装优化环境部署过程，并面向不同场景提供以下三类容器镜像。 OS for AI • SDK 镜像：以 openEuler 为基础镜像，安装相应硬件平台的 SDK，如 Ascend 平台的 平台的 CANN 或 NVIDIA 的 CUDA 软件。 • AI 框架镜像：以 SDK 镜像为基础，安装 AI 框架软件，如 PyTorch 或 TensorFlow。 • 模型应用镜像：在 AI 框架镜像的基础上，包含完整的工具链和模型应用。 相关使用方式请参考 openEuler AI 容器镜像用户指南。 openEuler 使能 AI，向用户提供更多 OS 选择。基于 openEuler openEuler 的 AI 容器镜像可以解决开发运行环境部署门槛高的问题，用 户根据自身需求选择对应的容器镜像即可一键部署，三类容器镜像的应用场景如下。 • SDK 镜像：提供对应硬件的计算加速工具包和开发环境，用户可进行 Ascend CANN 或 NVIDIA CUDA 等应用的开发和调试。同时， 可在该类容器中运行高性能计算任务，例如大规模数据处理、并行计算等。 • AI 框架镜像：用户可直接在该类容器中进行

Typical usage ★ Limitations What is Yocto? ● Tooling for building your own Linux distribution and SDK ● Defines a format that eases sharing of compile recipes and patches ● Powerful configuration management binary packages like special gstreamer plugins are available ● SDCard / UBI / etc. image generation ● SDK generation and licence information and source package extraction ● Reduce image footprint ● Own application binary packages like special gstreamer plugins are available ● SDCard / UBI / etc. image generation ● SDK generation and licence information and source package extraction ● Reduce image footprint ● Own application

course of normal development. • Updated Microsoft Windows Platform SDK, February 2003 or later. An appropriate Windows Platform SDK is included by default in the full (not express/lite) versions of Visual version of the Platform SDK. To use Visual C++ 6.0 or 7.0 (Studio 2000 .NET), the Platform SDK environment must be prepared using the setenv.bat script (installed by the Platform SDK) before starting the the command line build or launching the msdev/devenv GUI environment. Installing the Platform SDK for Visual Studio Express versions (2003 and later) should adjust the default environment appropriately.

course of normal development. • Updated Microsoft Windows Platform SDK, February 2003 or later. An appropriate Windows Platform SDK is included by default in the full (not express/lite) versions of Visual version of the Platform SDK. To use Visual C++ 6.0 or 7.0 (Studio 2000 .NET), the Platform SDK environment must be prepared using the setenv.bat script (installed by the Platform SDK) before starting the the command line build or launching the msdev/devenv GUI environment. Installing the Platform SDK for Visual Studio Express versions (2003 and later) should adjust the default environment appropriately.

the course of normal development. Updated Microsoft Windows Platform SDK, February 2003 or later. An appropriate Windows Platform SDK is included by default in the full (not express/lite) versions of Visual version of the Platform SDK. To use Visual C++ 6.0 or 7.0 (Studio 2000 .NET), the Platform SDK environment must be prepared using the setenv.bat script (installed by the Platform SDK) before starting the the command line build or launching the msdev/devenv GUI environment. Installing the Platform SDK for Visual Studio Express versions (2003 and later) should adjust the default environment appropriately.

the course of normal development. Updated Microsoft Windows Platform SDK, February 2003 or later. An appropriate Windows Platform SDK is included by default in the full (not express/lite) versions of Visual version of the Platform SDK. To use Visual C++ 6.0 or 7.0 (Studio 2000 .NET), the Platform SDK environment must be prepared using the setenv.bat script (installed by the Platform SDK) before starting the the command line build or launching the msdev/devenv GUI environment. Installing the Platform SDK for Visual Studio Express versions (2003 and later) should adjust the default environment appropriately.

the course of normal development. Updated Microsoft Windows Platform SDK, February 2003 or later. An appropriate Windows Platform SDK is included by default in the full (not express/lite) versions of Visual version of the Platform SDK. To use Visual C++ 6.0 or 7.0 (Studio 2000 .NET), the Platform SDK environment must be prepared using the setenv.bat script (installed by the Platform SDK) before starting the the command line build or launching the msdev/devenv GUI environment. Installing the Platform SDK for Visual Studio Express versions (2003 and later) should adjust the default environment appropriately.

the course of normal development. Updated Microsoft Windows Platform SDK, February 2003 or later. An appropriate Windows Platform SDK is included by default in the full (not express/lite) versions of Visual version of the Platform SDK. To use Visual C++ 6.0 or 7.0 (Studio 2000 .NET), the Platform SDK environment must be prepared using the setenv.bat script (installed by the Platform SDK) before starting the the command line build or launching the msdev/devenv GUI environment. Installing the Platform SDK for Visual Studio Express versions (2003 and later) should adjust the default environment appropriately.

the course of normal development. Updated Microsoft Windows Platform SDK, February 2003 or later. An appropriate Windows Platform SDK is included by default in the full (not express/lite) versions of Visual version of the Platform SDK. To use Visual C++ 6.0 or 7.0 (Studio 2000 .NET), the Platform SDK environment must be prepared using the setenv.bat script (installed by the Platform SDK) before starting the the command line build or launching the msdev/devenv GUI environment. Installing the Platform SDK for Visual Studio Express versions (2003 and later) should adjust the default environment appropriately.