@saito197 Something is wrong.. or might be that your network is inspected? What’s MD5 checksum for mudfish-6.1.3-linux-x86_64.sh file itself? It should be
I’m also getting the same result from md5sum, but the installer spits out a different value every time I run it
saito@saito-laptop:~/Downloads$ wget https://mudfish.net/releases/mudfish-6.1.3-linux-x86_64.sh
--2025-11-26 12:38:11-- https://mudfish.net/releases/mudfish-6.1.3-linux-x86_64.sh
Resolving mudfish.net (mudfish.net)... 14.63.213.39
Connecting to mudfish.net (mudfish.net)|14.63.213.39|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 11743844 (11M) [application/octet-stream]
Saving to: ‘mudfish-6.1.3-linux-x86_64.sh’
mudfish-6.1.3-linux-x86_ 100%[===============================>] 11,20M 985KB/s in 14s
2025-11-26 12:38:27 (812 KB/s) - ‘mudfish-6.1.3-linux-x86_64.sh’ saved [11743844/11743844]
saito@saito-laptop:~/Downloads$ md5sum mudfish-6.1.3-linux-x86_64.sh
19c4d4637b71097ed6208a17b0355ad2 mudfish-6.1.3-linux-x86_64.sh
saito@saito-laptop:~/Downloads$ sudo sh mudfish-6.1.3-linux-x86_64.sh
Verifying archive integrity...Error in MD5 checksums: acf72d341851a2f41e9454451ab9af1f is different from d8b00b7e4a7c542089792c8c93b583a2
saito@saito-laptop:~/Downloads$ sudo sh mudfish-6.1.3-linux-x86_64.sh
Verifying archive integrity...Error in MD5 checksums: f1947127576f5518a51f84ce78694d48 is different from d8b00b7e4a7c542089792c8c93b583a2
saito@saito-laptop:~/Downloads$ sudo sh mudfish-6.1.3-linux-x86_64.sh
Verifying archive integrity...Error in MD5 checksums: 04b29626619faf4a7dc74bf4de851b5e is different from d8b00b7e4a7c542089792c8c93b583a2
Very interesting… I can see that your result 19c4d4637b71097ed6208a17b0355ad2 looks good. So the downloaded binary is good.
It looks like it’ll failed with --check option. This is a result from my machine based on Ubuntu 24.04 LTS:
$ sh mudfish-6.1.3-linux-x86_64.sh --check
Verifying archive integrity... MD5 checksums are OK. All good.
If you want to ignore the md5 checksum part, I think you can try to use SETUP_NOCHECK=1 option like below:
$ sudo SETUP_NOCHECK=1 sh mudfish-6.1.3-linux-x86_64.sh
Uncompressing Mudfish Cloud VPN v6.1.3.....................
Installation is done under /opt/mudfish/6.1.3.
At this moment, not sure why it’s happening on your machine. If you want to look into this issue a little bit more, please try to run the following command:
Thank you for this details. Interesting.. Do you know what file system for your disk you’re using?
It looks like that this issue could be triggered between the file system behaviour. I’m using ext4. If you’re not, please try to test whether the following tricky method solves your issue:
If this solves your issue, it means it’s triggered by dd if=./mudfish-6.1.3-linux-x86_64.sh ibs=9466 skip=1 obs=1024 conv=sync command, specially conv=sync option.
saito@saito-laptop:~/Downloads$ sed 's/conv=sync//g' mudfish-6.1.3-linux-x86_64.sh > mudfish_fixed.sh
saito@saito-laptop:~/Downloads$ chmod +x mudfish_fixed.sh
saito@saito-laptop:~/Downloads$ ./mudfish_fixed.sh --check
Verifying archive integrity...Error in MD5 checksums: 518e6b4c5f0d9f8258909c4a10cfe880 is different from d8b00b7e4a7c542089792c8c93b583a2
It’s also still spitting different checksums every time I run the command
Here’s the sh -x output for the new mudfish_fixed.sh file:
+ CRCsum=248931734
+ MD5=d8b00b7e4a7c542089792c8c93b583a2
+ TMPROOT=/tmp
+ label=Mudfish Cloud VPN v6.1.3
+ script=./bin/pkg_linux_setup.sh
+ scriptargs=
+ targetdir=6.1.3
+ filesizes=11734378
+ keep=n
+ print_cmd_arg=
+ type printf
+ print_cmd=printf
+ unset CDPATH
+ finish=true
+ xterm_loop=
+ nox11=n
+ copy=none
+ ownership=y
+ verbose=n
+ initargs=
+ true
+ break
+ test n = n
+ tty -s
+ :
+ test 6.1.3 = .
+ test n = y
+ tmpdir=/tmp/selfgz68612
+ dashp=
+ mkdir /tmp/selfgz68612
+ pwd
+ location=/home/saito/Downloads
+ test x != x1
+ MS_Check mudfish_fixed.sh
+ OLD_PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/saito/.dotnet/tools
+ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/saito/.dotnet/tools:/bin:/usr/bin:/sbin:/usr/local/ssl/bin:/usr/local/bin:/opt/openssl/bin
+ MD5_ARG=
+ exec
+ MD5_PATH=/usr/bin/md5sum
+ test -x /usr/bin/md5sum
+ test -x /usr/bin/md5sum
+ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/saito/.dotnet/tools
+ MS_Printf Verifying archive integrity...
+ printf Verifying archive integrity...
Verifying archive integrity...+ head -n 402 mudfish_fixed.sh
+ wc -c
+ tr -d
+ offset=9457
+ verb=
+ i=1
+ echo 248931734
+ cut -d -f1
+ crc=248931734
+ test -x /usr/bin/md5sum
+ basename /usr/bin/md5sum
+ test md5sum = digest
+ echo d8b00b7e4a7c542089792c8c93b583a2
+ cut -d -f1
+ md5=d8b00b7e4a7c542089792c8c93b583a2
+ test d8b00b7e4a7c542089792c8c93b583a2 = 00000000000000000000000000000000
+ MS_dd mudfish_fixed.sh 9457 11734378
+ eval /usr/bin/md5sum
+ /usr/bin/md5sum
+ expr 11734378 / 1024
+ cut -b-32
+ blocks=11459
+ expr 11734378 % 1024
+ bytes=362
+ dd if=mudfish_fixed.sh ibs=9457 skip=1 obs=1024
+ md5sum=77d9aeccc895231ea8c1083a1bc9846f
+ test 77d9aeccc895231ea8c1083a1bc9846f != d8b00b7e4a7c542089792c8c93b583a2
+ echo Error in MD5 checksums: 77d9aeccc895231ea8c1083a1bc9846f is different from d8b00b7e4a7c542089792c8c93b583a2
Error in MD5 checksums: 77d9aeccc895231ea8c1083a1bc9846f is different from d8b00b7e4a7c542089792c8c93b583a2
+ exit 2
As you might know, the mudfish installer uses https://makeself.io/ for packaging. I’d updated its version to the latest stable and built the package again.
Very interesting… I can see that your result