Skip to main content

Backend 3.16.0

Tera Insights Team
Tera Insights Team
tiCrypt Team

What is in this release​


New​

  • Add per-VM allow lists: a VM access rule lets the running VM of each listed VM config reach a server on the given ports. An implicit rule applies while the VM runs; an explicit rule also needs a user to open a gate for that VM config, for at most the rule's time limit (/vm/access-rules routes)
  • Licensing server and VM access rule ports accept port ranges as well as single ports
  • An admin can remove a licensing server's deactivation date by sending "deactivation": null

Changes​

  • The ticrypt-allowlist component is no longer needed (subsumed by ticrypt-nft)
  • Allow lists are sent to ticrypt-nft in full when they change and when it connects, instead of being resent on an interval
  • Generated VM definitions use the virtio video model instead of cirrus

Fixes​

  • A licensing server with a deactivation date now stays active until that date, instead of being switched off within a minute; one whose date has passed is now switched off
  • Updating a licensing server with a protocol other than tcp or udp is now refused, as creating one already was
  • Reloading the VM service configuration no longer adds another licensing rule refresh each time
  • Deleting a VM configuration now removes it from VM access rules, so those rules can still be saved

Upgrading​

  • Requires ticrypt-nft 1.1.0 or higher (new API)
  • Allow lists are sent to ticrypt-nft only when nft.enabled = true is set in the ticrypt.vm section of /etc/ticrypt/ticrypt-vm.conf; it is off by default