electron-hardener 0.2.2

Utility to remove features from Electron that modify runtime behavior
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

//! A re-implementation of the `electron-evil-feature-patcher` CLI tool that works nearly identically.

use electron_hardener::{patcher::ElectronOption, ElectronApp, Fuse};
use std::{env, fs};

const FUSES_TO_DISABLE: &[Fuse] = &[Fuse::RunAsNode, Fuse::NodeOptions, Fuse::NodeCliInspect];
const FUSES_TO_ENABLE: &[Fuse] = &[Fuse::OnlyLoadAppFromAsar];

const ELECTRON_FLAGS: &[ElectronOption] = &[
    ElectronOption::JsFlags,
    ElectronOption::RemoteDebuggingPipe,
    ElectronOption::RemoteDebuggingPort,
    ElectronOption::WaitForDebuggerChildren,
];

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let application_path = env::args()
        .nth(1)
        .ok_or_else(|| "no file path provided".to_string())?;

    let mut application_bytes = fs::read(&application_path)?;

    let mut app = ElectronApp::from_bytes(&mut application_bytes)?;

    for fuse in FUSES_TO_DISABLE.iter().copied() {
        app.set_fuse_status(fuse, false)?;
    }

    for fuse in FUSES_TO_ENABLE.iter().copied() {
        app.set_fuse_status(fuse, true)?;
    }

    for flag in ELECTRON_FLAGS.iter().copied() {
        app.patch_option(flag)?;
    }

    fs::write(application_path, application_bytes)?;

    Ok(())
}