Windows sandbox: one PATH folder whose permissions can't be read breaks every later helper start
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 52/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- rust, typescript
Direzione di ricerca
Read win.rs around RecoveryRecord::undo (1216–1290), recover_abandoned_runs (1293–1335), and the grant logic (1588–1594, 1688–1708). Start by running the Rust tests for sandbox recovery; the issue requests a test where one failed undo does not prevent other records from recovering. Done means access-denied revocation is handled safely and recovery continues per record, quarantining records after repeated failures.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Found in the 2026-10-07 code review (traced through the code; not reproduced with a real folder that denies reading its permissions). Related to #152, which has a different trigger.
Problem
runrecords every existingread_onlypath inrecord.grantedbefore granting, and ignores grant failures for non-required paths (win.rs:1588-1594,1688-1708).RecoveryRecord::undo(win.rs:1216-1290) callsedit_acl(path, sid, 0, Revoke)for each one. That starts withGetNamedSecurityInfoWand returnsErrwhen the permissions can't be read.- The record is kept, and
DeleteAppContainerProfileis skipped. On the next start,recover_abandoned_runs(win.rs:1293-1335) hits the same error,servesendsError{id:null}, and the helper exits.
Scenario
PATH contains a folder that exists but whose permissions the user can't read (for example an admin's tool folder added machine-wide, or a restricted share). After the first sandboxed command, every sandboxed command fails with "cannot read the permissions of X". This lasts until the user deletes the record under %LOCALAPPDATA%\Patch\sandbox-recovery by hand.
Fix
- When revoking, treat
ERROR_ACCESS_DENIEDfromGetNamedSecurityInfoWas "nothing to undo". Without READ_CONTROL/WRITE_DAC the grant could never have been applied. - Recover each record on its own: log a failure, keep going with the other records, and quarantine a record after N failed attempts instead of aborting the helper.
- Rust test: one record whose undo fails, with the other records still recovered.
- Lingua principale
- TypeScript
- Stelle
- 2
- Fork
- 2
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Issue simili
-
area: web bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
kinqsradio/orbyn-engineering#227 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
joeldesante/TurfBuilder#258 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
ncecere/open-mcp-portal#85 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
loathers/garbage-collector#2865 ·
I maintainer di solito rispondono entro 1 giorno
-
test-reliability
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Azure/azure-sdk-for-js#40672 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno