HyperFrames restricts private network access and captured instructions
HyperFrames version 0.9.51 expands protections in video rendering and website capture. Operators can block additional private networks, and checks follow the IPv4 destination embedded in certain IPv6 addresses. Captured page titles and font names face restrictions before reaching agent instruction files. The release also tightens executable and uploaded-file handling.
Artificial Intelligence··Evening
Operators can protect additional private networks
HyperFrames, HeyGen’s video-production project, released version 0.9.51 on November 15 with changes to network access and website capture. Operators can specify additional infrastructure that must remain inaccessible to rendering jobs, beyond the usual reserved address blocks. That configuration governs the downloading of assets as well as the production proxy and rules for pages. An invalid network entry produces a warning and closes access instead of being silently ignored.[1]
Address checks follow the carried destination
The release extracts IPv4 destinations carried within IPv6 addresses, two forms used to address network traffic. The private-network rules then apply to that address, including supported translation forms. Public destinations remain distinguishable from private ones. The change covers attempts to reach a local service through a different address representation rather than treating all such traffic alike.[1]
Captured text is restricted before entering instruction files
Website capture now uses the host name and local name in generated agent instructions instead of freely copying the page title. Font names face character and length limits; unsuitable names are omitted. Captured website text is explicitly identified as data. The release also keeps Chrome’s sandbox enabled on supporting hosts, limits helper executables to trusted folders and prevents playlists disguised as media from reaching the converter.[1]