Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Windows 11 Smart App Control blocks sharp's unsigned libvips DLL during hyperframes snapshot

Aperta
  • Qualcosa non va?
#4,845 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
node.js, typescript
Ambito
backend, cli

Direzione di ricerca

Start in packages/cli at the snapshot entry point and trace the step that uses sharp; reproduce with the documented npx hyperframes snapshot command on Windows 11 with Smart App Control enabled. Check the Code Integrity events and CLI output, then verify that a blocked native load is reported clearly and snapshot continues without sharp or completes the affected step.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

On Windows 11 with Smart App Control (SAC) on, Windows Code Integrity refuses to let node.exe
load the libvips DLL bundled with sharp when hyperframes snapshot runs. Windows shows a Smart App
Control warning. render and check are not affected, and snapshot still writes its frame PNGs,
so the failure appears to be in a step that uses sharp, and it is silent in the CLI output.

The DLLs in @img/sharp-win32-x64/lib (libvips-42.dll, libvips-cpp-8.18.7.dll) are not
Authenticode-signed. SAC only lets unsigned code load when Microsoft's cloud reputation service
vouches for it, so the same files can load on one day and be refused on another.

Related to #4654 (studio server loads when sharp's native binary is missing): here the binary is
present but the OS refuses to load it.

Environment

  • Windows 11, Smart App Control on
  • hyperframes 0.8.91 via npx
  • sharp 0.35.5 (dependency sharp ^0.35.0 of packages/cli), @img/sharp-win32-x64

Steps

  1. Windows 11 with Smart App Control on.
  2. npx [email protected] snapshot <project> --at <t1>,<t2> --no-end --describe false

What happens

Windows' Code Integrity log (Microsoft-Windows-CodeIntegrity/Operational, events 3033 and 3077)
records that node.exe attempted to load
node_modules/@img/sharp-win32-x64/lib/libvips-cpp-8.18.7.dll and that it “did not meet the
Windows signing level requirements”. This happened on each snapshot run and on no render run.
The CLI reports no error.

Expected

Either the step works, or the CLI reports that sharp could not be loaded (and why) and continues
without it.

Suggestions

  1. Detect a failed native load of sharp, including this Code Integrity case, and report it clearly,
    as #4654 does for the studio server.
  2. Raise signing with sharp upstream: Microsoft's guidance for SAC is that all shipped binaries,
    DLLs included, are signed with a certificate from the Microsoft Trusted Root Program.
  3. Note the limitation in the Windows docs: SAC cannot allow-list a file, and the only user-side
    workaround is turning SAC off, which cannot be undone without resetting Windows.
Lingua principale
TypeScript
Stelle
54.1k
Fork
4.9k
Merge medio
7h 29m
PR unite (30g)
778

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di heygen-com/hyperframes

Tutte le issue di heygen-com/hyperframes

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.