Self signing Tauri app

[eager saffron]

Hi there,

When self signing the app through tauri.conf.json, we're left with these options;

"windows": { "certificateThumbprint": null, "digestAlgorithm": "sha256", "timestampUrl": "" },

Where can I, if possible, put down my company name? I'd rather not have it be signed as "YourCompanyName", self signed or not.

Cheers!

Also... is it possible to not have it sign .exes that I sideload?

[bronze yoke]

This is something I'm interested in as well

[royal terrace]

Where can I, if possible, put down my company name?
isn't this set in the certificate itself? For example https://gist.github.com/thewh1teagle/06022cf1ec17a62949377a17c1b590bd isn't the -Subject "CN=thewh1teagle" part where it takes the company name from?

Also... is it possible to not have it sign .exes that I sideload?
run $env:TAURI_SKIP_SIDECAR_SIGNATURE_CHECK="true" (or however you set env vars in your shell) before building the app.

[eager saffron]

I thought so as well, but for some reason that does not work for me. When I manually sign other files with signtool, I have to set the subject when running the signing command. I can see the subject being set correctly when I check my certificates, so I don't understand why it doesn't automatically get picked up by signtool nor tauri.

[eager saffron]

Cheers Fabian!

I'll try to do it exactly like that gist in a minute, seems to have some extra steps

[eager saffron]

I followed the gist, works just fine now. Not sure why it didn't work before. By the way, is there any way to set that env automatically somewhere in the build? I tried setting it in build.rs but it just doesn't get picked up.

[royal terrace]

the sidecar one? you could modify the tauri script in package.json (if you use npm or similar)

build.rs won't work

beforeBuildCommand for example won't work either

it's the tauri cli itself that needs the env var so the outer most invocation needs the env var set already, which really only leaves us with the script option