File remove-fuses.patch of Package signal-desktop

It is impossible to monkeypatch a shared copy of Electron, and in future versions of the nodejs-electron package
we intentionally fail the build of any app which tries to do this to alert the packager.

One problematic fuse which may break user data compatibility with upstream binaries is cookie encryption,
but Signal stores data in an sqlite database, not cookies, and users have not reported problems so far.

--- Signal-Desktop-5.60.0/ts/scripts/fuse-electron.ts.old	2022-09-21 19:35:54.000000000 +0200
+++ Signal-Desktop-5.60.0/ts/scripts/fuse-electron.ts	2022-09-27 11:08:24.084185994 +0200
@@ -33,20 +33,4 @@
     `Fusing electron at ${electron} ` +
       `inspect-arguments=${enableInspectArguments}`
   );
-  await flipFuses(electron, {
-    version: FuseVersion.V1,
-    // Disables ELECTRON_RUN_AS_NODE
-    [FuseV1Options.RunAsNode]: false,
-    // Enables cookie encryption
-    [FuseV1Options.EnableCookieEncryption]: true,
-    // Disables the NODE_OPTIONS environment variable
-    [FuseV1Options.EnableNodeOptionsEnvironmentVariable]: false,
-    // Disables the --inspect and --inspect-brk family of CLI options
-    [FuseV1Options.EnableNodeCliInspectArguments]: enableInspectArguments,
-    // Enables validation of the app.asar archive on macOS
-    [FuseV1Options.EnableEmbeddedAsarIntegrityValidation]: true,
-    // Enforces that Electron will only load your app from "app.asar" instead of
-    // its normal search paths
-    [FuseV1Options.OnlyLoadAppFromAsar]: true,
-  });
 }
openSUSE Build Service is sponsored by