![n'1fo[r-matik]](https://www.n1fo.fr/wp-content/uploads/2022/04/n1fo-logo-small.svg){kind=logo}
Sandboxie est ce qu'on pourrait appeler un programme de protection d'ordinateur, mais pas dans la même catégorie qu'un antivirus ou autre anti-malware. Dans les grandes lignes, il permet de créer un espace sécurisé où ira s’exécuter un logiciel souhaité (un navigateur internet, un programme quelconque) et toutes les modifications apportées par le logiciel isolé ne se répercutera pas en dehors de l'espace protégé.
Par exemple, dans le cas d'une navigation sur internet avec un navigateur isolé, si vous téléchargez un fichier exécutable qui s'avère être un virus (on parle beaucoup des CryptoLocker ou d'autres logiciels de rançons), le malware ne modifiera que les fichiers à l'intérieur de l'espace protégé laissant ainsi tous les documents et photos personnelles en dehors de cet espace intact.
Sandboxie est un logiciel devenu gratuit pour une utilisation personnelle depuis la version 5.31, des modifications ont été entrepris pour une transformation en logiciel open-source. Ainsi, depuis avril 2020, un autre développeur a repris le développement sous forme d'un fork appelé : Sandboxie Plus.
Il est compatible de Windows 7 à Windows 11 (64 bits uniquement).
Sandboxie Plus / Sandboxie Classic
Versions actuelles : 1.18.0 / 5.73.0
Windows 32 et 64 bits
Added
- added wildcard support for
RecoverFolderandAutoRecoverIgnorepatterns (*,?,**), matching across NT, DOS, and network-alias path forms in both DLL and SandMan #3761 #5318 - added
UseAutoRecoverIgnoreForQuick=[y|n]to applyAutoRecoverIgnorepatterns to the Quick Recovery window (default: enabled) #5278 - added pending-change highlighting to SandMan Options and Settings dialogs; it indicates unapplied changes and not controls whose changes take effect immediately
Options/HighlightPendingChanges(default: enabled), configurable in Global Settings > Interface Config > User Interface
Changed
- reworked the crash dump menchanism
- changed SandMan auto-delete recovery to reuse an already open recovery dialog as the delete decision dialog, regardless of filter state, instead of closing it or silently continuing with box deletion
Fixed
- fixed expected non-user SID profile and shell lookup noise by suppressing matching SBIE1406/SBIE1412 and derivative SBIE1204 FileRootPath messages #5422
- fixed NT device path (
\Device\LanmanRedirector\...) shown in popup notification instead of UNC form, causing garbled display and wrong recovery target #711 - fixed "Close until all programs stop" permanently suspending recovery when clicked while no processes are running
- fixed SandMan Immediate Recovery blinking without showing the recovery window when the new-file event path and scanned recovery path differed only by casing, such as
downloadsvsDownloads - improved SandMan responsiveness during Sbie message and notification floods by batching UI updates and reducing expensive per-row rendering
- added workaround to chrome settings reset, it can be disabled with 'UseChromeSecurePreferencesHack=n' #5184#5286#5180
- this is more of a hack than an elegant solution, we make IsOS(OS_DOMAINMEMBER) return true and when accessign the host's "Secure Preferences" force a migration into the sandbox and remove all "*_encrypted_hash" entries
- note: this only works for settings and extensions host credentials, cookies, passwords, etc. remain unaccessible... from within the sandbox
- if this is requires a manual workaround is required reg add "HKLM\Software\Policies\Google\Chrome" /v ApplicationBoundEncryptionEnabled /t REG_DWORD /d 0 /f
- adapted for MS Edge, SOFTWARE\Policies\Microsoft\Edge, Brave, etc...
- fixed issue with DPAPI when running services as system in sandbox, this allows to access with chrome host credentials, cookies, passwords, etc. when sandboxed
- this requires to enable the elevation service to be sandboxed 'SandboxService=GoogleChromeElevationService' as system 'RunServicesAsSystem=y' and opening the SAM endpoint 'OpenSamEndpoint=y'
- there is also a convinient template 'Template=Chromium_Elevation'
- note: each crome derivative has a different service name like: MicrosoftEdgeElevationService, MicrosoftEdgeDevElevationService, MicrosoftCopilotElevationService, GoogleChromeElevationService, GoogleChromeDevElevationService, BraveElevationService
