What changed, and why it matters
This commit updates the Windows build pipeline for a small helper program called mwebd, which Stack Wallet uses for Litecoin MWEB privacy features. It bumps the mwebd version from v0.1.8 to v0.1.19, switches to a newer Go compiler, removes an old workaround that disabled part of the upstream plugin, and fixes a checksum comparison bug caused by Windows file paths. There is no direct evidence in the commit that this fixes a security vulnerability, but updating dependencies and removing workarounds can have security side effects.
Treat this as a routine build/dependency maintenance commit. Review the mwebd v0.1.19 release notes for any security fixes, verify that the removed flutter_mwebd workaround does not reintroduce build failures or unexpected FFI behavior, and confirm the SHA-256 checksum fix is working correctly on Windows CI runners. No urgent security response is indicated by the commit itself.
Security signals we found
Dependency update: mwebd upgraded from v0.1.8 to v0.1.19
Build toolchain update: Go upgraded from 1.22 to 1.24.13
Removal of CI workaround that disabled upstream flutter_mwebd Windows FFI plugin
Checksum verification bug fix in prebuilt binary fetch script
No explicit security claim, CVE, or advisory referenced in commit
Evidence from the diff
The commit modifies three files: .github/workflows/build.yaml, .github/workflows/release-mwebd-windows.yaml, and tool/build_standalone_mwebd_windows.dart. Key changes: (1) sets MWEBD_FETCH=1 in the Windows build workflow; (2) removes a CI workaround that patched flutter_mwebd’s pubspec.yaml to disable the Windows FFI plugin; (3) updates the default mwebd tag from v0.1.8 to v0.1.19; (4) updates the Go setup action from v5 to v6 and Go from 1.22 to 1.24.13; (5) fixes a SHA-256 checksum comparison bug on Windows by stripping a leading backslash that sha256sum adds when paths contain backslashes; (6) makes the release tag variable const. The diff does not describe any CVE, security bug, or researcher attribution.
Changed components
Windows build workflow (.github/workflows/build.yaml)mwebd Windows release workflow (.github/workflows/release-mwebd-windows.yaml)Standalone mwebd Windows build tool (tool/build_standalone_mwebd_windows.dart)mwebd binary dependencyflutter_mwebd plugin integration on WindowsInspect captured patch +17 / −25
diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml
index e4f1868..2290bc7 100644
--- a/.github/workflows/build.yaml
+++ b/.github/workflows/build.yaml
@@ -265,6 +265,8 @@ jobs:
run: flutter doctor -v
- name: Configure app
+ env:
+ MWEBD_FETCH: '1'
run: |
cd scripts
echo "yes" | ./build_app.sh \
@@ -294,23 +296,6 @@ jobs:
- name: Get dependencies
run: flutter pub get
- # Stack Wallet uses mwebd.exe as a subprocess on Windows, not the FFI
- # DLL, so we don't need libmwebd.dll. The upstream plugin's Windows
- # build path requires WSL, which the GitHub runner lacks.
- - name: Patch flutter_mwebd to skip Windows FFI build (CI workaround)
- run: |
- set -euo pipefail
- cache_root="$(cygpath -u "$LOCALAPPDATA")/Pub/Cache/hosted/pub.dev"
- plugin_dir=$(find "$cache_root" -maxdepth 1 -type d -name 'flutter_mwebd-*' -print -quit)
- if [ -z "$plugin_dir" ] || [ ! -f "$plugin_dir/pubspec.yaml" ]; then
- echo "::error::Could not locate flutter_mwebd in $cache_root"
- exit 1
- fi
- pubspec="$plugin_dir/pubspec.yaml"
- echo "Patching $pubspec"
- sed -i '/^ windows:$/,/^ ffiPlugin: true$/d' "$pubspec"
- flutter pub get
-
- name: Create git_versions.dart stubs
run: |
mkdir -p crypto_plugins/flutter_libepiccash/lib
diff --git a/.github/workflows/release-mwebd-windows.yaml b/.github/workflows/release-mwebd-windows.yaml
index c826ac8..cec0fd5 100644
--- a/.github/workflows/release-mwebd-windows.yaml
+++ b/.github/workflows/release-mwebd-windows.yaml
@@ -6,7 +6,7 @@ on:
mwebd_version:
description: 'mwebd tag to build (must match _mwebdVersion in tool/build_standalone_mwebd_windows.dart)'
required: true
- default: 'v0.1.8'
+ default: 'v0.1.19'
permissions:
contents: write
@@ -18,9 +18,9 @@ jobs:
run:
shell: bash
steps:
- - uses: actions/setup-go@v5
+ - uses: actions/setup-go@v6
with:
- go-version: '1.22'
+ go-version: '1.24.13'
- name: Clone mwebd
run: git clone https://github.com/ltcmweb/mwebd.git --branch "${{ inputs.mwebd_version }}" mwebd
diff --git a/tool/build_standalone_mwebd_windows.dart b/tool/build_standalone_mwebd_windows.dart
index 3f8c178..fe81b13 100644
--- a/tool/build_standalone_mwebd_windows.dart
+++ b/tool/build_standalone_mwebd_windows.dart
@@ -1,6 +1,6 @@
import 'dart:io';
-const _mwebdVersion = "v0.1.8";
+const _mwebdVersion = "v0.1.19";
const _defaultFetchBaseUrl =
"https://github.com/cypherstack/stack_wallet/releases/download";
@@ -17,7 +17,7 @@ Future<void> main(List<String> args) async {
Future<void> _fetchPrebuilt(Directory projectToolDir) async {
final baseUrl =
Platform.environment["MWEBD_FETCH_BASE_URL"] ?? _defaultFetchBaseUrl;
- final tag = "mwebd-$_mwebdVersion";
+ const tag = "mwebd-$_mwebdVersion";
final winAssetsDir = Directory(
"${projectToolDir.parent.path}"
@@ -50,9 +50,15 @@ Future<void> _fetchPrebuilt(Directory projectToolDir) async {
final expected = (await File(
shaPath,
).readAsString()).trim().split(RegExp(r"\s+")).first;
- final actual = (await Process.run("sha256sum", [
- exePath,
- ], runInShell: true)).stdout.toString().trim().split(RegExp(r"\s+")).first;
+ // sha256sum adds a leading '\' to the hash when the filename contains
+ // backslashes. Strip it before comparing.
+ final actual = (await Process.run("sha256sum", [exePath], runInShell: true))
+ .stdout
+ .toString()
+ .trim()
+ .split(RegExp(r"\s+"))
+ .first
+ .replaceFirst(r'\', '');
if (expected.toLowerCase() != actual.toLowerCase()) {
stderr.writeln(
"mwebd.exe sha256 mismatch: expected $expected, got $actual",
@@ -180,6 +186,7 @@ Future<void> _buildFromSource(Directory projectToolDir) async {
Future<void> _waitForProcess(Process process) async {
final exitCode = await process.exitCode;
if (exitCode != 0) {
+ // ignore: avoid_print
print("Exited process with code=$exitCode\n${StackTrace.current}");
exit(exitCode);
}
Why this scored 24/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.