Windows packaging: MSI installer with code signing; harden the batch scripts in the interim
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
The problem sits in install.bat and uninstall.bat, where the odbcconf.exe /A {INSTALLDRIVER ...} call loads an unsigned DLL. The long-term goal is an MSI that registers the driver through the ODBCDriver table, with Authenticode signing, which needs a signing certificate and installer toolchain licence. A newcomer could start with the interim batch-script fixes (elevation check, pause on error, verifying uninstall), but the MSI and signing work is design-heavy and unassigned.
Written by the indexing model from the issue text.
Description
Description
When using the current install.bat / uninstall.bat scripts:
- If started via "Run as administrator" from Explorer, both scripts fail, whereas an elevated cmd.exe works. The window closes before an error can be read, and uninstall.bat reports success without checking what it removed.
- Short-term: detect missing elevation with a clear message, pause on error, verify results in uninstall.
- odbcconf.exe /A {INSTALLDRIVER …} loading an unsigned DLL matches a known detection pattern (MITRE ATT&CK T1218.008, https://attack.mitre.org/techniques/T1218/008/) and triggered security tooling on a user's machine.
Proposal
A proper fix for both:
- an MSI that registers the driver through Windows Installer's ODBCDriver table (https://learn.microsoft.com/en-us/windows/win32/msi/odbcdriver-table), so no odbcconf call is needed and a standard uninstall via Apps, plus Authenticode signing of the DLL and MSI and MakePQX sign for the .mez.
This will require a signing certificate and an installer toolchain's licence to implement and test this robustly.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/stackable-odbc-trino
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
RUSTSEC-2026-0348: Brotli certificate decompression can allocate up to 1 GiB before authenticationOpen
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in stackabletech/stackable-odbc-trino
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
adorsys/status-list-server#698 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nannou-org/egui_graph#92 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 Half a day Newbie friendliness 72/100
sujithputta02/Esapay#13 ·
-
Deduplicate normalized_f64_bits (hash_table.rs and bloom_filter.rs)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
tursodatabase/turso#10002 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
topgrade-rs/topgrade#2419 ·
Maintainers usually reply within 1 day