Trust Platform Design Suite - Kudelski keySTREAM connect Extension
This module contains the frontend, backend services and resources required for keySTREAM connect extension.
Release Notes
Release 1.3.2
- Firmware updates to support Upgrade and Downgrading through campaigns
- keySTREAM campaign handling fix through create and delete campaigns
Release 1.3.1
- FoTA usecase improvements to address WiFi connection issues
Release 1.3.0
- Added FoTA with keySTREAM Usecase
- CryptoAuth Pro Trust Platform (EV89U05A) board support is added
Release v1.2.0
- Added support for public key provisioning
- Added support for shared symmetric key provisioning
- Updated 2 tier PKI documentation
- Updated usecase help for added features
- Added fixes for issues on usecase (linux/osx)
- Added firmware binary needed for factory programming
Release v1.1.2
- Added AWS ATS support
- Fixed video links on Usecase
- Updated MoQ and Certificate details for Secure Exchange Process
Release v1.1.1
- Added 2-Tier PKI support
- Transition from UTC time to Generalized time
- Other minor bug fixes
Release v1.0.2
- Step 2 Usecase bug fixes for new installation
- Usecase learn video updated to YT keySTREAM video
Release v1.0.1
- Updated WINC firmware update utility
- Removed device reset requirement on step 1 (Usecase TD)
- Updated form for user input on step 2 (Usecase TD)
- Updated Usecase help documentation
Release v1.0.0
Updates
Device Onboarding
- Device Onboarding is the process by which a device is registered in keySTREAM server with a certain device identity and attached to a certain device vendor. Device onboarding is performed automatically by keySTREAM as part of the in-field device identity provisioning process.
Device Certificate Renewal
- A new certificate will be generated and provisioned to the device before the old one expires. Renewing a certificate does not mean changing the associated key pair. **The key pair stays the same.**
Device Refurbish
- A device can be brought back to factory provisioned state at any time using the device refurbishment functionality.
Optional Multi Device Profile Public Uid
- Added Mutable Device Profile Public UID Feature in KTA.
CAL Update 3.7.4
- KTA code has been integrated with Cryptoauthlib (3.7.4).
Fixes
- Changes Done to Support Integration of KTA with Latest Cryptoauthlib (3.7.4)
- Fixed Compilation Warnings
- Updated Doxygen Header's for KTA Source Files
- Device Reboot issue fixed
- Key Renewal issue fixed
- Expiry Date issue fixed
1 maintainer
Metadata
1 maintainer
Release files for tpds-extension-keystream-connect 1.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tpds_extension_keystream_connect-1.3.2-py3-none-any.whl | Python 3 | none | any | Details for tpds_extension_keystream_connect-1.3.2-py3-none-any.whl |
Release files / tpds_extension_keystream_connect-1.3.2-py3-none-any.whl
| Download URL | tpds_extension_keystream_connect-1.3.2-py3-none-any.whl |
|---|---|
| Size | 19.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56e4e3a356ccb6625fef5030fdd66fd45c25bbdbd45335f3e23b3e96e5b18a6f
|
|
BLAKE2b-256 checksum How to use checksums |
7ae7c0fe8979f2bddd9f7d3dc18d750fba6b76df6193a0a4aa0ac333915aa20e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.0
|
Security for tpds-extension-keystream-connect 1.3.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
