TheArchive/restic
1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2025-08-25 23:47:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: Windows VSS Event ID 8194 (#5170)

Browse Source
This commit is contained in:
Snshadow
2025-01-27 00:25:38 +09:00
committed by GitHub
parent ed3922ac82
commit 6301250d83
2 changed files with 41 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
internal/fs/vss_windows.go
View File

@@ -810,6 +810,26 @@ func initializeVssCOMInterface() (*ole.IUnknown, error) {
}
}
// initialize COM security for VSS, this can't be called more then once
// Allowing all processes to perform incoming COM calls is not necessarily a security weakness.
// A requester acting as a COM server, like all other COM servers, always retains the option to authorize its clients on every COM method implemented in its process.
//
// Note that internal COM callbacks implemented by VSS are secured by default.
// Reference: https://learn.microsoft.com/en-us/windows/win32/vss/security-considerations-for-requestors#:~:text=Allowing%20all%20processes,secured%20by%20default.
if err = ole.CoInitializeSecurity(
-1, // Default COM authentication service
6, // RPC_C_AUTHN_LEVEL_PKT_PRIVACY
3, // RPC_C_IMP_LEVEL_IMPERSONATE
0x20, // EOAC_STATIC_CLOAKING
); err != nil {
// TODO warn for expected event logs for VSS IVssWriterCallback failure
return nil, newVssError(
"Failed to initialize security for VSS request",
HRESULT(err.(*ole.OleError).Code()))
}
var oleIUnknown *ole.IUnknown
result, _, _ := vssInstance.Call(uintptr(unsafe.Pointer(&oleIUnknown)))
hresult := HRESULT(result)