Released Sandboxie Plus (Sbie fork) Versions with Signed Driver

Discussion in 'Sandboxie (SBIE Open Source) Plus & Classic' started by DavidXanatos, Dec 7, 2020.

  1. Monica2000

    Monica2000 Registered Member

    Joined:
    May 18, 2020
    Posts:
    41
    Location:
    Spain
    I added that to my global settings, my 32 sandboxes are working as usual. :thumb:
     
  2. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    886
    Location:
    Viena
    oh you shouldn't have even gotten so far, Sbie+ should have complained about you still having processes runnign in the box,
    will be fixed in next build

    you can add it to the global section than it will apply to all boxes

    about recovering I'll add an option to overwrite it to the next build.
     
  3. Zem

    Zem Registered Member

    Joined:
    Dec 19, 2020
    Posts:
    5
    Location:
    UK
    Thanks, I have added it to the global section.

    Thank you very much for looking at the recovery overwrite issue. Much appreciated.
     
  4. bjm_

    bjm_ Registered Member

    Joined:
    May 22, 2009
    Posts:
    3,777
    Location:
    .
    @DavidXanatos
    Um, just moved ClosedIpcPath=\RPC Control\LSARPC_ENDPOINT from my [Edge] ini to my [GlobalSettings] ini.

    With ClosedIpcPath=\RPC Control\LSARPC_ENDPOINT with my [Edge] ini. I found ClosedIpcPath=\RPC Control\LSARPC_ENDPOINT populate with my Edge sandbox Resource Access.

    With ClosedIpcPath=\RPC Control\LSARPC_ENDPOINT with [GlobalSettings] ini. I'm not finding ClosedIpcPath=\RPC Control\LSARPC_ENDPOINT populate with Resource Access in all my sandboxes. Is this as expected?
    0.5.3a
     
    Last edited: Jan 2, 2021
  5. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    886
    Location:
    Viena
    @bjm_ that is strange values from the global section should normally apply to all sandboxes
     
  6. bjm_

    bjm_ Registered Member

    Joined:
    May 22, 2009
    Posts:
    3,777
    Location:
    .
    @DavidXanatos
    [GlobalSettings]

    TemplateReject=Windows10CoreUI
    TemplateReject=FireFix_for_Win7
    TemplateReject=7zipShellEx
    TemplateReject=WindowsRasMan
    TemplateReject=WindowsLive
    TemplateReject=OfficeLicensing
    ActivationPrompt=n
    ForceDisableSeconds=3600
    FileRootPath=C:\Sandbox\%USER%\%SANDBOX%
    SeparateUserFolders=y
    KeyRootPath=\REGISTRY\USER\Sandbox_%USER%_%SANDBOX%
    IpcRootPath=\Sandbox\%USER%\%SANDBOX%\Session_%SESSION%
    EditAdminOnly=n
    ForceDisableAdminOnly=n
    ForgetPassword=n
    ClosedIpcPath=\RPC Control\LSARPC_ENDPOINT
    png_8594.png
    -
    png_8595.png
    with no options from an existing box
    png_8596.png
    with no options from an existing box
     
    Last edited: Jan 2, 2021
  7. Soban

    Soban Registered Member

    Joined:
    Dec 19, 2020
    Posts:
    6
    Location:
    .
    When opening chrome which is not my default browser in sandboxie, I get this error message.

    SBIE2101 Object name not found: , error ConnectPort (C0000022) access=001F0000 initialized=1
    SBIE2101 Object name not found: , error ConnectPort (C0000022) access=001F0000 initialized=1
    SBIE2101 Object name not found: , error ConnectPort (C0000022) access=001F0000 initialized=1

    On regular (non plus) sandboxie 5.45.1 The issue with Firefox still logging the user out on Sandboxed web browser (default browser) from sites like youtube and twitter is a thing still. Any clue what might cause it @DavidXanatos
     
  8. Mr.X

    Mr.X Registered Member

    Joined:
    Aug 10, 2013
    Posts:
    3,841
    Location:
    Mexico
    New bug introduced don't ask me what version cause I noticed today. Sorting sandboxes alphabetically works but uppercase takes precedence over lowercase, the very first letter, not good. I got some sandboxes names both with uppercase and lowercase now they're mixed up.
     
  9. busy

    busy Registered Member

    Joined:
    Apr 10, 2006
    Posts:
    116
    I'm getting BSOD when I start SandMan.exe.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_CORRUPTED_MMPOOL (d0)
    Arguments:
    Arg1: 00000000786f6273, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: 0000000000000000, address which referenced memory
       An attempt was made to access a pageable (or completely invalid) address at an
       interrupt request level (IRQL) that is too high.  This is
       caused by drivers that have corrupted the system pool.  Run the driver
       verifier against any new (or suspect) drivers, and if that doesn't turn up
       the culprit, then use gflags to enable special pool.  You can also set
       HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ProtectNonPagedPool
       to a DWORD 1 value and reboot.  Then the system will unmap freed nonpaged pool,
       preventing drivers (although not DMA-hardware) from corrupting the pool.
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    PROCESSES_ANALYSIS: 1
    
    SERVICE_ANALYSIS: 1
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  19041.1.amd64fre.vb_release.191206-1406
    
    SYSTEM_MANUFACTURER:  System manufacturer
    
    SYSTEM_PRODUCT_NAME:  System Product Name
    
    SYSTEM_SKU:  SKU
    
    SYSTEM_VERSION:  System Version
    
    BIOS_VENDOR:  American Megatrends Inc.
    
    BIOS_VERSION:  2104
    
    BIOS_DATE:  08/13/2013
    
    BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
    
    BASEBOARD_PRODUCT:  P8Z77-V DELUXE
    
    BASEBOARD_VERSION:  Rev 1.xx
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: 786f6273
    
    BUGCHECK_P2: 2
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 0
    
    READ_ADDRESS: fffff8054dafa390: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
     00000000786f6273
    
    CURRENT_IRQL:  0
    
    FAULTING_IP:
    +0
    00000000`00000000 ??              ???
    
    CPU_COUNT: 8
    
    CPU_MHZ: dbe
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3a
    
    CPU_STEPPING: 9
    
    CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 21'00000000 (cache) 21'00000000 (init)
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD0
    
    PROCESS_NAME:  SandMan.exe
    
    ANALYSIS_SESSION_HOST:  USER
    
    ANALYSIS_SESSION_TIME:  01-03-2021 22:41:24.0855
    
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8054ab0bae4 to fffff8054d1f5780
    
    STACK_TEXT:  
    ffffec80`f5f26668 fffff805`4ab0bae4 : 00000000`000000d0 00000000`786f6273 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffec80`f5f26670 00000000`000000d0 : 00000000`786f6273 00000000`00000002 00000000`00000000 00000000`00000000 : SbieDrv+0xbae4
    ffffec80`f5f26678 00000000`786f6273 : 00000000`00000002 00000000`00000000 00000000`00000000 ffffdb8a`4ac829f0 : 0xd0
    ffffec80`f5f26680 00000000`00000002 : 00000000`00000000 00000000`00000000 ffffdb8a`4ac829f0 00000000`00000000 : 0x786f6273
    ffffec80`f5f26688 00000000`00000000 : 00000000`00000000 ffffdb8a`4ac829f0 00000000`00000000 fffff805`4ab027a2 : 0x2
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  baee7fb63df0fdfcc2aba7fc7b99df5fba62fc12
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  01bbdecd079088c98834311c96470219eb8a973d
    
    THREAD_SHA1_HASH_MOD:  10928eba9a3091d02cba96b444221b1fce7ea4f9
    
    FOLLOWUP_IP:
    SbieDrv+bae4
    fffff805`4ab0bae4 cc              int     3
    
    FAULT_INSTR_CODE:  cccccccc
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  SbieDrv+bae4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: SbieDrv
    
    IMAGE_NAME:  SbieDrv.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5fdf8645
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  bae4
    
    FAILURE_BUCKET_ID:  0xD0_SbieDrv!unknown_function
    
    BUCKET_ID:  0xD0_SbieDrv!unknown_function
    
    PRIMARY_PROBLEM_CLASS:  0xD0_SbieDrv!unknown_function
    
    TARGET_TIME:  2021-01-02T22:30:28.000Z
    
    OSBUILD:  19041
    
    OSSERVICEPACK:  685
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  unknown_date
    
    BUILDDATESTAMP_STR:  191206-1406
    
    BUILDLAB_STR:  vb_release
    
    BUILDOSVER_STR:  10.0.19041.1.amd64fre.vb_release.191206-1406
    
    ANALYSIS_SESSION_ELAPSED_TIME:  2b05
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xd0_sbiedrv!unknown_function
    
    FAILURE_ID_HASH:  {6688d3e6-fb19-6cf7-ddd9-c3ef581ee9bb}
    
    Followup:     MachineOwner
    ---------
    
     
  10. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    886
    Location:
    Viena
  11. algol1

    algol1 Registered Member

    Joined:
    Aug 10, 2020
    Posts:
    47
    Location:
    Vienna, Austria
    Hello @DavidXanatos, I'm sorry for having to tell you that the latest bugfix-release v0.5.3 is still useless for me as the issue reported about the lost path-adjustment-screen in the installation-process still persists.

    Instead of upgrading my current Plus-version 0.5.2 it will parallel-install v0.5.3 to the standard path (only option, which I do not want to use) and at the same time leave v0.5.2 untouched and active.

    Also, as a minor issue, in v0.5.2 Sandman refuses to start as a tray-icon only as has been standard with classic Sandboxie. On each boot Sandman will come up in normal window and only after closing that manually will continue to run in the tray.

    These are my 2 cents with the new version so far.
     
  12. Survivor

    Survivor Registered Member

    Joined:
    Jul 11, 2020
    Posts:
    104
    Location:
    Land of Oz
    Could you give some more info what this does. That would help to understand, what we should look at. It can be quite difficult to hunt the effect, if all you know is it blocks something, look if something doesn't work. Could be just something rare or direct stopping a start of a program. So some more hints would be good.
     
  13. busy

    busy Registered Member

    Joined:
    Apr 10, 2006
    Posts:
    116
    Driver version is 5.45.1.0 (Installed Sandboxie-Plus-x64-v0.5.3).

    I have attached minidump file to the post with password protected (txt->zip) and will send password via PM.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_CORRUPTED_MMPOOL (d0)
    Arguments:
    Arg1: 00000000786f6273, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: 0000000000000000, address which referenced memory
       An attempt was made to access a pageable (or completely invalid) address at an
       interrupt request level (IRQL) that is too high.  This is
       caused by drivers that have corrupted the system pool.  Run the driver
       verifier against any new (or suspect) drivers, and if that doesn't turn up
       the culprit, then use gflags to enable special pool.  You can also set
       HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ProtectNonPagedPool
       to a DWORD 1 value and reboot.  Then the system will unmap freed nonpaged pool,
       preventing drivers (although not DMA-hardware) from corrupting the pool.
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    PROCESSES_ANALYSIS: 1
    
    SERVICE_ANALYSIS: 1
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  19041.1.amd64fre.vb_release.191206-1406
    
    SYSTEM_MANUFACTURER:  System manufacturer
    
    SYSTEM_PRODUCT_NAME:  System Product Name
    
    SYSTEM_SKU:  SKU
    
    SYSTEM_VERSION:  System Version
    
    BIOS_VENDOR:  American Megatrends Inc.
    
    BIOS_VERSION:  2104
    
    BIOS_DATE:  08/13/2013
    
    BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
    
    BASEBOARD_PRODUCT:  P8Z77-V DELUXE
    
    BASEBOARD_VERSION:  Rev 1.xx
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: 786f6273
    
    BUGCHECK_P2: 2
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 0
    
    READ_ADDRESS: fffff8054dafa390: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
     00000000786f6273
    
    CURRENT_IRQL:  0
    
    FAULTING_IP:
    +0
    00000000`00000000 ??              ???
    
    CPU_COUNT: 8
    
    CPU_MHZ: dbe
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3a
    
    CPU_STEPPING: 9
    
    CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 21'00000000 (cache) 21'00000000 (init)
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD0
    
    PROCESS_NAME:  SandMan.exe
    
    ANALYSIS_SESSION_HOST:  USER
    
    ANALYSIS_SESSION_TIME:  01-04-2021 21:25:00.0123
    
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8054ab0bae4 to fffff8054d1f5780
    
    STACK_TEXT: 
    ffffec80`f5f26668 fffff805`4ab0bae4 : 00000000`000000d0 00000000`786f6273 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffec80`f5f26670 fffff805`4ab027a2 : ffffdb8a`4ac829f0 ffffec80`f5f26b80 ffffdb8a`4a31edd0 ffffdb8a`4a652a50 : SbieDrv!Pool_Free+0x4c [C:\Projects\Sandboxie\Sandboxie\common\pool.c @ 679]
    ffffec80`f5f266b0 fffff805`4ab02edd : 00000000`00000000 ffffec80`f5f26b80 ffffdb8a`4a31edd0 00000000`00000001 : SbieDrv!Box_Free+0x46 [C:\Projects\Sandboxie\Sandboxie\core\drv\box.c @ 116]
    ffffec80`f5f266e0 fffff805`4ab01636 : ffffdb8a`4a652a50 ffffdb8a`4a31edd0 fffff805`4ab02d20 0000005c`2db2e110 : SbieDrv!Conf_Api_Query+0x1bd [C:\Projects\Sandboxie\Sandboxie\core\drv\conf.c @ 1334]
    ffffec80`f5f26850 fffff805`4d3fcb82 : 00000000`00222007 fffff805`4ab01480 ffffc90e`73e6f100 ffffc90e`73e6f100 : SbieDrv!Api_FastIo_DEVICE_CONTROL+0x1b6 [C:\Projects\Sandboxie\Sandboxie\core\drv\api.c @ 521]
    ffffec80`f5f268e0 fffff805`4d3fc7e6 : 00007fff`44bb9000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x382
    ffffec80`f5f26a20 fffff805`4d2071b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
    ffffec80`f5f26a90 00007fff`6deac094 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
    0000005c`2db2e058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`6deac094
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  38f5d8d1192629b75a486b6b55542349c35b6c34
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  097cb5a23e60da403dd0bfebd4ab5640050c33a2
    
    THREAD_SHA1_HASH_MOD:  298760472c23fb81e946b23f8fb38697e623be5d
    
    FOLLOWUP_IP:
    SbieDrv!Pool_Free+4c [C:\Projects\Sandboxie\Sandboxie\common\pool.c @ 679]
    fffff805`4ab0bae4 cc              int     3
    
    FAULT_INSTR_CODE:  cccccccc
    
    FAULTING_SOURCE_LINE:  C:\Projects\Sandboxie\Sandboxie\common\pool.c
    
    FAULTING_SOURCE_FILE:  C:\Projects\Sandboxie\Sandboxie\common\pool.c
    
    FAULTING_SOURCE_LINE_NUMBER:  679
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  SbieDrv!Pool_Free+4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: SbieDrv
    
    IMAGE_NAME:  SbieDrv.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5fdf8645
    
    IMAGE_VERSION:  5.45.1.0
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  4c
    
    FAILURE_BUCKET_ID:  0xD0_SbieDrv!Pool_Free
    
    BUCKET_ID:  0xD0_SbieDrv!Pool_Free
    
    PRIMARY_PROBLEM_CLASS:  0xD0_SbieDrv!Pool_Free
    
    TARGET_TIME:  2021-01-02T22:30:28.000Z
    
    OSBUILD:  19041
    
    OSSERVICEPACK:  685
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    
    OS_LOCALE: 
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  unknown_date
    
    BUILDDATESTAMP_STR:  191206-1406
    
    BUILDLAB_STR:  vb_release
    
    BUILDOSVER_STR:  10.0.19041.1.amd64fre.vb_release.191206-1406
    
    ANALYSIS_SESSION_ELAPSED_TIME:  1bf6
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xd0_sbiedrv!pool_free
    
    FAILURE_ID_HASH:  {1d4a85ee-624b-b5fb-eb74-77991a7c786b}
    
    Followup:     MachineOwner
    ---------
    
    
    

     

    Attached Files:

    Last edited: Jan 4, 2021
  14. bjm_

    bjm_ Registered Member

    Joined:
    May 22, 2009
    Posts:
    3,777
    Location:
    .
    Okay....on my side....ClosedIpcPath=\RPC Control\LSARPC_ENDPOINT with [GlobalSettings] ini. I'm not finding ClosedIpcPath=\RPC Control\LSARPC_ENDPOINT populate with Resource Access nor Edit ini Section in my sandboxes. 0.5.3a
    png_8624.png png_8625.png png_8626.png
     
  15. beethoven

    beethoven Registered Member

    Joined:
    Dec 27, 2004
    Posts:
    1,270
    Running Version Plus 0.5.2 and don't understand why I am constantly getting a notification re "Do you want to allow SumatraPdf.exe (20124) to copy a 86.00MB large file into Sandbox: Defaultbox? File Name .....Windows\Explorer\iconcache_48db - answering this with No and ticking the remember for this process box does not do anything.
     
  16. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    886
    Location:
    Viena
    @algol1
    will test out the updating whats going wrong there

    about the tray, may be i messed to add a parameter, in the installer,
    you can fix that by unchecking applying and than checking an aplying again the autostart setting in the settings.

    @busy
    thanks got...
    hmmm.... SbieDrv!Gui_InitClipboard+0x284 never changed anything here may be some old bug
    will examine it closer soon

    @bjm_ have you ticked the template checkbox?
    also it wont be shown in the section editor that one does not include template or global values

    @beethoven
    Because it wants to copy it, I'll look into why ignore fails, but i would assume its because its a per process flag and you may get as it should be one prompt per process just that it often starts new instances
    just allow it that it probably will shut up, its just a thumbnails cache for explorer and those shell provided open/save file dialog's so many programs conveniently use.






    @Survivor
    \RPC Control\LSARPC_ENDPOINT is a IPC Port used to talk to lsass.exe the "Local Security Authority" process
    sandboxie opens this one by default since windows 7, but given the sensitive nature of that it does nto seam to me to be a particular good idea to do so.
    I would expect it to break things around remote log on, ingle sign on or alike, so try accessing shared network folders from within sandboxie (first enable this access ofcause)
    That said for me network share access worked just fine and otehr related things like chrome asking for windows username and password in order to show saved passwords in plaintext worked as well.

    If I don't get any reports of negative side effects of not opening this IPC path I'll remove it from the next build,
    if some users run into problems they can Re open the path with the appropriate ini option.
     
  17. bjm_

    bjm_ Registered Member

    Joined:
    May 22, 2009
    Posts:
    3,777
    Location:
    .
    png_8629.png png_8631.png
     
  18. henryg1

    henryg1 Registered Member

    Joined:
    Jun 14, 2020
    Posts:
    120
    Location:
    uk
    Not sure when it started, but I can no longer open an Excel workbook (Office 386) into a sandbox
    upload_2021-1-4_14-17-27.png

    Here are my compatibility settings

    upload_2021-1-4_14-20-36.png

    It has worked previously. Anyone please?
     
  19. robert147

    robert147 Registered Member

    Joined:
    Jun 29, 2020
    Posts:
    22
    Location:
    Netherlands
    @henryg1, do you have Sandboxie installed in the default location ?
    Otherwise you need to adjust "Templates.ini"
    Parameters "HostInjectDll=" and "HostInjectDll64="
    needs to have the correct path to file SboxHostDll.dll

    @DavidXanatos, has provided a good solution and you can set it to:
    HostInjectDll=\SboxHostDll.dll
    HostInjectDll64=\SboxHostDll.dll
     
  20. henryg1

    henryg1 Registered Member

    Joined:
    Jun 14, 2020
    Posts:
    120
    Location:
    uk
    Of course I knew that <fx:hits head against a wall :ouch:>. Or I did, but had forgotten. So many tears (typo but I'll leave it ;)) of updating Sbie, that I had forgotten the need to update my template settings <fx:hits head against a wall again, but harder!> :mad:

    I'll update it now, trying David's solution first, but it would be nice if SB+ could learn to deal with non-standard install locations. Can't it store the location in the registry and go from there (?) - ignorance is bliss.

    Thanks for your help though. More appreciated.
     
    Last edited: Jan 4, 2021
  21. henryg1

    henryg1 Registered Member

    Joined:
    Jun 14, 2020
    Posts:
    120
    Location:
    uk
    Just checked, and

    HostInjectDll=\SboxHostDll.dll
    HostInjectDll64=\SboxHostDll.dll

    are already set.

    So changed them to

    HostInjectDll=C:\Program Files\Utils\Sandboxie-Plus\SboxHostDll.dll
    HostInjectDll64=C:\Program Files\Utils\Sandboxie-Plus\SboxHostDll.dll

    but get

    upload_2021-1-4_17-12-56.png


    if I try just to sandbox an Excel file, and

    upload_2021-1-4_17-9-48.png

    if I try to sandbox Excel.

    I don't think HostInjectDll was what I used to change, but can't remember what I did.

    If I uninstall SB+ and reinstall to the default location I assume that will fix everything. May be easier in the long run.
     
  22. busy

    busy Registered Member

    Joined:
    Apr 10, 2006
    Posts:
    116
    @DavidXanatos

    Oh, I forgot to mention, i tried to use Sandboxie-Plus with old Sandboxie configuration. Now, I'm using without it and no BSOD after starting SandMan.exe.

     
  23. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    886
    Location:
    Viena
    ok. but I don't thint thing it was related to the old config, or did you manage to reproduce the BSOD multiple times?
    idk. wat failed there might have been some strange edge case that resulted in the driver doing something wrong.
     
  24. busy

    busy Registered Member

    Joined:
    Apr 10, 2006
    Posts:
    116
    Yes, i did. BSOD every time when I run SandMan.exe with the old configuration.

     
  25. Survivor

    Survivor Registered Member

    Joined:
    Jul 11, 2020
    Posts:
    104
    Location:
    Land of Oz
    @Survivor
    \RPC Control\LSARPC_ENDPOINT is a IPC Port used to talk to lsass.exe the "Local Security Authority" process
    sandboxie opens this one by default since windows 7, but given the sensitive nature of that it does nto seam to me to be a particular good idea to do so.
    I would expect it to break things around remote log on, ingle sign on or alike, so try accessing shared network folders from within sandboxie (first enable this access ofcause)
    That said for me network share access worked just fine and otehr related things like chrome asking for windows username and password in order to show saved passwords in plaintext worked as well.

    If I don't get any reports of negative side effects of not opening this IPC path I'll remove it from the next build,
    if some users run into problems they can Re open the path with the appropriate ini option.[/QUOTE]
    OK, I didn't see any difference for my usual use case, as expected. So I tried a new box with run explorer, trying to access the mapped network drive, with and without your parameter. Both worked.
    I would say if it could easily be added back, why not remove it, but would be cool to have sandbox option check box or add to list and have this one listed. It is hard to keep track of those parameter.
    However I think some others might better test the sign in with MS, or outlook, ... as I don't use such stuff. That could have impact, reading what you write.

    While doing this, I saw another option BlockNetworkFiles=y or n, which I had on y in my test box, created it with default. That blocked the network share access successfully. Does this one has a place in the sandbox options? I thought it is internet block, but it seems not to be, also it is not the ...mup one. So I wonder. Which it is

    Oh and I forgot, Happy new year to all :cool:

    Just had a fast shot at 0.5.3 Jan, which still says B. Groups still not working right. Though empty ones are staying, even the previous one test1 appeared again, for this, I can't remove them anymore, cannot stack one in another. All those things you showed once in your idea for group. So tree hierarchy. Or wasn't that meant too be. Just testing for Brummelchen here, he is the groupie. :) Not sure if I will use it. But the idea is nice. Maybe I Docker mine even more and group them. Who knows.
     
    Last edited: Jan 4, 2021
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.