Optigatrust

Latest version: v1.5.1

Safety actively analyzes 724051 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

4.1.0

* PSoC PALs were removed from the PALs directory and shall be now part of the application

3.1.4

* Fixed 62S2 Pin assignment for the Power Control
* Fixed wrong ASN.1 ECDSA Signature size (r and s components) calculation.
* Datasheet Update
* (Linux PAL) Fixed the Segmentation fault for 64bits Linux system
* (Linux PAL) Added libgpiod support

3.1.3

* Fix i2c initialization routine for the PSoC6 FreeRTOS component
* Add the OPTIGA™ Trust IoT Security Development Kit link to the readme

3.1.2

* After the 3.01.2558 release of the core, I2C address structure member in the PAL changed its place, this release fixes it.

3.1.1

* Fix building "Error[Pe513]: a value of type "void (*)(void *, uint16_t)" cannot be assigned to an entity of type "void *"" Error in the optiga/comms/ifx_i2c/ifx_i2c_physical_layer.c file

3.1.0

* Based on the 3.01.2558 release of the core communication stack plus additional tools and PALs
* Missing of error handling for pal_i2c_init failure keeps the local host application in hung state when optiga_util_open_application is invoked.
* ifx_i2c_context structure and other structure members are not arranged in the descending order of their sizes, leading to incorrect memory access in case of few compilers.
* Re-entrancy issues in execution handler of OPTIGA™ command layer and ifx_i2c layer in linux environment, when the CPU load is high.
* In Protected update tool, unicast option is considered as Octet string instead of hex array, creating an invalid Manifest.
* Few of the resources created/initialized as part of optiga_util_create / optiga_crypt_create / optiga_util_open_application are not de-allocated / destroyed as part of optiga_util_destroy / optiga_crypt_destroy / optiga_util_close_application, creating problems in multi-process linux execution environment.


Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic
Versioning](https://semver.org/spec/v2.0.0.html).

Page 2 of 3

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.