This article provides an overview of bug fixes and known issues in the Fortanix Confidential Computing Manager (CCM) 3.17 release.
Prerequisites
A container registry account to push the converted application container Image(s).
A subscription account on Azure Portal to create Compute Node/s.
Bug Fixes
CCM SaaS:
Fixed an issue where invalid request errors in the SGX converter flow displays 500 error instead of displaying an appropriate response code and message.
Fixed an issue where the timestamp value: “Updated At” does not update and remains same as “Created At” when the credentials of datasets are updated.
Fortanix CCM now adds the capability to support statically predefined networking configurations of routes and ARP entries in AWS Nitro and fixes UDP protocol checksum computation.
Known Issues
CCM SaaS issues:
The
get PCK certAPI does not require authentication currently.Node agents are presenting an invalid certificate chain length.
The converter should throw an error if the certificate key is not in an encrypted folder.
No framing is applied for sending Syslog messages over TCP.
Nitro Converter does not return an error during conversion even when the output image credentials are wrong.
Limitations
Fortanix has a fair usage policy in this Early Customer Access Program. Hence, Fortanix has limited the resources one can create per account. Therefore, it is expected to observe a resource creation failure message once you have reached the max limit.
To report an issue/bug, visit https://support.fortanix.com/hc/en-us/requests/new.
Node Agent Download
Download link for SGX Platform: https://support.fortanix.com/hc/en-us/articles/360043407012-Fortanix-Node-Agent-Software-Intel-SGX-Platform
Download link for AWS Nitro Platform: https://support.fortanix.com/hc/en-us/articles/4412575587732-Fortanix-Node-Agent-Software-AWS-Nitro-Platform
NOTE
The current version of the node agent on Azure Marketplace will not create certificates.